Understanding Sharing Permissions

Note: If you are part of an Organization using Figma then your sharing permissions are slightly different. Learn more about Organization Permissions in our Member Management section.

In this article, we will only cover the Permission levels in Figma. For more information on sharing your Files or inviting collaborators to Projects, check out our Sharing Files and Sharing Projects articles.

To support collaboration and improve design workflows within Teams, we have Permissions. Permissions control how other collaborators can interact with your Files and Projects.

You can set a collaborator's Permissions when you first invite them to a resource. Or, you can update their access to a Team, Project or File as you need.

There are four different levels of access, or Permissions:

  1. Viewers
  2. Editors
  3. Admins
  4. Owners

You can set Permissions at a Team, Project and File level. 

This means a collaborator can have different Permissions for individual Files and Projects.


Viewers have "Can View" access to a Team, Project or File.

Viewers can only view or comment on any Files or Prototypes you invite them to. They are not able to make any changes or modifications to any objects or properties within a shared File.

When you invite someone to a Team as a Viewer, they will have "Can View" permission to any Team Projects and Files.

Viewers Can

  • Click on objects within a design to view their Properties.
  • View the CSS Properties of a selection in the Properties Panel (Developer Handoff).
  • View and interact with Prototypes.
  • See and use redlines to measure distances.
  • Copy the contents of Text objects.
  • Save and/or duplicate Files.
  • Use Components from Files they are a Viewer on, but only in a File they are an Editor on.
  • Export Assets.
  • Comment on any Files or Prototypes you invite them to.

Viewers Cannot

  • Move, scale, edit or change any elements of a design.
  • Use, publish or change any Master Components within a Team Library.
  • View the Version History of the File.
  • Share any Files from their Drafts.

Note: If you aren't logged in to a Figma account, you can still view Files with Public Link Access. This won't give you the same level of access as a "Viewer".

You won't be able to interact with any layers or objects, or make comments. But you can pan around the canvas or adjust the zoom level. 


Editors have "Can Edit" permissions to access to a Team, Project or File. 

When you invite someone to a Team as an Editor, they will have  "Can Edit" permission to any Team Projects and Files.

Like Viewers, Editors are able to view and comment on any Files. They can also make changes to the File, including any elements or properties within the File.

When working in Teams, the number of Editors on your Team will impact your billing for that month (or year for Annual plans). Learn more about plans and pricing in our Choosing a Figma plan article.

Editors Can

  • Move, scale, edit or change any elements or properties of a design.
  • View, interact with, or edit Prototypes.
  • View, use and publish changes to Styles or Master Components within a Team Library.
  • View, add, duplicate or restore previous versions from the Version History.
  • Share Personal Files from their Drafts.
  • Move, Rename, Delete or Restore a File.
  • Invite other collaborators to a Team, Project or File as either Viewers or Editors.
  • Upgrade Viewers to Editor roles. Or, downgrade existing Editors to Viewers.
  • Create Private Projects (Professional Teams only).
  • Upgrade a Starter or Student Team to a Professional Team. This is done by entering their card details and will also change their Permissions to Admin (see below).

Editors Cannot

  • Invite others to the Team as Admins.
  • Change who the Team Owner is.
  • Access the Admin Dashboard of a Professional Team.


Within a Team, you can also give collaborators Admin access. This gives them extra administrative rights within the Team.

Admins have access to both your Team Settings and the Admin Dashboard. Any Admin can manage your Team's billing via the Admin Dashboard.

You can upgrade any Editor to an Admin.

Admins Can

Admins can do everything that Editors can, as well as:

  • Invite others to a Team as Admins.
  • Remove members from the Team.
  • Enable Shared Libraries in Teams.
  • Manage Shared Fonts in Teams.
  • View the Admin Dashboard.
  • Downgrade Editors to Viewers. Or downgrade other Admins to Viewers or Editors.
  • Update the payment source to other billing details.
  • Downgrade the Team to a Starter Team.
  • View Past Invoices for the Team.

Admins Cannot

  • Transfer ownership of the Team to another member.

Note: Admins are still considered as collaborators with Can Edit access (Editors). Figma will bill your Team for any Admins on your account. It's not currently possible to add someone to Figma in a "buyer"or purely administrative role.


Anyone who creates a Team, Project or File will be the Owner of that resource.

  • There can be only one Owner for each resource.
  • The Owner can invite other collaborators to their Team, Project or File, at any Permission level (Viewer, Editor or Admin). 
  • An Owner can transfer ownership of a File, Project or Team to any Admin, Editor or Viewer with access to that resource. This can only be done by the current Owner.
  • When a Team member leaves a Team, any Files or Projects they owned will be transferred to the Team owner.
  • If the Owner leaves the Team, they will need to transfer ownership to another Team member or collaborator.
  • Only the Owner of a resource (Team*, Project or File) will be able to use Delete forever to delete it permanently. 
  • Editors will be able to Delete Files or Projects, but these are still accessible to the Owner in their Deleted Files folder.

*If you are within a Figma Organization, anyone with Admin privileges in the Organization will be able to delete a Team. Learn more in our Team Management for Organizations article.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.