Before you start
Who can use this feature
Available on Organization and Enterprise plans
Teams are shared spaces for organizing and collaborating on files. Every team contains folders, and every folder contains files.
You can set permissions on a team to control who can reach it and what they can do once they're there.
Learn more about sharing and permissions in Figma.
Note: Organization and Enterprise plans support an unlimited number of teams.
Starter and Professional plans have a single team, which is called your plan. You'll still see the word "team" in a few places in the file browser, but there are no separate teams to create or share on these plans. On Starter and Professional, you invite users to join your plan, and then set their access permissions on the folder and file level. If you invited somebody directly to a folder or file instead of to your Starter or Professional plan, they join the plan as a limited access member.
Overview
Team permissions define what someone can do at the team level, like creating folders, inviting members, or changing team settings.
Open the team share modal
Team permissions are managed through the team's share modal. To open the team share modal:
- Open the file browser by logging in at figma.com. If you're in a Figma file, click the Figma menu > Back to files.
- Navigate to the team:
- On the Organization or Enterprise plan without workspaces enabled, select All teams from the left sidebar, then select a team.
- On the Enterprise plan with workspaces enabled, select All workspaces from the left sidebar, then select a team from the Your teams tab.
- Click Share.
What each permission means
On the Organization and Enterprise plans, any member of a team is given can view or can edit permissions on that team.
In addition to can view and can edit permissions, a team member can be an owner or an admin:
- Admin: Admins have extra administrative rights within the team. They can manage any team settings, including shared libraries.
- Owner: Every team, folder, or file has an owner. There is only one owner per team. The owner is the person that created the team, but ownership can also be transferred.
The table below outlines which team actions are available for each permission level:
| Action | Can view | Can edit | Team admin/Owner |
|---|---|---|---|
| Invite others to the team | With can view permissions only | ||
| Create folders | |||
| Move files and folders | |||
| Delete team files or folders | |||
| Update team names or descriptions | |||
| Remove members from the team | |||
| Change the team name, icon, or description | |||
| Update collaborator permissions on the team | |||
| 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 |
How access is organized
The team share modal shows everyone who can access the team, organized from broadest to most specific:
- Audience access: who can reach this team across your organization or workspace
- Individual user roles: people and user groups who have been directly invited to this team
Click on any row in the share modal to adjust permissions for that group. These two groups work differently from each other. See each section below for more details.
Audience access on a team
Audience access controls whether your wider organization or workspace can reach a team, and what they can do when they get there.
You choose this when you create a team, and you can change it at any time.
To set audience access on a team:
- Open the team share modal.
- From the Who has access dropdown, select the top row to determine who can access the folder:
-
Only those invited: Only people you explicitly invite can access the team. Then, control if people in your organization who haven’t been invited can discover the file by setting team visibility:
- Visible: Members can discover and request access in the file browser.
- Hidden: The team cannot be found by search. Members must be invited by an existing member.
- [Workspace name] (Enterprise plan only): Allows workspaces members to access the team via link or through the file browser.
- [Organization name]: Select your organization name to allow members to access the team via link or through the file browser.
-
Only those invited: Only people you explicitly invite can access the team. Then, control if people in your organization who haven’t been invited can discover the file by setting team visibility:
- If organization or workspace access is allowed, choose a permission level under What they can do.
- Click Save.
Setting a team to Anyone in [organization] can edit lets organization members open the team and create files and folders within it, but every folder and file inside it has its own audience access setting. Some of them may be limited to invited people only. To give someone edit access to a team and everything inside it, invite them directly.
Example
The Produce team is set to Anyone in Produce Co can edit. It contains two folders.
- The Fruit Folder is set to Anyone in Produce Co
can edit - The Vegetable Folder is set to Only invited people
Jules is a member of the Produce Co organization. Nobody has directly invited him to the team or to either folder.
- Jules can open the Produce team, because audience access on the team covers everyone in the organization.
- Jules can open Fruit Folder and create files in it, because that folder has its own audience access set to Anyone in Produce Co
can edit. - He can't see Vegetable Folder, because that folder is limited to invited people.
If Jules were invited to the Produce team directly instead, he'd have an individual user role, and he could open both folders and everything inside them.
Individual user roles on a team
An individual user role is access you give to a specific person or group on a team by directly inviting them.
To invite someone, open the team share modal, enter their email address, and choose can edit or can view. You can also enter the name of a user group — everyone in the group gets the same permission, and access updates automatically when someone joins or leaves the group.
To change or remove someone's role:
- Open the team share modal.
- Use the dropdown next to their name to update their permission. Click Remove to remove them from the team.
People and groups with a role appear in the list in the share modal. This is the quickest way to tell how someone got access — if they aren't in the list, they're reaching the team through audience access instead.
Inherited user roles
Individual user roles on a team pass down to the folders and files inside it. Someone invited to a team with can edit gets can edit on the team's folders and the files in them, without anyone inviting them to each one.
You can give someone more access to a single folder or file than their team role gives them. You can't give them less.
Example
James has can view permissions on the Produce team. His manager, Vanessa, invites him to a specific file in that team with can edit access.
James can now edit that file. He still only has can view access to the other files and folders in the team.
Learn more about inherited roles on files and folders.
Frequently asked questions
They most likely have audience access to the team but no individual user role, and the folders and files inside are limited to invited people. Audience access doesn't pass down to a team's contents.
To check, open the team's share modal and look for the person in the list. If they aren't listed, they're reaching the team through audience access.
To fix it, choose whichever fits:
- Invite them to the team directly. Their role will pass down to everything inside.
- Add them to a user group and invite that group to the team.
- Change the audience access on the folders so your organization or workspace can reach them.
Seats are separate from permissions.
In Figma, a person's seat determines which Figma products they have access to. For example, a user with a Collab seat has access to FigJam and Figma Slides.
Permissions determine which files, folders, and teams they can edit.
For a user to be able to edit a file, they need both the appropriate seat and permissions.
No, team permissions do not impact your subscription or bill. Your bill is determined by your plan and the number of paid seats you purchase.