Add all Figma provisioners and deprovisioners by department
Why is this change being made?
As part of our upgrade to Figma Enterprise, we now have the ability to use the Billing Groups feature. This feature allows us to identify specific admins per billing group. These admins are responsible for:
- Provisioning users
- Deprovisioning users
- Managing departmental spend for their department
- Confirming seat counts during quarterly true ups
- Confirming seat counts during yearly renewal
- Projecting seat counts for the FY
Current billing groups are set up with the following admins:
Billing group | Billing admin |
---|---|
R&D: Development | @samdbeckham |
R&D: Product | @tauriedavis @jeldergl |
Sales: Customer Success: SA | @simon_mansfield |
Marketing: Brand & Product Marketing | @amittner |
Marketing: Integrated Marketing* | TBD |
Marketing: Marketing Ops | @amy.waller |
Marketing: Growth | @s_awezec |
*Integrated Marketing includes both Digital Experience and Digital Strategy teams.
This MR ensures all admins/provisioners are included in the tech stack. It also lists @tauriedavis as business owner, as she is responsible for finalizing annual renewals/true ups.
Tech Stack - Update Existing System
Business/Technical System Owner or Delegate to Complete
Please do not merge before the Business Systems Analysts have reviewed and approved.
-
Rename this MR's title to [System Name] - Tech Stack - Update Existing System
-
Update data field(s) for the existing system within the 'Changes' tab of this MR. Commit update when ready. More instructions are here.
Are you changing the existing system's provisioner(s)?
-
Yes. Create an Issue to add the new provisioner(s) of the system to the appropriate Google/Slack/GitLab groups: - [Issue link]
-
No
Are you removing an existing system from the Tech Stack?
-
Yes. Be sure to complete a Tech Stack Offboarding Issue as well. -
No
Security Risk to Complete
Not required prior to merging
-
Once updates are finalized and if necessary, communicate change to impacted parties (e.g., Security Compliance)
/cc @gitlab-com/gl-security/security-assurance/security-risk-team