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, view 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 seats 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.
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
Action |
Can view | Can edit |
---|---|---|
✓ | ✓ | |
✕ | ✓ | |
✕ | ✓ | |
Can create team, but not any files in that team | ✓ | |
✓ | ✓ | |
✓ | Not applicable | |
✕ | ✓ | |
Invite people to teams, projects, or files |
With can view access only | ✓ |
In drafts | ✓ | |
In drafts | ✓ | |
✕ | ✓ |
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 |
✓ | ✓ |
✓ | ✓ | |
Move, edit, or delete layers |
✕ | ✓ |
✓ | ✓ | |
✓ | ✓ | |
Edit design and prototype properties |
✕ | ✓ |
In drafts only | ✓ | |
✓ | ✓ | |
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 |
✕ | ✓ |
✓ | ✓ | |
✓ | ✓ | |
✕ | ✓ | |
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
Action |
Can view | Can edit |
---|---|---|
✓ | ✓ | |
✕ | ✓ | |
✓ | ✓ | |
✓ | ✓ | |
✓ | ✓ | |
✓ | ✓ | |
Copy objects on the board |
✓ | ✓ |
✓ | ✓ | |
✓ | ✓ | |
✓ | ✓ | |
Follow along in a file |
✓ | ✓ |
✓ | ✓ | |
✓ | ✓ | |
✓ | ✓ | |
✕ | ✓ | |
✕ | ✓ | |
Create stickies, shapes, connectors, and text |
✕ | ✓ |
✕ | ✓ | |
✕ | ✓ | |
In drafts | ✓ | |
Insert strong blocks, widgets, or media (Images, GIFs, videos, links) |
✕ | ✓ |
✕ | ✓ | |
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 seat and not their team permissions—determine if they can edit FigJam or design files.
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 seat type. Team admins need to downgrade someone to a viewer-restricted seat to remove them from the team's billing.
On paid plans, projects have their own access settings. This means that a person’s team permissions don’t always reflect what they can access in a project.
A person can have different permissions at a team, project, and file level.
Let’s explore this with an example: Vanessa creates a project in the Growth team. On the project, she sets the team access level to can view. 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 a full seat.
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).
Action | Can view | Can edit | Team admin |
With can view permissions only |
✓ | ✓ | |
With can view permissions only |
✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✕ | ✓ | |
✕ | ✕ | ✓ | |
✕ | ✕ | ✓ | |
✕ | ✕ |
Only the team owner can transfer ownership |
|
✕ | ✕ | ✓ | |
Upload and manage team fonts (Organization and Enterprise plans only) |
✕ | ✕ | ✓ |
View and manage Figma design and FigJam seats (billing status) |
✕ | ✕ |
✓ Professional plan only |
✕ | ✕ | ✓ Professional plan only |