Organization plan permissions

Who can use this feature

Applies to organizations on the Organization plan.

On the Organization plan, you can share assets at five different levels: organization, team, projects, files, and prototypes. As this is a paid plan, you also have access to these extra sharing settings:

• Share just a prototype and not the file
• Restrict viewers from copying, sharing, or exporting
• Add password protection to files
• Authenticate members with your identity provider (SAML SSO)

Organization

Organization admins can use account types and seat types to manage access to the organization. Any access to individual teams, projects, or files is controlled by their permissions ↓.

Account type

A person’s account type controls what resources and settings they can access. There are three account types: members, guests, and admins.

Seat type

A person's seat type determines which Figma products they have access to.

Seat	What's included
Full	Full access to all Figma products, including Figma Design, Dev Mode, Figma Slides, and FigJam.
Dev	Full access to Dev Mode, Figma Slides, and FigJam. View and comment access in Figma Design files.
Collab	Full access to Figma Slides and FigJam. View and comment access in Figma Design files. No access to Dev Mode; basic inspection only.
View (free seat)	View and comment access to Figma Design, Figma Slides, and FigJam. No access to Dev Mode; basic inspection only.

Learn more about seat types at Figma. 

Permissions

A person's permissions control their access to individual teams, projects, and files within the organization.

Read our Guide to sharing and permissions for more information on how sharing works in Figma.

Teams

Teams in an organization have an audience access setting. This controls how members of the organization can find and join the team. 

• [Organization name]: Anyone in the organization can access the team.
• Only those invited: Only users explicitly invited to the team can access it. If the team is limited to Only those invited, you’ll need to choose from one of the following visibility options:
  • Visible: The team can be found by organization members from the file browser. Members can ask for permission to join a visible team.
  • Hidden: The team cannot be found by search. Members must be invited by an existing member. 

Organization members can join multiple teams in the organization. To control what access each member has to the team, they have team permissions.

Team permissions are the same across all team types: can view, can edit, andadmin. Teams also have one owner.

In an organization, team permissions only control what team-level actions people can take. Whether someone can edit files depends on their seat type and permissions. 

Team actions

This table includes a list of common team-level actions and tasks in Figma. Use the icons to see 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	✕	✕	✓

Projects

In addition to audience access settings, every project has a team access setting. This determines what access team members have to that project.

In an organization, only the project owner or those with can edit permission can change a project's team access. 

• Can view: Team members can only view files in this project, even if they have can edit permissions on the team. 
• Can access (default): Team members can access the project based on their team-level permissions. For example, if a user has can view team permissions, and the team access level for the project is set to can access, then the user has can view access on the project.
• Remove team access: Remove a team’s access to a project. If you remove a team’s access to a project, team members can only access the project if they have already been directly invited or if project owner invites them afterward. You can re-add team access to the project at any time. 

Team files

On the Organization plan, access to team files is based on a person's team permissions. 

• Restrict viewer actions: By default, anyone with can view access to the file will be able to copy and share the file and its contents. On paid plans you can restrict viewers from copying, sharing, or exporting from the file.
• More audience settings: Team files also have default permissions for link sharing. Anyone who accesses a file from a link gets those permissions. Files in an organization have extra link sharing options, to make it easier to find and access organization resources.
  There are two aspects of link sharing: access and permissions. On the Organization plan, you have the following link sharing settings.

Access	Can edit	Can view
Anyone: Anyone inside or outside your team or organization can access the file if they have the link.	✓	✓
[Organization name]: 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 invited people: Only people you explicitly invite to the file, or the team it lives in, can access the file.	Access based on user's permissions

Drafts

Everyone has access to draft files, which are separate from their team files and projects. On the Organization plan, people can invite collaborators to files in their drafts with can view or can edit permissions.

If someone with a View seat shares a file from their drafts, they will be prompted to request a seat upgrade.