With the admin updates that came out on March 11, there is one new feature that we would like removed or able to be turned off by an org admin.
When a user requests an upgrade in Figma, this new feature allows the user temporary access to the functionality of that seat for 3 days (unless the admin replies to the upgrade request sooner). Here is the description from this article:
To ensure users aren’t blocked from collaborating while admins review their seat request, they’ll be able to use the functionality of the seat they requested temporarily for up to three days. During that time, they can create new files and edit any files where their teammates have given them edit access. They will not be able to edit files they do not have edit access to. The temporary access ends immediately if the request is denied or expires.
Prior to the updates on March 11, this was the behavior for dev mode requests -- users would get temporary dev mode access for a short amount of time while they waited for their dev mode request to be approved/denied. This did cause some confusion/frustration for devs and admins, but not as much as it does now with Full (aka Editor) upgrade requests.
This poses issues in our org for three reasons:
- Risk: We have strict controls in our org as to who has editing capabilities. We need to ensure that only approved users are able to edit files.
- User confusion/frustration: We have had instances where a user thinks they have been upgraded to a Full seat because they are able to make edits for a few days. But then their editing access is taken away after 3 days, and they are confused/frustrated and come to the admins to ask why.
- Admin frustration: When the users mentioned above come to admins asking why their access was taken away, we have to explain that it was temporary. And in most cases, we cannot actually give them a Full license. This is not enjoyable for an admin to have to do multiple times a week.
Suggested solutions:
- Remove this temporary 3-day access feature.
- Make this temporary 3-day access feature able to be turned on/off at the org level by an admin.
Thank you!