Related Videos

• Manage personal access tokens

  Personal access tokens allow you to grant access to your data through the Figma API. Some third-party integrations and plugins require a personal access token so that they can be authorized to access your data within Figma.

  A personal access token can only be used for a single integration. You must generate a new personal access token for every integration you configure.

  Note: Personal access tokens allow third-party programs to access all of your files and data in Figma. It’s not possible to restrict access when using a personal access token. We recommend only giving this information to trusted third-party integrations.

  Generate a personal access token

  1. From the file browser, click the account menu in the top-right corner and select Settings.
  2. Scroll to the Personal access tokens section.
  3. Enter a name for your new token and press Return / Enter.
  4. Copy the token that is generated

  Note: The token only displays immediately after being generated. If you navigate away from the page, you will not be able to copy the token and will have to generate a new one.

  Revoke a personal access token

  If you no longer want to use a third-party integration, you can block access to your data by revoking the personal access token.

  1. From the file browser, click the account menu in the top-right corner and select Settings.
  2. Scroll to the Personal access tokens section.
  3. From the list of personal access tokens, select the token you want to revoke.
  4. Click Revoke access.

  The integration will no longer be able to access your data via the API. If you want to use the integration again in the future, you will need to generate another personal access token and reconfigure the integration.

• Add password protection to files

  Who can use this feature

  Supported on Professional, Organization, and Enterprise plans.

  Only people with explicit edit access to the file can add or reset a password. This includes the file owner and anyone in the share modal with can edit access.

  Every FigJam file, Figma design file, and prototype has a unique link. You can use these links to share your files and prototypes with collaborators.

  There are some situations where you want to share a file publicly, but only want specific people to be able to access it.

  • Share sensitive or private information within a team or organization
  • Share client work in a simple and secure way
  • Give external collaborators a safe way to access resources

  Password protection makes sure only people with the password can access the file. Password don't apply to people with existing permissions on the file, project, or team.

  

  Password protection is just one of the ways Figma protects your data. Learn more about Figma’s privacy and security practices.

  Add password protection

  You can add a password using the file’s link sharing settings. Link sharing controls what access people without existing permissions get when they open a file. 

  Things to note

  • For design files, the password applies to both the file and any prototypes in that file.
  • You can also add password protection to open sessions in FigJam.
  • For files with branches, the password only applies to the main file. This is because only people with access to the main file can access branches. If you add a password to the main file, the link sharing setting for any branches is set to Only people invited to branch. Share a branch →
  • You can’t set a password on a file that’s shared in the Figma Community. Anyone with the link and password won’t be available as a setting in published files.
  • On the Enterprise plan, organization admins can require passwords for all public links. Manage public link sharing →

  1. Open the file and click Share in the toolbar.
  2. Update the audience setting to Anyone with a link and password.
  3. Enter a password in the Choose password field. There are no requirements for password length or character types.
  4. Click Save to apply. Figma will show when the password was set and who it was set by.
  5. You can then update the file permissions for anyone who accesses it using the link and password. Choose from can edit, can view, or can view prototypes only.
  6. Figma will update the file access and reload the file. To access the file again, people will now need to enter the password.
  7. Select Copy link from the share modal to copy the file link to your clipboard.

  Figma will show a generic thumbnail and icon for password-protected files. This applies to files in the file browser, as well as link previews in other tools, like Slack.

  • FigJam files: FigJam’s dot background
  • Figma design files: Default background gray
  • Prototypes: Black background

  

  Open password-protected files

  When someone opens a password-protected file, Figma checks to see if they already have access to the file.

  If the have a role on the file, or access via the team or project, they won't need to enter the password. They can access the file based on their existing permissions.

  If they don’t already have access, Figma will show the Password required screen. They won’t be able to see the file’s contents until they enter the password.

  

  1. Select to toggle password visibility.
  2. Enter the password in the field provided and select Continue.
  3. If the password is correct, Figma will load the file or prototype. If the password is incorrect, you’ll see an error message.
  4. You can now access the file based on the link sharing settings.

  The file will stay unlocked for the next day or so. Figma will prompt you to re-enter the password:

  • After 22 hours has passed
  • If the password is reset
  • You access the file from another browser
  • You clear your cookies
  • You access the file in a private or incognito window

  View password

  It’s not possible to view a password once it has been set. We recommend reaching out to the person who set the password to confirm. You can see who last set the password on the file’s share modal.

  

  If you don’t remember a password you set, you can reset the password ↓

  Reset password

  Forgotten the password, or want to change it to something else? You can reset the password for each file. You need an edit role on the file to reset the password.

  If you change the file’s password, Figma will reload the file for anyone without an explicit role on the file. Anyone with the file open will need to enter the new password to access the file.

  1. From the file, select Share in the toolbar.
  2. Under Anyone with the link and password, you’ll see when the password was last set. Select Reset to change the password.
  3. Figma reloads the file for anyone without an explicit role on the file. To continue to view or edit the file, anyone without a role will need to enter the new password.

  Remove password

  To remove password protection, you need to update the file’s link sharing settings. You can do this from the Share modal.

  1. If you’re in the file browser, you can right-click on the file and select Share. Otherwise, you can select Share from the toolbar in the file.
  2. Update the audience to another setting:
     1. To make the file public, select Anyone with the link.
     2. To restrict access to your organization only, choose from Anyone in organization, or Anyone in the organization with the link. (Organization and Enterprise plan only)
     3. To remove access for everyone, except those invited to the file, select Only people invited to the file.
  3. Figma will update the file access and reload the file for anyone with it open.
• Team permissions

  Who can use this feature

  Supported on any team or plan

  Teams allow you to create and share resources and collaborate on files and projects.

  There are two levels of access a person can have in a team. Every team member has to have either can view or can edit access to the team.

  There are also two other kinds of permissions in a team: admins and owners. We recommend you explore our Admins in Figma article.

  Access

  Every member of a team has permissions that control their default access to the team. A person’s permissions on individual files and projects are then inherited from their team permissions.

  You set a person’s permissions when you first invite them to the team. Team admins can make changes to a person’s team permissions at any time. Manage permissions in teams →

  Can view

  People with view access can still access everything in the team. They can explore projects and view any FigJam or design files.

  While they can’t make changes to team files or projects, people with view access can still experience collaboration in Figma.

  • Explore design files and pages with read-only access
  • Select layers, inspect and copy properties, and export assets from design files
  • Join FigJam boards and express themselves with emotes
  • Use cursor chat to talk to collaborators
  • Add and reply to comments
  • Follow collaborators
  • Join audio calls
  • View and interact with prototypes in presentation view
  • Present slides and presentations

  Anyone with view access can invite others to the team, or individual files and projects within the team. They can invite others, but only with can view access.

  Note: If you don’t want people to copy anything from the file, there is a setting for that! Prevent anyone with can view permissions from being able to copy, save, or export assets within a file. Restrict sharing →

  Can edit

  Members with edit access can view and edit files and projects within that team. This allows them to perform file-level actions, as well as make changes to a file’s contents.

  • Invite other people to the team with either can edit or can view access. They can even invite people to individual files and projects within the team.
  • Adjust the access of other members and external collaborators.
  • Publish styles and components to the team's libraries.

  Edit access doesn't allow members to manage team-wide settings, like default libraries. Or billing-related tasks for teams on the Professional plan. Only team admins can do these tasks.

  Team admins

  Admins are team members that have extra administrative right within the team. This allows them to manage any team settings, including any shared libraries. Guide to team management →

  Note: On the Professional plan, team admins also manage the team's subscription. They are the only people in the team that can manage the Figma design and FigJam roles for people that interact with the team

  Owners

  Every team, project, or file has an owner. There is only one owner for every resource. Usually, the owner is the person that created the resource.

  Existing owners can transfer ownership of a team (or resource in a team) to another team member or collaborator. When transferring the team, the new owner must be a member of the team.

  Permissions

  The impact of team permissions on a person's overall access depends on your plan. Select your plan to explore what each permission allows you to do.

  Starter or Education Professional, Organization, or Enterprise

  On the Starter and Education plans, a person’s team permissions determine their access to design and FigJam files. They also control what team tasks they can perform outside of files.

  General

  Permissions table with a list of general team tasks. Icons indicate if someone with that permission can ✓ or can't ✕ perform that task.

  Action	Can view	Can edit
  Create and edit files in drafts	✓	✓
  Create new files in teams	✕	✓
  Create new projects	✕	✓
  Create new teams	Can create team, but not any files in that team	✓
  Duplicate Community files	✓	✓
  Request to edit a file	✓	Not applicable
  Share files or libraries from their drafts	✕	✓
  Invite people to teams, projects, or files	With can view access only	✓
  Use styles from libraries	In drafts	✓
  Insert components from libraries	In drafts	✓
  Create and share libraries	✕	✓

  Figma design files

  Permissions table with a list of tasks in Figma design files. Icons indicate if someone with that permission can ✓ or can't ✕ perform that task.

  Action	Can view	Can edit
  Open and view design files	✓	✓
  Select layers in the left sidebar or canvas	✓	✓
  Move, edit, or delete layers	✕	✓
  Measure distances between layers in design files	✓	✓
  Use the inspect panel to view layer properties	✓	✓
  Edit design and prototype properties	✕	✓
  Use styles from libraries	In drafts only	✓
  Add, reply to, or resolve comments	✓	✓
  View the version history of a file, then duplicate or share links to specific versions	✓ Last 30 days only	✓ Last 30 days only
  Create and name file versions, or restore previous versions of a file	✕	✓
  View and interact with prototypes and presentations	✓	✓
  View existing prototype flows and connections	✓	✓
  Create or edit prototype connections	✕	✓
  Save a local copy as .fig	✓	✓
  Copy frames, components, and layers	✓	✓
  Export frames, layers, and assets in design files	✓	✓
  Move and adjust layers on the canvas	✕	✓

  FigJam files

  Permissions table with a list of FigJam specific tasks. Icons indicate if someone with that permission can ✓ or can't ✕ perform that task.

  Action	Can view	Can edit
  Pan and zoom in a board	✓	✓
  Select, move, and order objects	✕	✓
  Add, reply to, or resolve comments	✓	✓
  Add temporary emotes	✓	✓
  Use cursor chat	✓	✓
  High-five collaborators	✓	✓
  Copy objects on the board	✓	✓
  Export selection as an image	✓	✓
  Export board as an image	✓	✓
  Export stickies to CSV	✓	✓
  Follow along in a file	✓	✓
  View and interact with link previews	✓	✓
  View timer	✓	✓
  Use templates in drafts	✓	✓
  Use templates in team files	✕	✓
  View and use toolbar	✕	✓
  Create stickies, shapes, connectors, and text	✕	✓
  Use marker, highlighter and eraser	✕	✓
  Add stamps to the board	✕	✓
  Use stickers from libraries	In drafts	✓
  Insert strong blocks, widgets, or media (Images, GIFs, videos, links)	✕	✓
  Interact with widgets	✕	✓
  Run plugins in FigJam files	✕	✓
  View the version history of a file, then duplicate or share links to specific versions	✓ Last 30 days only	✓ Last 30 days only
  Create and name file versions, or restore previous versions of a file	✕	✓

  On Figma’s paid plans, a person’s design and FigJam roles and not their team permissions—determine if they can edit FigJam or design files. This applies on Professional, Organization, and Enterprise plans.

  A person's team permissions only apply to tasks in teams that take place outside of FigJam and design files.

  Note: Removing a collaborator's can edit permissions on teams, files, or projects doesn’t change their role. Team admins need to downgrade a collaborators role to viewer-restricted to remove them from the team's billing.

  On paid plans, it’s possible to create private or view-only projects. This means that a person’s team permissions don’t always reflect what they can access.

  A person can have different permissions at a team, project, and file level.

  Let’s explore this with an example: Vanessa creates a view-only project in the Growth team for a new project. Praveer has can edit access to the team, but can only view the files in this project. Vanessa wants Praveer to be able to join their group brainstorm, so she gives him explicit can edit access to the FigJam file for the brainstorm. Praveer can join and edit the FigJam file as long as he has an editor role.

  Generally, Figma honors explicit permissions over inherited permissions. We can see this play out in our example above. The explicit project permissions (can view) override Praveer’s team permissions (can edit). Then Praveer’s explicit permissions on the file (can edit) override the permisisons inherited from the project (can view).

  Permissions table with a list of common actions and tasks in Figma. Icons indicate if someone with that permission can ✓ or can't ✕ perform that task.

  Action	Can view	Can edit	Team admin
  Invite others to the team or team files and projects	With can view permissions only	✓	✓
  Share files from their drafts	With can view permissions only	✓	✓
  Create projects	✕	✓	✓
  Move files and projects	✕	✓	✓
  Delete team files or projects	✕	✓	✓
  Update team and project names or descriptions	✕	✓	✓
  Remove members from the team	✕	✓	✓
  Change the team name, icon, or description	✕	✓	✓
  Update collaborator permissions on a team, project, or file	✕	✓	✓
  Manage team settings	✕	✕	✓
  Manage Community profile for team	✕	✕	✓
  Choose default libraries for the team	✕	✕	✓
  Transfer ownership of the team	✕	✕	Only the team owner can transfer ownership
  Delete team	✕	✕	✓
  Upload and manage team fonts (Organization and Enterprise plans only)	✕	✕	✓
  View and manage Figma design and FigJam roles (billing status)	✕	✕	✓ Professional plan only
  View, manage, and upgrade the team's subscription	✕	✕	✓ Professional plan only

• Roles in Figma

  Who can use this feature

  Roles are supported on the Professional, Organization, and Enterprise plans.

  Figma has two products: Figma design and FigJam. Everyone on a paid plan (Professional, Organization, or Enterprise) will have 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. There are three roles: viewer, viewer-restricted, and editor.

  On an organization plan (Organization and Enterprise), a person’s team, project, and file permissions also affect their access.

  Who can manage roles

  Only admins can manage roles for other members and guests.

  • Professional plan: team admins can manage roles and permissions.
  • Organization plan: only organization admins can manage roles. Team admins manage team-level permissions.
  • Enterprise plan: organization admins can manage roles for anyone in the organization. Workspace admins manage roles for people in workspaces they manage. Team admins manage team-level permissions.

  Note: On the Enterprise plan, organization admins can choose the default role for each product. Otherwise, anyone new to a team on the Professional plan or an organization, has an introductory viewer role.

  Types of roles

  Viewer

  Viewer is an introductory role that removes barriers to collaboration for new members and guests. Figma doesn't include viewers in the organization's billing.

  Viewers can upgrade themselves to a paid editor role by performing an upgrade action. Admins don't need to approve these upgrades.

  • Share a file from their drafts in the organization
  • Click Edit file to edit an organization or team file
  • Request to join a team as an editor (and are accepted by an admin)
  • Join a team that doesn't have any editors
  • Create a file within a team project

  This allows people to get the access they need without requiring approval. Figma only includes them in the organization’s billing when they signal their intent and take an explicit edit action.

  Note: To restrict a member or guest's access, organization or license admins can downgrade them to a viewer-restricted role. They can do this at any time in the billing process, including during the true-up period.

  Viewer-restricted

  Viewer-restricted members and guests can only take some actions within an organization. Figma doesn't include anyone with a viewer-restricted role in the organization's billing.

  Admins have explicit control over if and when they get an editor seat. People with viewer-restricted roles can’t upgrade themselves to an editor role.

  These members and guests need to request an editor upgrade if they want to edit on Figma design or FigJam. Admins can approve or ignore their request to upgrade them to a paid editor seat on that product.

  Caution: Downgrading a member or guest to viewer-restricted won't remove their edit permissions on teams, files, or projects. While they won't be able to edit files, they can still perform other file and project-level actions. Team permissions →

  Editor

  Editors are billable members and guests that have edit access to at least one team, file, or project. Despite their billing status, editors don't have edit access to the entire organization, just the resources they have can edit permissions on.

  Figma includes anyone with an editor role in the organization's billing. Both members and guests can have editor roles.

  Admins can review and manage roles of any editors. They can also downgrade roles before confirming or finalizing billing.

  Viewer versus viewer-restricted?

  When you add people to a team or organization, Figma gives them an introductory viewer role. Viewers can upgrade themselves to an editor role by performing an upgrade action.

  People with a Viewer-restricted role have explicitly restricted access. Viewer-restricted users need to request an upgrade, which can be approved by an admin.

  Activities

  Some activities are restricted to specific roles. We’ve broken these down into general activities, and activities in Figma design and FigJam files.

  General

  Action	Viewer	Viewer - restricted	Editor
  Create and edit files in drafts	✓	✓	✓
  Create new files in teams	Upgrade action	Drafts only	✓
  Create new projects	Upgrade action	✕	✓
  Create new teams	✓	Can create team, but not any files in that team	✓
  Duplicate Community files	✓	✓	✓
  Request to edit a file	Upgrade action	Requires admin approval	✓
  Share files or libraries from their drafts	Upgrade action	✕	✓
  Invite people to teams, projects, or files	✓	With can view access only	✓
  Join open teams	✓	Can view only	Can view by default
  Request to join closed teams	Can view or can edit	Can view only	✓
  Access secret teams (by invite only)	✓	✓	✓
  Get edit access to organization files via link sharing	Upgrade action	✕	✓
  Use styles from libraries	In drafts	In drafts	✓
  Insert components from libraries	In drafts	In drafts	✓
  Create and share libraries with the team or organization	Upgrade action	✕	✓

  Figma design files

  Action	Viewer	Viewer-restricted	Editor
  Open and view design files	✓	✓	✓
  Select layers in the left sidebar or canvas	✓	✓	✓
  Move, edit, or delete layers	✕	✕	✓
  Measure distances between layers in design files	✓	✓	✓
  Use the inspect panel to view layer properties	✓	✓	✓
  Edit design and prototype properties	✕	✕	✓
  Insert components from libraries	In drafts only	In drafts only	✓
  Use styles from libraries	in drafts only	In drafts only	✓
  Add, reply to, or resolve comments	✓	✓	✓
  View the version history of a file, then duplicate or share links to specific versions	✓	✓	✓
  Create and name file versions, or restore previous versions of a file	✕	✕	✓
  View and interact with prototypes and presentations	✓	✓	✓
  View existing prototype flows and connections	✓	✓	✓
  Create or edit prototype connections	✕	✕	✓
  Save a local copy as .fig (see note below)	✓	✓	✓
  Copy frames, components, and layers (see note below)	✓	✓	✓
  Export frames, layers, and assets in design files (see note below)	✓	✓	✓
  Move and adjust layers on the canvas	✕	✕	✓
  Create branches (Organization and Enterprise only)	✕	✕	✓

  Note: Editors can choose whether to allow viewers to copy, share, or export from a file. This is set for each file individually. If you're a viewer or viewer-restricted member and can't copy from a file, it usually means this setting has been disabled.

  FigJam files

  Action	Viewer	Viewer - restricted	Editor
  Pan and zoom in a board	✓	✓	✓
  Select, move, and order objects	✕	✕	✓
  Add, reply to, or resolve comments	✓	✓	✓
  Add temporary emotes	✓	✓	✓
  Use cursor chat	✓	✓	✓
  High-five collaborators	✓	✓	✓
  Copy objects on the board	✓	✓	✓
  Export selection as an image	✓	✓	✓
  Export board as an image	✓	✓	✓
  Export stickies to CSV	✓	✓	✓
  Follow along in observation mode	✓	✓	✓
  Join audio calls (with captions)	✓	✓	✓
  View and interact with link previews	✓	✓	✓
  View timer	✓	✓	✓
  Use templates in drafts	✓	✓	✓
  Use templates in team files	✕	✕	✓
  View and use toolbar	✕	✕	✓
  Create stickies, shapes, connectors, and text	✕	✕	✓
  Use marker, highlighter and eraser	✕	✕	✓
  Add stamps to the board	✕	✕	✓
  Use stickers from libraries	In drafts	In drafts	✓
  Add components from libraries	In drafts	In drafts	✓
  Insert code blocks, widgets, or media (Images, GIFs, videos, links)	✕	✕	✓
  Interact with widgets	✕	✕	✓
  Run plugins in FigJam files	✕	✕	✓
  View the version history of a file, then duplicate or share links to specific versions	✓	✓	✓
  Create and name file versions, or restore previous versions of a file	✕	✕	✓

• 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	✕	✓

• Admins in Figma

  Who can use this feature

  Supported on any team or plan

  There are three different kinds of admins you can find in Figma. In this article, we’ll explore what actions each of these admins can take, and which plans they’re supported on.

  Team admins

  Supported on: Starter Education Professional Organization Enterprise

  Team admins manage members, permissions, libraries, and other settings for their team. Usually, Figma assigns the person who creates or upgrades a team as a team admin.

  You can have as many team admins on a team as you need. Any existing team admin can give other team members admin access. 

  • Grant admin access to other team members
  • Adjust permissions for team members
  • Remove a person’s access to the team
  • Manage default libraries for the team
  • Update the team name and icon
  • Set the handle for the team’s Community profile
  • Delete team
  • Restored deleted team

  On the Professional plan, team admins also manage billing related tasks, like updating roles and confirming editor seats.

  • Update design and FigJam roles (Professional plan only)
  • View and manage team billing (Professional plan only)
    • Upgrade team plan
    • Update payment method
    • Cancel subscription
  • View and download invoices (Professional plan only)

  Guide to team management →

  Admins on the Professional plan: By default, admins have can edit access to team files and projects. This means they're included in your team's billing. If you want to give someone admin access to the team, without being able to edit files and projects, you can change their role to viewer-restricted.

  Workspace admins

  Supported on: Enterprise plan only

  Workspaces are groups of teams, people, and resources within an organization. They add another layer of structure within large organizations.

  Workspace admins have a level of access below an organization admin. They can perform limited actions within the workspaces they manage.

  Organization admins

  Supported on: Organization Enterprise

  Organization admins are members of an organization with extra administrative rights. They view and manage a whole host of administrative aspects of an organization.

  This includes login and provisioning, access and security; libraries, fonts, and other resources; billing and more.

  Organization teams support team permissions. This allows you to control how people in the organization can find and interact with individual teams.

  While organization admins can manage organization-wide settings, they don’t have admin privileges on individual teams. Only team admins can manage resources in individual teams.

  • Manage organization domains
  • Adjust login and provisioning settings, including SAML SSO and SCIM
  • Manage Figma design and FigJam roles for members and guests
  • Remove people from the organization
  • View all open, closed, and secret teams
  • View and export organization activity
  • Control access to products and features
  • Control guest access and default roles (Enterprise plan only)
  • Manage organization-wide resources, including libraries, fonts, plugins, and widgets
  • Manage the organization’s Community presence
  • Manage organization billing and true-ups

  Guide to Admin settings →