Sharing in Figma lets you collaborate across teams, folders, and files. This guide gives you a high-level overview of how sharing and permissions work.
Note: Starting August 3, 2026, projects are being transitioned to folders, with the rollout reaching all users over the next few weeks. Your content and access will remain the same.
What can you share?
You can share different kinds of assets in Figma: prototypes, files, folders, and your team or plan.
You can think of these as different levels of sharing—with the team or plan as the higher levels and a file or prototype as the lowest or most granular.
How can you share?
There are three main methods for sharing resources in Figma:
- Share a link to a resource
- Invite people to a specific resource
- Embed a file or prototype outside of Figma
Share links
The fastest way to share your work with collaborators is to send them a link. You can copy and share links to prototypes, files and folders.
On the Organization and Enterprise plans, you can also share a link to a single team. Starter and Professional plans consist of a single team, so if you invite someone to your team, they become full members of your plan.
If they already have access to the team, folder, or file they can interact with it based on those permissions or the link share settings. If they don't, they can request access.
- Share files and prototypes via link
- Share folders with a link
- Share teams on the Organization and Enterprise plans with a link
- Share Starter or Professional plans with a link
Send invitations
You can invite someone to a file, folder, team, or plan using their email address. They’ll receive an email invitation and a notification in their Figma account. To access the resource, they just need to accept the invitation.
- Invite to files to give them access to a single file
- Invite to folders to give them access to all files in a folder
- Invite people to a team to give them access to all files and folders in the team (Organization and Enterprise plan)
- Invite users to your Starter or Professional plan to add members to these plan types
- Add members and guests to an organization, or specific assets within the organization, on the Organization or Enterprise plans
Embed outside Figma
Embed files and prototype in a website or browser-based applications to bring your designs and prototypes to your team.
- Add style and component libraries in your design system documentation
- Include detailed feature designs and explorations in a PRD, spec document, or user story
- Keep your FigJam files alongside meeting notes
- Embed or share prototypes in testing environments
People can interact with embeds based on their permissions on that file. They’ll be prompted to log in to their Figma account if it’s a private file.
Learn more about embedding files or prototypes.
Understanding permissions
Permissions control what collaborators can do:
-
Can view: People with
can viewaccess can only perform certain 'read only' actions, like inspecting properties, following, and commenting. -
Can edit: People with
can editaccess can make changes to files and folders.
Permissions work at different levels:
- At the file level: Determines whether someone can view or edit that specific file.
- At the folder level: Determines whether someone can create and edit files and folders in the folder, or only view it.
- At the team level (Organization and Enterprise only): Determines what someone can do at the team level, such as creating folders, inviting members, or changing team settings.
Learn more:
Inherited and explicit permissions
When you give someone access at a higher level, like a team or folder, they’ll inherit permissions for everything inside it. For example, if a person has can view access to a folder, they’ll inherit can view access for files inside that folder.
You can also grant explicit permissions at a lower level. This allows you to give someone more access to a specific resource than they would inherit.
Example: James has can view access at the folder level. If you invite him to a file in that folder with can edit access, he’ll be able to edit that file, while still only viewing other files in the folder.
Permissions vs. seats
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.
Admin management of permissions
If you're an admin, you can adjust permissions on resources you already have access to.
Learn more about changing permissions as as admin.
Troubleshooting access
If someone can’t access a resource, check these common causes:
- Team vs. folder access: Being in a team doesn’t always guarantee folder or file access. Confirm their permissions at the correct level:
-
Seats vs. permissions: On paid plans, a collaborator needs both the correct seat and
can editaccess to edit a file. Users can request both file access and seats. Seats will only be approved according to admin’s seat approval settings.