Figma provisioners/deprovisioners are found in the Tech Stack YAML file.
While multiple departments have team members with Editor roles as paid seats, the UX department is responsible for provisioning and deprovisioning all seats.
Due to how Figma manages seats for our current Organization plan, any existing Editor is able to add a member as a paid Editor at any time. For this reason, we utilize a spreadsheet to track approved Figma seats.
All approved seats should be listed in the spreadsheet and include:
This spreadsheet is also used to assist in our quarterly audits. Once an Editor seat is deprovisioned, the team member should be removed from the spreadsheet.
Every approved Figma seat must have a corresponding access request issue with budget approval. Provisioners will be pinged in the access request issue to grant access.
As a provisioner, ensure:
Our billing cycle includes quarterly true-ups. Each quarter, admins receive an email informing them of the upcoming invoice. This gives them an opportunity to review added seats before approving the new invoice.
To audit seats:
@gitlab.com
email address, remove them from the organization.Hey [name] :wave: I am responsible for Figma billing/seats and I see you were added as an Editor recently. I am trying to track down your access request issue. Does this exist? If not, I will need to revoke Editor access until a seat is approved as part of the budget.
Deprovisioners are included on offboarding issue templates.
Admin settings > Members
section. Use the ellipsis (⋯) menu to the right of the member's information and select 'Remove'.For more information, refer to Figma's Remove people from an organization documentation.