Full-seat user has only View access when I invite "Anyone in [team name]" to folder

Hi ​@JosephxBrick, thanks for reaching out! 

When did you invite your entire team to this folder? And has this user been actively online attempting to retrieve their edit access?

Users typically need to accept the invitation then refresh to see the changes reflected on their account. 

Again, this user has been a team member with a full seat for years. The entire team is invited to the folder. When I hit the share button with the folder selected, it shows that everyone in the team can access. However, when, in the share popup, I show the listing of everyone in the team, he has just view access, while other team members with full seats have edit access. Arnold is the user in question below, and as you can see he’s accepted the invite.

He had access on Friday, but not today, and I’ve changed nothing about permissions.

Here is Admin > People:

The entire team has been invited to this folder for months. There is only one Arnold on the team.

Thanks for the additional context, ​@JosephxBrick! 

It looks like Arnold accidentally accessed the team with two separate email addresses. His full seat is actually associated with a gmail email address, and his ingenuix email address only has Guest view access for the Ingenuix team. Be sure he’s accessing the folder using the correct email. 

Yes, but he doesn’t have two users in Admin > People with two different email addresses. He has only one entry, which is associated with his gmail. This illustration might prove helpful.

Again, everything was working on Friday. This is new today. He has no edit access when signed in with his gmail account.

In the listing shown in the bottom right image above, other users with full seats are shown as having edit access. Plus, how he is signed into the account should have no bearing on the list above in the bottom right image, correct?

I was able to work around this by inviting him to the file in the project that he needed to access (which I don’t like doing because it’s unwieldy to manage permissions that way. I know Figma has been revamping its permissions, so maybe something got messed up here.

I am engaged with Figma support. I will post the response here.

Glad to hear you found a workaround, Joseph! 

I’ve flagged this over to the team investigate, if anything has changed within inherited permissions to ensure this doesn’t happen again to you or anyone else in the future. 

Hey Joseph, the team took a deeper look on the backend, and it looks like Arnold still has can view permissions on the team level, which is overriding any can edit access for specific files that should be inherited for the folder.

Since you invited Arnold directly, this is now forcing the explicit can edit access for this file over his inherited can view permissions on the team. Please note that team permissions will be prioritized over project permissions

For any other users in the team that will need broad can edit permissions to inherit down to projects, if the projects are set to open team access, you can follow this guidance to update team members permissions: https://help.figma.com/hc/en-us/articles/360039485514-Manage-team-permissions