Branch and merging devs role

Generally speaking, if a member of an organization with Full design seat is invited to a team, the member will have edit access to all the projects and files inside that team, unless there are explicit settings applied to certain projects, such as invite-only projects or view-only projects which require specific permission to be given to that member to be able to access or edit the files inside the project.

If your organization members are having difficulty accessing / editing within certain projects or files, please let us know and we can have support help you identify what’s going on.

Figma honors explicit permission over inherited permissions. As an example, even if a user has edit access to a team, if a particular project is a view-only project, the user can only view the files in that project. The team admin will then need to give that user explicit permission to be able to edit the files in that project.

I understand it can take some time to understand how Figma’s roles, permissions, and accesses all come together. I recommend that you take some time to go through these helpful Help Center articles.

• How seats (full, viewer, viewer-restricted) work and what can they do / not do: If you want to understand what are some of the general accesses and permissions a Full seat user has, please refer to the table under “General” (good for understanding viewers and viewer-restricted seats as well!)
• Team permissions: This article is helpful in understanding how team permissions work. I recommend going through the topic on “Permissions” (make sure you’re referring to the guide for Professional, Organization, or Enterprise).