Members versus guests

Everyone in an organization has an account type. A person's account type determines what they can access within the organization.

This includes organization-wide resources, like teams, libraries, plugins, and widgets. It also includes features and functionality, like branching, library analytics, and shared fonts.

There are two main account types we’ll explore in this article: members and guests.

Members

Members are people in the organization that have an email address that matches any of the organization's domains.

Twigma has the twigma.com and dev.twigma.com domains registered to their organization. Anyone that joins the organization with a Twigma email address, for example: name@twigma.com or name@dev.twigma.com, is a member.

Members can access teams, libraries, and other resources shared within the organization.

• View and explore visible organization teams
• Access teams open to the organization or request to join visible teams set to Only those invited
• View activity for other members and guests
• Access styles and components from organization-wide libraries
• View library analytics (for libraries they can access)
• Access shared fonts in organization files
• Use private plugins in organization files

A member’s seat type, and their permissions on individual teams, impact how they can interact with those resources.

There are a few ways to add members to the organization:

• Add them to the organization itself
• Invite them to a specific team, project, or file
• Import members with existing Figma accounts using domain capture
• Provision and authenticate users via SAML SSO

📖   Add organization members →

Guests

Guest refers to anyone in the organization that doesn't have a company email. They are external users with email addresses that don't match any of the organization's domains. They could be contractors, agencies, clients, or external collaborators.

Twigma has the twigma.com domain registered to their organization. They work with an agency called DsgnSystm who they invite to a specific team in the organization. Collaborators from the agency have dsgnsystm.com emails, not twigma.com emails, so they are guests. They can't access any teams or resources outside the team they’re invited to.

Guests have limited access to the organization. They can only access the resources you invite them to. They can't browse organization teams or access shared resources like fonts, plugins, or library analytics.

Set permissions when inviting guests to a team, file, or project. Like members, they can have different permissions on each resource. Guests can also have any seat type.

Organization admins can set seat approval settings for anyone joining the organization. Seat approval settings apply to both members and guests.