All the problems mentioned in this thread are big issues for me as well as an organization administrator. Wish they would be addressed.
I agree itâs cumbersome but you donât have to uncheck it per member, you have to uncheck it per file.
There are more files than members (10,000+ in our org I guess). Unchecking it one by one is not realistic, donât even say I canât uncheck some files even as an admin.
well, I never imagined such a number of files 
so I stand corrected
Thereâs seems to be zero movement on this issue and it really needs to be addressed, have Figma commented on this being looked into?
nope⌠
iâve always had the feeling that if huge companies like Google and Microsoft are using Figma, they
a) donât have a problem with budget
and/or
b) have their own (expensive) processes to ensure not everybody can edit everything
and/or
c) they have multiple organizations within their organization (which doesnât really fix the issue
In any case, whatâs more annoying about the silence from Figma regarding this topic, is that they donât even want to share best practices or examples from other companies how to work around it. Probably because it would be like admitting the system is flawed.
In order to work with them, our customers require an ISO 27001 security standard for summary. So unfortunately I canât push the Figma tool within our teams until a precise management of users and shares is possible.
(And also, not until Figma Token is natively integrated ^^)
All these issues mentioned in this thread are an issue for me too being the one that has volunteered to be the admin for our company, thinking it would not be too much work. Our user group is getting so large now that it is impossible to have control.
A new question that that arose today from a user was âhow do I downgrade myself from editor to viewer-restricted?â. This is not possible as far as I know and it should be. If a user realizes they no longer need editor access, but still want viewer access they should be able to downgrade themselves or at least click on a button to ask an admin to do it for them.
Well people, it finally happened. All these missing features, administration bugs and wonky access controls have finally been fixed!
Itâs just going to cost you an extra $30 per editor per month.
Welcome to Figma Enterprise 
1 Like
I just had my WTF! moment figuring this out as well, not the only one it seems. If this is true, and this is how they are going to play this, all goodwill will be out the window. Holy moly talking about being tone deaf.
P.s. although they are ignoring this (specifically created) feedback forum anyway, instead focussing on âthe 32 quick wins we heard you ask for on Twitterâ. SighâŚ.
Please comment, upvote, share, expand on this thread. I really donât want to have to change tools again but this is unacceptable and literally why we left our last tool. If they are pay-walling basic access controls I will not have anything to do with their platform.
1 Like
You know after all the kerfuffle regarding Enterprise and none of its features coming to Organization, it dawned on me that (AFAIK), even Entreprise seems to be missing one of the features that, when you think about it, would already bring this level of individual responsibility and consequent security that weâre all missing:
For every Figma member, show WHO invited them
You can now randomly find instances where the person who upgraded someone as editor is visible. And maybe some other examples. But not all.
Just show for every role change, including invitation as viewer, who was the initiator. At the very least, you can educate those âenablersâ with whatever Figma access policies you have at your company.
Hope another design tool beat FIgma.
Again cleaned up multiple editors from our Figma org who had joined using gmail and whatnot for Figma their account and had instantly upgraded themselves to editors. Someone must have had invited them so I guess they were not totally outsiders but itâs getting really painful to manage the Figma users and this security loophole is frightening.
I do understand that thereâs need for the Enterprise tier but it should be justified by feature set (i.e. workspace). Security cannot be part of that, it just needs to be present at all Figma plans.
2 Likes
EDIT: Apparently this change has been reversed: https://twitter.com/manosaie/status/1585155240872931328
Hey everybody, good news! /s
You were wishing to get more control over permissions in order to make adminâs tasks easier and have more control of editors? Best $Adobe can do is less control:
Figma last week pushed an unnanounced update where people can request to join Teams ONLY WITH EDIT RIGHTS, by default. They even removed the text field where people can write a reason to request access.
I repeat: every time a user request access to a Team, instead of having the option to request view and edit access, it will be sent with edit access, even if they donât need to edit anything. Try it yourself, click ârequest accessâ in any team youâre not in.
Hereâs the official statement from support after we contacted them thinking this was a bug (so naive of us!)
EDIT: Apparently this change has been reversed: https://twitter.com/manosaie/status/1585155240872931328
We have just upgraded to Enterprise and if anyone is curious, this requested feature is still NOT available.
@_Hal illustrated it perfectly:
I could swear I saw somewhere that Enterprise would allow to restrict who can invite others, but itâs still not available. Unbelievable for more than $70 per month per editor.
I canât believe that this is true. I just went to see where I messed up and found that there is no way to stop people without budget approval from just inviting others and ballooning the bill.