Everyone who interacts with an organization has both a Figma design role and FigJam role. Roles determine the highest level of access you can have on those file types. It also determines if you’re included in the organization’s billing.
There are some actions you can only do with a paid editor role. If you have a viewer-restricted role and try any of those actions, you need to request an upgrade.
If you're not sure what FigJam and Figma design roles you have, you can view them in your account settings ↓.
Note: Requesting a role upgrade doesn’t give you edit access to the entire organization. You can only edit teams, files, or projects you have can edit access to.
Request an upgrade
The request upgrade modal allows you to request a role upgrade for either Figma design or FigJam. There are a few places you can start this process from.
Account settings
Open Figma in the organization workspace.
Click your avatar in the navigation bar and select Settings.
Scroll down to the Organizations section to view the organization’s you’re a part of. You’ll see the organization name, if you’re a member or guest, and your Figma design and FigJam roles.
Click Request upgrade next to the relevant organization and role. Request upgrades for Figma design or FigJam separately.
Figma or FigJam file
Your upgrade request only applies to the file type you’re requesting from. For example: if you request an upgrade from a FigJam role, the upgrade only applies to your FigJam role.
Open the Figma design or FigJam file.
Click Edit file in the toolbar to start the request process.
If you already have edit access to the file, this sends an upgrade request. If you don’t have edit access to the file, Figma sends an upgrade request first. If approved, Figma will then send a request to edit to the file owner.
Other locations
You’ll see the request access modal when you try to:
From the request access modal, you can select admins and add a reason for your request:
Use the checkboxes to select admin(s) to send your request to. Check Select all to send the request to all admins.
Add a message to explain why you’re requesting the upgrade (optional).
Click the Request upgrade button. Figma will send an email to the admin(s) you selected.
Contact an admin
If you don't agree with an admin's decision, we recommend reaching out to your manager or an admin.
Figma includes the email of the admin who declined your request in the notification. You can also view a list of Admins on the right side of the organization page.
Anyone who is new to the Organization plan or wants to learn more about navigating the organization workspace.
This article gives you an overview of everything you need to know to get started as a member of an organization.
Understand organization and external team workspaces, explore organization teams, and find shared resources.
Perfect for folks who are used to Professional teams, or are completely new to Figma.
Join organization
You'll need a Figma account to join the organization. There are a few ways to join an organization:
Through an invitation
By opening a link to a file
Via domain capture
With domain capture, Figma will add anyone with a Figma account under a company email to the organization. This applies for existing Figma accounts or if you create a new account with your company email.
For invitations, you can join the organization by accepting the invite to a file, project, or team. You can also join the organization by opening a link to a Figma file.
Figma uses domains to recognize how people can join the organization. If you have a email address that matches a domain in the organization, you'll join as a member. If you don't, you'll join as a guest.
Note: As guests don't have a company email, they can't login using SAML SSO. Guests can still log in via email address and password, even if SAML SSO or Google SSO is mandatory.
Explore file browser
The file browser is what we call the parts of Figma outside of the Editor. The file browser enables you to explore your workspace and navigate between accounts.
Navigate your workspace
The navigation bar at the top of the workspace allows you to access any account and workspace-level actions.
Note: If you're using the Figma desktop app, you can navigate between the file browser and any files you're viewing. Click to open the file browser for the current workspace. When you're viewing the Community, you can navigate back and forward using the arrow keys.
A
Workspace switcher
View the current workspace in the top-left of the file browser. Click to open the workspace switcher to access the Community and any other workspaces you have access to. Switch accounts and workspaces →
Caution: For anyone with a company email, the organization has ownership of the content you create in any workspace associated with your company email.
For guests without company emails, organizations only own what you create and share in the organization workspace.
Within an organization account, you will have at least three workspaces:
Organization workspaces includes all the teams that are included in your organization. It's where you can access organization resources, like private plugins, libraries, and shared fonts. Organization workspaces have their own icons, usually a company logo.
If you're a guest of any organization, you'll see a badge next to the workspace. Guests can only access teams, files, or projects the organization they're explicitly invited to.
External teams workspace is where you find any teams you're a member of, which are outside the organization workspace. You can't access resources from the organization—like private plugins and organization fonts or libraries—in this workspace.
Log out: Select an email address to log out of a specific account, or Log out of all accounts.
Sidebar
Recent files
Select Recent in the left sidebar to view and access files and prototypes you've recently viewed or edited from this account.
This includes files and prototypes from your drafts, team files, and any other shared files you've opened. It's not possible to view recent files across multiple Figma accounts.
Figma lists files and prototypes separately, you can use the tile icon to identify files from prototypes:
Design files
FigJam files
Prototype
There are extra file actions → available from the recent space. Right-click on the file to view the file actions.
Show in project: open the project page where the file is located. Figma will open that project page in the file browser.
Remove from recent: remove the file or prototype from your recents. This won't delete the file, you can still access the file from the team/project where it's located.
Drafts
Access both yourDraftsand anyDeletedfiles from theDraftsworkspace. Use the tabs at the top of the page to switch between them.
Drafts
Every Figma account comes with its own drafts. You can think of your drafts like a sketchbook or notebook, a place where you can jot down your ideas and experiment with different concepts.
Drafts are a separate space from the organization's teams and projects. Other members of your organization can't see what's in your drafts, unless you invite them to your files.
When you leave or are removed from an organization, the organization will take over ownership of your drafts in the organization workspace.
The Deleted files folder is an archive of any files you have access to that have been deleted. This includes files that you deleted yourself and files others deleted.
When you delete a file, Figma will remove the file for all collaborators. You can access deleted files from the workspace under Drafts > Deleted. Use the Created by to filter your results. Choose to view files created by: Anyone, You, or Others.
Figma will keep files in the deleted files folder indefinitely. It's not possible to open a deleted file, but depending on your access to the original file, there are some actions you can take.
Intellectual property in an organization: The organization has ownership over everything you create in the organization workspace. This includes files in your drafts, teams, and files or projects other collaborator's share with you.
Shared projects
Select Shared files or Shared projects in the sidebar to view files or projects outside of dedicated teams. This includes:
Files from another members drafts, which you have a role on.
Files from teams you're not a member of, which you have a role on.
External projects that you have a role on.
Tip!Organization admins can find and manage the drafts of any deleted organization members in Shared projects.
View organization teams
Organization members can create and join as many teams as they want in the organization space. Click on the organization name in the sidebar to access all teams in the organization.
View the team name, icon, and description, as well as any members in that team. Click the Join or Request to join button to join a team.
Click New team at the top of the page to create a new team in the organization.
Find out which members are organization admins under the Admins heading.
A team's organization access setting controls how members can access each team. Guests must be invited to any type of team, regardless of the team's organization access.
Open: Members can freely join open teams with can view access. An admin or editor can upgrade members to give them can edit access.
Closed: Members can request can view or can edit access to the team. Team admins accept.
Secret: Members must be invited to the team by an existing member. They can invite members with either can view or can edit access.
Figma Organizations go beyond the team setup you may be used to in a Professional team. Instead of a single workspace for a team, you have a dedicated "Organization space".
Everything in the Organization space is owned by the organization. This includes files from individual's Drafts and every team within the organization.
There are two levels of permissions in a Figma Organization, team permissions and organization permissions.
Team permissions work the same way as they do in a Starter, Education, or Professional team.You'll likely be a member of multiple teams in the organization, you can have different permissions on each team.
Everyone who interacts with an organization will also have an account type and a role.
A person's account type defines how much of the organization they can access. A person's role determines if they can get edit access to teams, projects, or files. It also determines if they're included in the organization's billing
You can create as many teams as you need within an organization. Choose to map teams to your company's hierarchy, or create cross-functional teams for company-wide projects.
Control how other members of the organization can find and access teams with Organization Access. There are three levels of organization access: open, closed, and secret.
Teams in organizations also have access to extra features, like Design System Analytics, which allows you to track component usage across teams in your organization.
Organization Admins can manage every aspect of the Organization in the organization's Admin Settings. They can adjust members, view teams, monitor activity, manage billing, and configure security settings.
Figma Organization also gives you greater control over shared resources, like plugins, fonts, and organization-wide libraries.
Organization Admins do not have admin access to every team in the Organization. You can only perform admin actions on teams if you are a Team Admin.
Organization Admins can view a list of open and closed teams in the Organization. From here they can claim ownership of empty teams, and perform limited bulk actions.
As members can join many teams, Figma bills organizations as a whole. Anyone with can edit access to a team, project, or file outside their drafts is included in the organization's billing.
Branches are controlled environments—like sandboxes—where you can explore changes to styles, components, and other aspects of a file or library without affecting the main file.
A main file is the file from which you create a branch, and branching allows main files to continue acting as the source of truth.
While viewing a branch, check for updates from the main file and apply any changes to your branch to make sure you're using the latest version.
When you're satisfied with your changes, you can review and merge your branch with the main file. You'll have the option to resolve any conflicts before applying changes from your branch to the main file.
View branches
Who can view branches
Only people with an editor role in the organization can access the branching feature.
Anyone with can view or can edit access to the main file can view branches.
Identify files with branches and view them from the file browser or Figma Editor.
From the editor
Click the next to the file/branch name in the toolbar.
Select See all branches to open the branches modal.
If you have can edit access to the main file, you can take further action on branches from the file name menu:
Select Duplicate as a file to create a new file from the branch. This will create a separate file, so you won't be able to apply any changes from that file back to the main file.
Select Rename to change the name of the branch (from branch only)
Select Archive to archive the current branch without merging (from branch only)
The Branches modal lets you see all Active and Archived branches, as well as any branches that you created (Yours).
If you have can edit access to the main file, you can do the following from the Branches modal:
Click the Merge button to merge the branch
Click the to open the actions menu:
Archive branch
Copy link to the branch
Rename branch
From the file browser
If a file has branches, you'll see an icon on the top-left of the file tile, and the total number of branches underneath the file name.
Click to view the main file
Use the dropdown to select one of the branches
Create a branch
Who can create branches
Only people with an editor role in the organization can access the branching feature.
Anyone with can view access to the main file can create branches and edit the branches they have can edit access to.
Anyone with can edit access to the main file can create and edit all branches on the file.
Only people with an editor role in the organization can access the branching feature.
Anyone with access to the main file can share branches.
If you're working on revisions or iterations on a branch, you may want to share your progress with other designers and collaborators.
Share branches with others to allow them to view or edit them. There are a few ways to share branches:
A
Via main file
Anyone with can view access to the main file can view any branches on that file.
Click the next to the file/branch name in the toolbar.
Select See all branches to open the branches modal.
Select the branch to open it in the Editor.
B
Via share link
Share a branch link and control access to the branch using link sharing.
Open the branch.
Click the Share button in the toolbar.
Click the link sharing setting.
Select Anyone with a link to allow anyone to access the file using the file link.
Click Copy link to add the branch link to your clipboard.
C
Via invite to branch
Invite a collaborator to the branch with specific permissions.
Click the Share button in the top-right corner.
Enter the collaborator's email in the email field.
Click to adjust their permissions.
Select can view to give them view-only access to files in that project.
Select can edit to give them edit access to any files in that project.
Click Send invite to send an email invitation to their address. If they're already using Figma, they'll get an in-app notification as well.
Tip! You can tell if a file link is for a main file or a branch as all branches will include a /branch/ variable and a unique string for that branch.
Receive updates from the main file
Who can receive updates
Only people with an editor role in the organization can access the branching feature.
Anyone with can viewaccess to the main file can receive updates for branches they created or have can edit access to.
Anyone with can edit access to the main file can create and receive updates for all branches on the file.
Note: It's currently not possible to choose which changes from the main file you want to apply, so you'll need to receive all updates.
If changes are made in the main file, you'll be notified in any branch you have can edit access to, and have the option to receive these updates.
Expand the menu next to the file/branch name in the toolbar.
Select Update from main... to preview any updates.
View a list of items that have been , , or . You can see a preview of the latest versions, but it's not a before and after of what's changed.
Select Apply changes to apply all updates to your branch.
Receiving updates will change any existing layers, components, or styles in your branch file to match the ones in the main file. If new assets were created in the main file, they will be added to your branch. If you added new assets in your branch, those will not be deleted.
Undo updates from main
If a branch received updates from the main file and you wish to undo or reverse this action, you can restore a previous version of the file.
From the branch, click the next to the file/branch name in the toolbar.
Select Show version history to open version history in the right sidebar.
Select a version before the updates from the main file.
Right-click the version or click the and select Restore this version.
Figma will add two autosave checkpoints to the file's version history.
A checkpoint that saves the current version up until you clicked Restore this version. This is an autosaved version with a timestamp that matches the current time.
A checkpoint at the same timestamp for the version you just restored.
Click Done in the toolbar to exit version history.
Reviews and approvals
Before you Start
Who can request and approve changes
Only people with an editor role in the organization can access the branching feature.
Anyone with can view or can edit access to the main file can request a review.
Anyone with can view or can edit access to the main file can approve changes.
Request a branch review
When you're finished making changes in your branch, you can request one or more people to review and approve the changes before merging the branch to the main file. This process is not a requirement for merging to the main file.
Open the branch you want reviewed.
Expand the menu next to the file/branch name in the toolbar.
Select review and merge changes.
The Branch review modal opens, allowing you to preview changes you've made and to select reviewers to approve the changes. Click in the top right-hand corner to search for and select your reviewer(s).
Once you've added your reviewer(s), click Request review.
The reviewers will be notified via in-app notification and email. A label will also appear next to your branch name in the toolbar to indicate an in review status.
Approve changes
If someone requested you to review their branch for approval, you'll be notified via in-app notification and email.
Click on the in-app notification or open the link from your email to access the branch's Branch review modal.
Alternatively, you can open the branch you want to review, click the menu next to the file/branch name in the toolbar, and select review and merge changes.
You can preview the changes from this modal. If you approve of the changes, click Approve next to your name under the list of Reviewers.
Click to revoke or undo your approval.
Merge
Who can merge branches
Only people with an editor role in the organization can access the branching feature.
Anyone with can edit access to the main file can merge branches.
Note: If you have can view access to a main file, you won't be able to merge branches to the main file even if the branch was reviewed and approved. You'll need to coordinate outside of the Figma app with someone who has can edit access to the main file.
When you want to apply your branch changes to the main file, you can merge the branch.
As part of this process, you'll see if there are updates available from or conflicts with the main file. Figma will alert you of this and allow you to choose how to resolve them.
After merging a branch into the main file, you have the option to undo the merge. However, keep in mind that the branch won't be recreated when undoing a merge.
Merge branch to main file
Open the branch you want to merge.
Expand the menu next to the file/branch name in the toolbar.
Select Review and merge changes.
The Branch review modal opens allowing you to preview the changes you've made in the current branch.
View a list of components, instances, or layers that have been , , or . Figma groups changes by page.
If there are any updates from the main file, you'll have the option to Update from main file ↓ or Resolve conflicts ↓ if those changes conflict with items in your branch.
Select an object or page to view the changes side by side or overlayed.
Side by side view is displayed by default. On the left shows what your object looks like before your changes (what it looks like in the main file). On the right is what that object look will look like after you merge your updates (what it looks like in the branch).
Overlay allows you to compare the before and after by placing them on top of one another. On the bottom is what the object will look like before your changes (what it looks like in the main file). On the top is what the object will look like after you merge your updates (what it looks like in the branch). Drag the toggle left or right to adjust the opacity of the after object.
View the layer, frame, or component name at the top of the modal.
Use the buttons to:
Zoom out
Zoom in
FIT Zoom to fit
Use the and arrows at the bottom to move between changes if there is more than one change.
Click the in the top left to go back to the summary.
Click the Merge button to apply. Figma will apply all your changes from the branch to the main file and archive the branch.
Resolve conflicts
If other collaborators have been continuing to make changes to the main file, you may receive conflicting changes alert when reviewing your changes. This means one or more of the items you've made changes to has also been updated in the main file.
Figma will also let you know if there are any conflicting changes from the Branch review modal.
Click the Resolve conflicts button to view any conflicts.
View a list of conflicts in the left sidebar.
Select an option from the list to review the conflicting changes side-by-side. The version from the main file (source) is on the left and the branch on the right.
Select which version you would like to use. Figma will add a badge next to the conflict to show whether you selected the main or branch.
Repeat the process for any other conflicting changes. You'll need to choose a version for every conflict.
To quickly select the same option for every conflict: use the Resolve all menu to apply your selection in bulk:
Pick main file to use the latest changes from the main file
Pick branch to use the changes from the branch for any conflicts
When you have a selection for every conflict, click the Next button to move to the next step of the process.
If there are other updates from the main file, you will preview those next. Click Apply changes to apply those updates.
Figma will apply updates from the main file return you to the branch. You can then return to the Review and merge process ↑
Undo merge
If you have merged changes from a branch and want to undo these changes, you can restore a previous version of the file.
Note: Reversing or undoing a merge will not restore the branch associated with the merge.
From the main file, click the next to the file name in the toolbar.
Select Show version history to open version history in the right sidebar.
Select a version before the merged branch. Identify a merged branch with the Branch merged icon.
In the right sidebar, click next to the version and select Restore this version.
Figma will add two autosave checkpoints to the file's version history.
A checkpoint that saves the current version up until you clicked Restore this version. This as an autosaved version with a timestamp that matches the current time.
A checkpoint at the same timestamp for the version you just restored.
View activity related to branching and merging in the file's version history. Figma will create checkpoints when you create a branch and merge a branch.
Figma will create an extra checkpoint in the file's version history before merging the file, this preserves a record of any other changes made to the main file before it was merged.
Everything that happened in the branch will be contained in that single checkpoint. You can view the detailed version history of a branch when viewing the branch itself.
Branch created
Updated from main
Branch merged
Comments
Comments from the main file don't appear in any branches
Comments do not count towards changes when checking for updates from the main file
Comments from the branch don't end up in the main file when you merge
Publishing libraries
You can only publish to a library from the main file. If you've made changes in a branch that you want to share, you'll need to merge the branch before publishing.
Publishing to the Community
You can only publish to the Community from the main file. If you want to publish the branch, you can duplicate it to create a new file that's separate from the main file.
In the toolbar, click the next to the file name.
Select Duplicate as new file from the options.
Figma will duplicate the branch and add it as a file to the existing location. The name of the file be Main file name : branch name (Copy).
Every team in Figma will have its own dedicated workspace, where you can access projects and files, view members, and apply team-level settings like default libraries and custom fonts.
One of the big benefits of Figma Organizations is that you can create as many teams as you need. As members of the organization can join multiple teams, you can easily establish cross-functional teams and share resources across them.
There are different ways to structure your teams. Create teams around your company's hierarchy, build multi-disciplinary teams for each product vertical, or create workspaces to collect resources and explore company-wide projects and initiatives.
Note: Anyone with an email address that matches an organization domain is a member. Anyone without an email that doesn't match the organization's domain(s) is a guest.
View teams
Organization members can view all teams in the organization from the organization space. If you're inviting guests from outside the organization, they can only view and access the teams you shared with them.
View the current workspace in the top-left of the file browser. Click to open the workspace switcher to access the Community and any other workspaces you have access to. Switch accounts and workspaces →
Click organization in the sidebar to view the organization's home page. This allows you to:
View all open and closed teams in the organization
Teams in an organization have an Org access setting, which determines how members can find and view teams. There are three access levels: open, closed, and secret.
Tip! Organization admins can also view a list of open and closed teams in the Admin settings. Admins can join, request to join, or leave teams they are a member from the Teams page.
Join teams
When you join an organization team, Figma will add that team to the sidebar in your file browser. You will only be able to access that team in the organization's workspace.
Join open teams
Request to join closed teams
Invite-only secret teams
Note: Team permissions in an organization are the same as team permissions in a Professional, Education, or Starter team. Learn how to manage teams and members →
Join open teams
Every member of an organization will be able to search for and find open teams. This allows you to search, view, and discover any files or projects within that team.
Join open teams without requiring an invitation from an existing member. By default, you join open teams with can view permissions.
You can also join an open team if someone invites you to the team. You'll need to accept the invite via the email or notification to join.
Click the Join button to add yourself to the team.
You can now view and comment on any files and projects within that team. To request edit access, you can ask another team member to upgrade you.
Note: An existing editor or admin of a team can give other members can edit access to the team. Figma include members with can edit access to files, projects, or teams in the organization's billing. Learn more about upgrades in an organization →
Request to join closed teams
Any member can search for and find closed teams, but they can't view any files or projects within them.
Members can request to join closed teams at viewers or editors. A team admin will need to confirm any requests, before they can join the team.
Existing members can invite other collaborators to the team. They can only invite collaborators at their permission level or lower. For example: a viewer can only invite a viewer, but an editor can invite a viewer or editor.
Click the Request to join button on the team card.
Use the to choose can view or can edit access.
Add any notes or information to give the team admin some context (optional).
Click Request access.
Figma will send a notification to every admin on that team, which they can approve or reject. You can only access the team once an admin has approved your request.
Caution: If you request to join a team as an editor, Figma will upgrade your role in the organization and include you in the organization's billing. Learn more about requesting upgrades →
Tip! If you don't need access to team anymore, or want to change the permission level, click Cancel request next to the team.
Invite-only secret teams
Secret teams are hidden from members of the organization, so organization members won't see them on the organization page or in the teams tab of the organization's Admin settings.
To get access to a secret team, an existing member needs to invite you. Only editors and admins can invite collaborators to a secret team. They can invite both members or guests.
Note:Organization admins can only access secret teams of which they're a member. Organization admins can see activity related to secret teams, including team members and file names, in the organization's activity logs.
Create teams
Any member of an organization can create a team. Guests aren't able to create teams in the organization space.
Click on the organization name in the sidebar.
Click the New team button in the top-right corner.
Give the team a Name.
Use the to select the Org access level.
Click Create team to create the team.
Figma will open the new team workspace. Click Add a team description to enter a bio for the team (optional).
Note: If you are a viewer in the organization and create a team, Figma will upgrade you to an editor and include you in the organization's billing.
Leave teams
When you leave a team, you will no longer be able to access any files, projects, libraries or fonts in that team.
You can leave a team from a few places in the organization space.
1
Sidebar
Right-click on the team name in the sidebar.
Select Leave team from the options.
2
Team page
Click on the team name in the sidebar.
Click the next to the team name in the menu bar.
Select Leave team from the options.
3
Organization page
Click on the organization name in the sidebar.
Hover over the Joined button next to the team you want to leave.
Any organization member can access resources shared across the entire organization. Guests of the organization can only access resources you invite them to.
Organizations go beyond the team setup you may be used to in a Professional or Starter team. Create unlimited teams in an organization and access them all from the organization in the file browser. Any team you create will have access to all the features of a Professional team, plus some extras.
In addition to that space, members have a personal space for any teams outside the organization. Everything in the organization space is owned by the organization. This includes files from every team in the organization, as well as files in individual's drafts.
In this article, we'll cover accessing shared resources including files, libraries, fonts, and plugins.
Note: Everyone in an organization has both an account type and a role. These control what resources a person can access in the organization and how they can interact with them.
Sharing files in an organization is different than sharing files from a Starter, Education or Professional team. Organizations support seamless collaboration between members, so there are a few ways members can get access to files:
A member invites them to the file
They are a member of the team or project
They open a link to an organization file (link sharing)
Caution: If you invite someone as an editor, who doesn't already have an editor role in the organization, Figma will upgrade them to paid status and include them in the organization's billing.
Note: If you invite someone who's email address doesn't match any of the organization's domains, they will be a guest of the organization. Guests can only access the files, projects, and teams to which you invite them.
Invite collaborators to files
Invite a collaborator to a file in your organization to give them an explicit role on the file. You can view everyone who has a role on the file in the share modal.
Click the Share button from the toolbar in the file.
Enter the member's email in the Invite someone.. field.
Choose what permission to give them
Can edit: Invite them to the file as an Editor. This requires a paid seat in an Organization.
Can view: Invite them to the file as a Viewer.
Click Send invite to confirm. They will need to accept the invite to edit the file.
Invite members to teams
When you are a member of a team, you can access to any files and projects within a team. View the team's access from the file's share modal:
Every file and prototype in Figma has a unique URL. For example: http://www.figma.com/file/ABCDEFGHIJKL/file-name
You can use this link to share designs and prototypes with members of your organization. This includes organization members who aren't invited to that specific file or team
Use link sharing settings to define who can open the file, and whether they have view or edit access. The default settings are Anyone at Organization with link and can view. Learn more about sharing links in an organization →
Inherited permissions versus explicit roles: If a user gets access to an organization file via a link, they will be able to access the file based on the file's link sharing settings (Can view or Can edit).
Like members who can access files via team-level permissions, this is an inherited permission and doesn't give them an explicit role on that file. ;
This means that members listed in the share modal won't include everyone who has access to, or interacted with, the file.
Libraries
Styles and components live in the files you created them in. To access and reuse these in other files, you can publish them to a library. This allows you to maintain a consistent brand and style, at scale.
Figma gives you access to an extensive catalog of Google Web Fonts. If you would like to use extra fonts in your Figma designs, you can use local fonts on your computer.
If you're using the Figma Desktop app, any local fonts will already be available to you. You can find these alongside the Google Web Fonts in the font picker.
If you're using Figma in the browser, you will need to install the Figma Font Helper application. This allows you to access any fonts you have stored locally on your computer when using Figma in the browser.
Figma Organizations can also upload and share custom fonts in the organization. This allows members to share fonts in a specific team, or across the entire organization.
Only organization admins can upload fonts to the entire organization.
Only team admins can upload fonts to a specific team.
In an Organization, you have both an Organization and Personal space. Figma links any plugins you install to your entire account.
Organization members can access both public and private plugins in an Organization. This allows other members of the Organization to use internal plugins, as well as access plugins from the Figma Community.
If the Approved plugin ;list is enabled, you can only use public plugins on this list within the organization space. You can use plugins outside of that list in your external team.
To find and install plugins that are private to your organization:
Open the Figma file browser and click the organization name in the left sidebar.
Select the Plugins header at the top of the page to view any plugins that are private to your organization.
Click the ↓ Install button to add the plugin to your account.
Make plugins
If you are a member of an organization you can choose to publish plugins privately or publicly. When you publish your plugin, you can choose to share the plugin privately or publicly.
Private plugins are only available to members of the organization, while public plugins are available for everyone.
Private
Organizations will often have their own systems and tools they have developed. They can include private information or data that members can't share outside the organization.
Any member of an organization can make and share a private plugin.
To publish plugins privately:
Set the Publish to setting to Organization name to create a private plugin.
Note: When a member shares a plugin with the organization, Figma lists that member as the plugin's creator. They can choose to add other contributors as creators too. Figma will only attribute the plugin to the organization if or when it's published to the organization's community profile.
Public
Community profiles showcase files and plugins shared with the Figma Community. Figma supports Community profiles for creators, teams, and organizations.
If you are an admin of a team or organization, you can publish plugins to those profiles as well as your own.
To publish plugins publicly:
Set the Publish to setting to Community to create a public plugin.
Set the Creator to Organization name to publish to the plugin to the organization's profile. You can then list any other contributors, as long as they have an existing Community profile.
Note: If you have a Figma account under a company email, your organization will have ownership over the contents of your Figma account. If you want to retain ownership of the plugin, we recommend creating a profile under a personal Figma account. Learn who can publish files and plugins →
Every file and prototype in Figma has a unique URL. In an organization, members can copy this link to quickly share designs and prototypes with other members of the organization.
Members can interact with a file based on the file's link sharing permissions, regardless of whether they're a member of that team or project. If public link sharing is enabled, members can also share files with people outside the organization.
A file's link sharing settings control who can open a file or prototype (access) and what type of actions they can take (permissions).
The default settings for the Organization plan is Anyone at organization with link and can view. You can update the link sharing settings for each file.
Discovery
can edit
can view
can view prototypes only
Anyone with the link
✕
✓
✓
Anyone at organization with link
✓
✓
✓
Anyone at organization
✓
✓
✓
Only people invited to this file
✕
✕
✕
Access
Choose how members can find files in the organization.
Anyone with the link: anyone inside or outside the organization can access the file. All they need is a link to the file.
Anyone at organization with the link: only members of the organization can access the file. Members can only access the file is they open a link to that file.
Anyone at organization: members can find this file when browsing and searching. Use this setting to share libraries with the organization. Guests can't access these files unless you invite them to the file or team.
Only people invited to this file: only the members or guests you invite to that file, or the team it lives in, can access the file.
Note: Organization admins can disable public link sharing for the organization. This removes Anyone with the link from the link sharing options and prevents anyone outside the organization accessing files via link sharing.
Permissions
The link sharing permissions control what level of access someone has when they access a file using the link. This only applies to anyone who access the file via a link, not team members or people invited to the file.
Can edit: anyone who opens the file can get edit access.
Can view: anyone who opens a file link can only view the file.
Can view prototypes only: anyone who opens the link can access any prototypes on that file, but not the underlying pages in the file.
The file's link sharing permissions will dictate the file experience for anyone who opens a link to that file. Whether they can actually edit the file depends on their Figma design or FigJam role.
Can edit files
If the link sharing settings are set to can edit, members are to get edit access to the file. Members or guests will see an Edit file button next to the file's name in the toolbar.
What happens next depends on the person's Figma design or FigJam role:
Editors can click Edit file to start editing the file right away.
Viewers can click this button to upgrade to a paid editor role and edit the file. This doesn't affect their permissions on other files or teams. Figma will include them in the organization's next quarterly true-up.
Viewer-restricted members or guests can click Edit file to request an upgrade. This sends a request which organization admins can approve or deny. They can only edit the file once an admin accepts the request. Request upgrades →
When members open an organization file, Figma will give them can view access by default. This prevents members from being accidentally upgraded when they view a file. There are only some actions you can perform with can view access:
Click the Hand tool to pan around the canvas
Click the Move tool to select layers in the canvas or layers panel
Click the to add comments
Measure distances between layers and objects
View layer properties in the Inspect panel
Copy the contents of any text layers
Copy frames, components, objects or layers within files.*
Note: Actions with an asterisk* are only supported if the Allow viewers to copy, share, and export from this file setting is on. Restrict who can copy and share files →
Update file settings
We recommend confirming your link sharing settings in the Share modal before you share your file.
File URLs stay the same regardless of their location or link sharing settings. It's not possible to set temporary links, custom URLs, or passwords for files or prototypes.
Click the Share button in the file.
Click the next to the link sharing setting to choose how people can find and access the file.
Click the to set the permissions for sharing links.
Click the next to Anyone else with a prototype link to set a permission for any prototypes in the file..
Check the box if you want the URL or embed code to Link to selected Frame (optional).
Click Copy Link to copy the file URL to your clipboard. If you're using Figma in the browser, you can also copy the file link in the address bar.
The Branches modal lets you see all Active and Archived branches, as well as any branches that you created (Yours).
