View members and guests

Related Videos

• Members versus guests

  Who can use this feature

  Supported on the Organization and Enterprise plans.

  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.

  

  Note: Another type of account in Figma is an admin. Admins are members with extra administrative rights within the team or organization. Admins in Figma →

  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 open and closed organization teams
  • Join open teams or request to join closed teams
  • 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 Figma design and FigJam roles, 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 also have either a viewer, viewer-restricted, or editor role on each product.

  On the Enterprise plan, organization admins can set default roles for anyone joining the organization. Default roles apply to both members and guests.

  Caution: It's not possible to make a guest into a member. People need to have a email address that matches an organization domain to be a member.

  Action	Guests	Members
  Log in using SAML SSO	✕	✓
  Access teams, projects, or files they have been invited to	✓	✓
  Invite other members and guests to resources (if guest access is permitted)	✓	✓
  Join FigJam open sessions	✓	✓
  Access FigJam or Figma design files via link sharing	Files set to Anyone with a link only	Files set to either Anyone with link, Anyone at organization, or Anyone at organization with link
  View other members and guests	✕	Can search for members and guests in the organization
  View all organization teams	✕	✓
  Join or request to join organization teams	✕	✓
  Create new teams in the organization	✕	✓
  Use organization-wide libraries	If invited to source file	✓
  Use an organization’s private plugins	✕	✓
  Use organization shared fonts	✕	✓
  View library analytics (for files they can access)	✕	✓
  Be a team admin of an organization team	✕	✓
  Publish to Community as organization	✕	✕
  Become an organization admin	✕	✓

• Add members or guests to an organization

  Who can use this feature

  Supported on the Organization and Enterprise plans

  There are a few ways to add members and guests to an organization:

  • Domain capture: all Figma accounts with company emails are added to the organization
  • Invite members or guests to teams, projects, or files
  • Add members to the organization
  • Add members to your identity provider (SAML SSO)

  Some methods are only available to members of the organization and not guests.

  	Members	Guests	Initial role
  Domain capture	✓	✕	Viewer only
  Add to the organization	✓	✕	Viewer only
  SAML SSO	✓	✕	Viewer only
  Invite to team, project, or file	✓	✓	Viewer or editor

  Members have an email address that matches any of the organization's domains. Members can access shared resources in the organization, including teams, fonts, libraries, and plugins.

  Guests are external users with an email address outside the organization. They can be contractors, agencies, clients, or external collaborators with external email addresses. Guests can only access the resources you explicitly invite them to.

  Roles and account types →

  Domain capture

  Domain capture makes sure anyone with a Figma account and a company email is included in the organization. This applies to anyone with any existing Figma account, as well as anyone who creates a new Figma account using their company email.

  When domain capture is on, you can still invite members to teams, projects, or files in the organization. Members can join the organization by accepting the invitation. If they don't have an account, Figma will make sure any account they create is part of the organization.

  Invite to teams, projects, or files

  Invite a member or guest to a file, project, or team to add them to your organization. Any member or guest can invite someone to a resource at or below their permission level.

  For example: someone with view access can only invite others with view access. Someone with edit access can invite someone with view or edit access.

  • Invite collaborators to a team
  • Invite someone to a project
  • Invite a collaborator to a file

  Note: Anyone you invite with can edit access is included in the organization's billing. Learn more about adding editors in a quarterly true-up →

  Add to the organization

  Organization and workspace admins can also invite members to the organization from the Members tab. You can't invite guests using this method, but you can invite them to specific teams, projects, or files.

  Figma will give everyone you invite via this process a provisional viewer role. You can update their access to viewer restricted or editor once Figma shows them in the Members tab.

  1. Select Admin settings in the sidebar.
  2. Select the Members tab.
  3. Click Invite member to open the invite modal.
  4. Enter the member's company email address and click Send Invite.
  5. Figma will send an email to the member's email address. Click the link in the email to join the organization.

  Add to identity provider (SAML SSO)

  If you have configured SAML SSO in your organization, you can add members to your identity provider. When added to your identity provider, Figma will create a provisional account for them.

  The third-party documentation below has detailed instructions on how to add members to your identity provider:

  • Azure Active Directory (external link)
  • OneLogin (external link)
  • Okta (external link)
  • Google (external link)
• Make someone an organization admin

  Who can use this feature

  Supported on Organization and Enterprise plans.

  Only organization admins can grant admin access to members.

  Organization admins are members with extra administrative rights within the organization. Grant a member admin access to upgrade them to an organization admin.

  They can view and adjust member and guest roles, view and manage the organization's billing, and adjust organization-wide settings. Admins in Figma →

  You can only make members an admin, it's not possible to give a guest of the organization admin access. Members have an email address that matches an organization domain.

  1. Open the organization in Figma.
  2. Select Admin settings in the sidebar.
  3. Select Members from the menu bar.
  4. Click next to the member.
  5. Select Grant admin access.

  View only admins

  If you have admins that don't need edit access to teams and files, you can update their role to viewer-restricted. This will allow them to manage aspects of the organization without being included in the organization's billing.

  1. Use the search field to find the admin.
  2. In the Figma design role column, click and select Viewer - restricted to remove editor access to Figma design files.
  3. In the FigJam role column, click and select Viewer - restricted to remove editor access on FigJam files.
• Manage roles in an organization

  Who can use this feature

  Supported on the Organization and Enterprise plans.

  Organization admins and workspace admins can manage members and guests in an organization.

  Figma has two products: Figma design and FigJam. Everyone in an organization has has a role on each product. A person's role determines their billing status, if they’re included in your billing. It also controls what activities they can do in design or FigJam files.

  Who can manage roles

  Organization plan: organization admins can manage roles for everyone in the organization. They can review and confirm editors and finalize invoices for true-ups.

  Enterprise plan: workspace admins can help organization admins with managing roles. They can manage roles for people in the workspaces they’re an admin of. They can also review and confirm any new editor seats during a true-up.

  Note: Roles are set an an organization level, they are just one part of Figma’s permissions model. You can control which resources someone can view or edit using team, project, and file permissions. Guide to sharing and permissions →

  View members tab

  View and manage roles for members and guests in the Members tab.

  1. Open the organization in Figma.
  2. Select Admin settings in the left sidebar.
  3. Select Members in the menu bar.

  Workspace admins can switch between workspaces when viewing members. Use the tabs at the top of the member list to switch between workspaces and Unassigned.

  View activity and access

  View member and guest activity and access to decide who needs access.

  1. View the dates of their Last edit and when they were Last active.

     • Click Last edit date to see the last Figma design and FigJam file they edited.
     • Click Last active to open the Recent activity modal for that person.

  2. View their current Design role and FigJam role. If they’re an editor, you can see the date they were upgraded.

  3. Click in the person's row and select View user activity. This opens the Recent activity modal.

     • View the Upgrade date and related Upgrade event.
     • View the last five events in the member's history. For each event, you'll see the date, activity description, related team, and the person's IP address .

     Note: Organization admins can also click See more activity to open the activity log with this member selected. This allows you to see a detailed history of that person’s activity within the organization. View member activity →

  4. If the person is a guest, there is also a Guest access tab. This lets you see which teams, projects, and files the guest has access to.

     • If public links are enabled, you’ll see the guest can access those files.
     • View a list of the teams, projects, and files they can access.
     • View their permissions on each resource.

  Upgrade or downgrade roles

  📖 Explore roles in Figma →

  Click their current Design role .

  1. Select Viewer - restricted (free) to prevent them from being able to Figma design files. They won’t have an editor seat on Figma design.
  2. Select Editor (paid) to allow them to edit Figma design files. This won’t affect their permissions on individual teams or files. They will contribute one FigJam editor seat.

  Click their current FigJam role .

  1. Select Viewer - restricted (free) to prevent them from getting edit access to FigJam files. They won’t have an editor seat on Figma design.
  2. Select Editor (paid) to allow them to edit FigJam files. This won’t affect their permissions on individual teams or files. They will contribute one Figma design editor seat.

  Note: Figma uses a person’s Figma design and FigJam role to calculate your billing. Someone can have a paid role on one product and a free role on the other. How is my invoice calculated →

• How roles are assigned or updated

  Who can use this feature

  Supported on the Organization and Enterprise plans

  Figma has two products or file types: Figma design and FigJam. Everyone in an organization has a role on both products.

  A person's role determines their billing status; if they’re included in your billing. It also controls what activities they can do in design or FigJam files.

  There are three roles: viewer, viewer-restricted, and editor. There are a few ways a person’s role can be set or updated in an organization.

  Initial roles

  Permissions at migration

  When you upgrade to the Organization or Enterprise plan, Figma assigns roles to people based on their existing permissions.

  • Anyone with can edit permissions on a team or file gets an editor role
  • Anyone with can view permissions on a team or file gets a viewer role.

  Add to organization

  When you add people to your organization via domain capture or manual invitation, Figma gives them an introductory viewer role. Organization or workspace admins can change their role after they join.

  Note: People can have edit permissions on teams, while only having viewer roles on Figma design or FigJam.

  Figma only includes them in the organization’s billing once they take an edit action on a file. This includes the Edit file button in the list of upgrade actions ↓

  Enterprise only features

  On the Enterprise plan, there are a few extra ways to assign design and FigJam roles:

  • Set default roles for new members and guests. This allows you to control what level of access people get on each product, when they first join.
  • If you use SAML SSO, you can provision and assign a member's role using SCIM. This allows you to assign roles to members before they join the organization.

  Note: If you set member roles via SCIM, Figma will honor the SCIM provisioned role over the default role. If you have SAML and basic SCIM enabled, but don't use SCIM to set roles, Figma will use the default role setting.

  You can identify members with roles set by SCIM with the next to their role in the Members tab.

  Admin upgrades

  Admins can manage Figma design and FigJam roles for members and guests.

  • Organization plan: only organization admins can make changes to people’s roles. Team admins can only manage team-level permissions.
  • Enterprise plan: organization admins can manage roles for anyone in the organization. Workspace admins can make changes to roles for people in their workspaces.

  Note: You can control which teams people can access with team permissions. Only team admins can make changes to a person’s team-level permissions.

  User-initiated upgrades

  Members and guests can start the upgrade process by taking an upgrade action.

  Anyone with a viewer role can upgrade themselves to a paid editor role by performing one these upgrade actions.

  People with a viewer-restricted role are prompted to request an upgrade when they attempt an upgrade action. Only organization or workspace admins can approve an upgrade request.

  • Share a file from drafts
  • Create a file within a team
  • Open a link to an organization file and take an edit action
  • Request to join a team as an editor (only if a team admin accepts your request)
  • Join a team without any existing editors

  Share files from drafts

  Viewers can upgrade to paid editor roles by sharing a file from their organization drafts with someone else in the organization. This applies to an invitation from the file's share modal, or by sharing an edit link to a file.

  Create new files

  Viewers are upgraded to a paid editor role if they create a file in an organization team. This doesn’t apply to files they create in their drafts, unless they share that file with people in the organization.

  • New FigJam file: upgrades to a paid editor role on FigJam.
  • New design file: upgrades to a paid editor role on Figma design.

  Edit Figma design or FigJam files

  Every file and prototype in Figma has a unique URL. In an organization, people can copy this link to quickly share designs and prototypes with other people in the organization.

  People can interact with organization files based on a few factors. The person's role, team permissions, and the file's link sharing permissions all play a part.

  When a file’s link sharing settings are set to can edit, people will see either an Edit file or Ask to edit button on their first open. 

  A person’s role and the file’s link sharing settings influence which button they see and what happens when they interact with it. For viewers, this will update their role or access. For those with a viewer-restricted role, this will send a request.

  Join teams

  Viewers can request to join closed teams in the organization. As part of that process, they can request either can view or can edit access.

  If a team admin accepts their request to join with edit permissions, Figma will upgrade them to a paid editor role in the organization.

  If a viewer joins an existing team in the organization, which doesn't have any editors or admins in it, they can get edit access by claiming ownership of that team.

• Approve or deny upgrade requests

  Who can use this feature

  Supported on the Organization and Enterprise plans

  People with a viewer-restricted role on either Figma design or FigJam won’t be able to edit files.

  If they try to take an editor upgrade action, Figma asks them to request an upgrade. They can enter a reason for their request before it’s sent to relevant admins.

  The request only applies to that specific product. If someone requests an upgrade from a FigJam file, the upgrade only applies to their FigJam role.

  Who manages upgrade requests

  Figma sends upgrade requests to the people with the most context on that person’s needs.

  • On the Organization plan, upgrade requests go to organization admins.
  • On the Enterprise plan, upgrade requests go to the relevant workspace admin. If the requester isn’t assigned to a workspace, organization admins can manage their request.

  Accept or decline upgrade requests

  Figma sends both an email and in-app notification to relevant admins. Requesters are notified of your decision by email and in-app notification.

  Email

  1. Open the upgrade request email.
  2. Click Manage request to view the request:
     
  3. You’ll see the name and email address of the requester, as well as the product and organization it’s related to.
     1. Select Approve access to grant them an editor role on that product. Figma will notify them of the upgrade. They’ll also be included in your organization’s next true-up.
     2. Select Reject access to decline the request. Figma will tell them their request was declined and their role stay as viewer-restricted.

  Note: If another admin has already approved or declined the request, you’ll see a message that “this request has been already been handled”.

  Notification

  1. Open the organization in Figma.
  2. Click to view your notifications.
  3. You’ll see the name and email address of the requester, as well as the product and organization it’s related to.
     1. Select Accept to grant them an editor role on that product. Figma will notify them of the upgrade. They’ll also be included in your organization’s next true-up.
     2. Select Decline to decline the request. Figma will tell them their request was declined and their role stays as viewer-restricted.
     
• View and export activity logs

  Who can use this feature

  Supported on the Organization and Enterprise plans

  Only organization admins can view member and guest activity.

  Activity logs provide a record of how members and guests interact with organization files and resources.

  • See when people access, copy, and share files.
  • Track any changes made to team administration and settings.
  • Track any changes made to team, project and file permissions.
  • View actions taken by specific members.
  • Track changes made by organization admin to organization-level settings.
  • Identify and prevent misuse of any organization resources.

  Monitor security at scale with the Activity Logs API. On the Enterprise plan, organization admins can use the Activity Logs API to protect their organization’s creative work. Use this API to identify anomalous events faster, build an internal application, and create security rules.

  View activity logs

  Access activity logs in the Activity tab of the organization's Admin settings.

  1. Open the organization in Figma.
  2. In the sidebar, select Admin settings.
  3. Click Activity at the top of the screen:
  4. Use the fields to filter results by your desired criteria. Choose from:
     
     1. Member: Enter an email address to view any events related to that person. These can be actions they have taken, or actions taken by someone else that apply to them.
     2. Date: Enter a start and end date to see results for a specific date range.
     3. Events: Select a specific type of event. Explore tracked events ↓
     4. Team: Select a team to view activity within that specific team.

  

  Note: Admins can also view recent activity for a specific member or guest in the Members tab. If they click to see more activity, Figma will open the Activity tab with that person's email address already populated.

  Activity log events

  Activity log events are available for the last year, a maximum of 365 days. For every event in the activity log, you'll see:

  • The type of event that took place.
  • The team member's name and email address. This could be the person that took the action, or the person the event applies to.
  • Date and time the event occurred. All times are shown in Coordinated Universal Time (UTC).
  • Product the event relates to, if applicable.
  • The Team the event relates to, if applicable.
  • IP address of the related team member.

  

  Members

  • Members signed in or signed out

  Note: Figma doesn't record any log in activities for guests of the organization. Figma also doesn't track when a member closes a browser window or exits Figma without logging out.

  Files

  • Created a file
  • Duplicated a file
  • Exported a file
  • File link access changed
  • Viewer permissions changed
  • File membership changed
  • Moved a file
  • Permanently deleted a file
  • Restored a file
  • Renamed a file
  • Saved a file
  • Trashed a file
  • Viewed a file
  • Viewed a prototype

  Branches

  • Created a branch
  • Merged a branch
  • Updated a branch
  • Archived a branch
  • Unarchived a branch
  • Deleted a branch

  Projects

  • Created a project
  • Deleted a project
  • Project membership changed
  • Moved a project
  • Renamed a project
  • Change the team access of a project

  Teams

  • Created a team
  • Deleted a team
  • Restored a team
  • Team membership changed
  • Renamed a tea
  • Changed the org access of a team
  • Changed the workspace of a team

  Organizations

  • Org merged
  • Org membership changed
  • Upgrade requests and activity
  • Org role changed
  • Exported the members list
  • Requested to join the org
  • Org join request approved
  • Org invite created
  • SCIM token generated
  • SCIM token revoked

  External access

  • Changed guest invite setting
  • Changed open sessions setting
  • Changed public link setting

  Default role

  • Changed default role setting

  Workspaces

  • Added workspace admins
  • Removed workspace admins
  • Created a workspace
  • Deleted a workspace
  • Renamed a workspace
  • Changed a user’s workspace
  • User selected their own workspace

  Community

  • File published, updated, or deleted
  • Plugin published, updated, or deleted

  Users

  Events related to login and authentication:

  • Signed in with email and password
  • Signed in with Google
  • Signed in with SAML
  • Signed out

  Private plugins

  • Plugin published
  • Plugin updated
  • Plugin deleted

  Plugin management

  • Plugin approve list setting changed
  • Approve list plugins changed
  • Install plugins org-wide

  Audio

  • User joined audio call

  Integrations

  • Personal access token created
  • Personal access token deleted
  • App connected
  • App disconnected

  Export activity logs

  You can export a copy of your activity logs, which includes all the data in your activity logs. This is great if you want to back up this information or dig further into events.

  Figma exports your data in CSV (Comma Separated Values) format. You can import this data into a tool or application of your choosing.

  When you request a CSV export Figma ignores any filters you’ve applied. This means the export will include all events within the date range you selected.

  1. Enter a start and end date to limit results to a specific date range.
  2. Click Request CSV in the top-right corner of the screen. 
  3. Figma will email you the activity log in CSV format.
• Invite guests to organization resources

  Before you Start

  Who can use this feature

  Supported on the Organization and Enterprise plans

  People with viewer or editor role in an organization can invite guests at or below their permission level.

  Guests are external users with email addresses that doesn't match any of the organization's domains. They could be contractors, agencies, clients, or external collaborators.

  Guests have limited access to the organization. They can't browse organization teams or access shared resources like fonts, plugins, or library analytics. You can only invite guests to individual teams, projects, and files in the organization.

  Guest access

  Guests can have the same roles and team permissions as members.

  You choose their permissions when you invite them to a file, project, or team. You can give them different permissions on different resources.

  These permissions inform their FigJam and Figma design roles. Roles determine the highest level of access a person can get, as well as their billing status.

  Guests can have any role: viewer, viewer - restricted, or editor. Like members, they can have different roles on design and FigJam files.

  Enterprise plan

  On the Enterprise plan, there are two settings that impact a guest's access.

  • Organization admins can set default roles for new members and guests. Figma will use those roles for any new guests.
  • Organization admins can restrict or disable guest access. If guest access is restricted, workspace or organization admins need to approve guests before they can access any resources.

  Organization plan

  On the Organization plan, new Use the table below to see which roles are assigned based on the resource and permissions.

  Note: Figma only gives them an editor role on the file type you initially invite them to. For example: If you invite them to edit a FigJam file, they will get an editor role on FigJam only.

  Resource	Invite permissions	Figma design or FigJam role
  Team	can view	Viewer on both file types
  Team	can edit	Viewer on both file types
  Project	can view	Viewer on both file types
  Project	can edit	Viewer on both file types
  File	can view	Viewer on both file types
  File	can edit	Editor on invited file type only

  Invite guests

  Invite someone from outside your organization to a file, project, or team. They'll only be able to access the specific resources you invite them to. 

  You can only invite someone at or below your permission level. If you have view access, you can only invite someone with view access. If you have edit access, you can invite some with either view or edit access.

  Team

  Invite them to a team to give them access to all files and projects in that specific team. They can only access and use libraries shared within that team.

  1. Open the team in Figma.
  2. Select the Members tab .
  3. Click Invite in the menu bar.

  Project

  Invite them to a project to give them access to files in that project. Permissions determine what level of access they have on those files.

  1. Open the team in Figma.
  2. Select the project to view.
  3. Click the Share button in the menu bar.

  File or prototype

  Invite them to a file or prototype. If you invite them to the file, they can view any prototypes in that file. If you invite them to the prototype, they can only access the prototype.

  • With the file or prototype open, select Share in the toolbar.
  • From the file browser, right-click on the file or prototype and select Share.

  Confirm guest details

  1. Enter the collaborator's email address in the Email field. To invite multiple people, enter their email addresses separated by a comma.

     Tip! Figma will identify any email addresses with external domains as a (guest). You'll see this next to their email address when inviting them.

  2. Select the permissions you want to give them.
     • Select Can view to give them view access.
     • Select Can edit to give them edit access.
     • Select Can view prototypes only to allow them to view any prototypes in that file (files only).
       
  3. Click Send invite.

  If your organization is on the Enterprise plan, the organization's guest membership setting will let you know if you can invite external users. There are three options:

  1. If there are no restrictions, Figma will ask you to confirm the external invite. Select Share to confirm and send an invite email to the guest.

  2. If admin approval is required, Figma will still send an invite to the external guest. To accept the invite and view the file/project/team, the guest needs to then request access.

     This sends a request to workspace admins (Enterprise only) and organization admins, which they can Dismiss or Add. If the request is approved, the guest can reload the page to access the resource.

     Figma will also send them an email to let them know they've been added to the organization.

  3. If guest access is disabled, an email won't be sent. Figma will let you know that the external user can't be invited to the resource.

  

• Accept guest access requests

  Who can use this feature

  Supported on the Enterprise plan.

  When the guest membership setting is set to require approval, admins need to accept new guests added or invited to the organization.

  Guests only require approval when they first join the organization. Once accepted, guests can be invited to other resources in the organization without admin approval.

  Who can accept guest requests

  Only admins can accept new guests. Figma uses’s the inviter’s workspace, or the location of the file, to determine who gets the request.

  • If the inviter is assigned to a workspace, or the file lives in a workspace, workspace admins can accept or ignore the request.
  • If the inviter isn’t assigned to a workspace, or the file lives outside a workspace, an organization admin can accept or ignore the request

  Accept requests

  Admins can only accept or ignore the request. If a request is ignored, the guest won’t be able to send another request.

  1. Open email / in-app notification
  2. Click View request to review the request.
  3. View details about the request, including:
     • Guest name and email address (matches their Figma account)
     • Organization name
     • Inviter's name, access level (view/edit), resource name
  4. Select Dismiss to ignore the request, or to add the guest via your identity provider.
  5. Select Add to accept the request.

  Caution: If the guest has been invited to a file with edit access, this will update them to a paid editor role for that file type.

  If the guest was invited to a team or a project, Figma will add them with an introductory viewer role on both Figma design and FigJam. They can upgrade themselves to a paid editor role by taking an upgrade action.