Prefer English?
Prefer English? Switch the website language for a better experience.
Figma keeps expanding its admin console. This time, it is not a feature visible to designers, but a foundational update for organizations managing dozens, even hundreds, of Figma seats. Four new controls are rolling out on Enterprise plans, all designed to regain control over three sensitive areas: AI costs, access, and automation of repetitive tasks.
Here is exactly what is changing.
Since paid AI credits arrived in Figma (for Figma agent, Figma Make, or other generative features), budget control naturally became a concern. Until now, managing this user by user was a headache for any large organization.
Admins can now set a default cap at the level of the entire organization or a specific billing group. This cap automatically applies to any new user, as well as to those without a custom limit. A simple safety net that avoids nasty surprises at the end of the month.
For organizations that already manage their access through an identity provider (Okta, Azure AD, and others), Figma now lets you configure AI credit limits directly from that tool for users managed via SCIM. The idea: centralize access governance in the same place as the rest of your IT stack, without juggling multiple interfaces.
This is arguably the most significant point for an organization's security. Until now, a team member could create their own Starter or Professional plan using their work email address, completely outside any oversight. The result: potentially sensitive work files, off the admins' radar, and fragmented billing.
The new option to control external plan creation closes this gap. All design activity stays tied to the organization, which simplifies auditing and compliance.
Finally, Figma is opening new admin REST APIs to create and manage teams, folders, and files programmatically. Good news for IT teams orchestrating onboarding and offboarding at scale, or looking to sync their Figma organization with other internal tools.
| Control | What it solves | Who it is for |
|---|---|---|
| Default AI limits | Automatic budget control | Organization and billing group admins |
| AI management via SCIM | Centralization with existing IT | IT and security teams |
| Blocking external plan creation | End of ghost accounts | Enterprise admins |
| Admin REST API | Automation of recurring tasks | Internal technical teams |
{{webdesign}}
At Mazette.co, Figma sits at the heart of our daily method, from exploration all the way through to handoff to Webflow. So naturally, this announcement speaks directly to us, even though it is primarily aimed at larger accounts.
At its core, this is good news. Ever since Figma shifted part of its AI features to a paid credit system, budget control has become a central concern for any organization managing multiple licenses. Setting default caps is simply good operational sense: it avoids unpleasant surprises on the bill and encourages accountability without having to micromanage every single user.
Blocking external plan creation strikes us as equally relevant, and arguably a bit overdue. How many organizations have orphaned Figma files out there, created by an intern or freelancer using their work email, invisible in the admin console? This security gap is common, and closing it is a no-brainer for any organization that cares about design governance.
The new admin REST APIs are particularly interesting from an agency standpoint: automating the creation of teams and folders for every new client project saves valuable time during onboarding. This is exactly the kind of optimization that, combined with other automations (Zapier or Make, for example), turns a patched-together Figma setup into a real system.
The only drawback: these controls remain limited to Enterprise plans. Smaller organizations, often the most exposed to shadow IT risks, will not have access to them. We hope some of these building blocks, particularly AI credit control, eventually make their way down to Organization plans.
Either way, this confirms a broader trend: Figma is no longer just a design tool, it is a full-fledged IT platform that needs to be managed as such. One more good reason to properly structure your Figma organization from the start, especially if you are planning a Webflow redesign involving multiple teams.
Code
Over 180 companies have already stepped out of the shadows with us.
Figma is adding four features for Enterprise admins: setting default limits on paid AI credits per user, managing those limits via SCIM, blocking the creation of Starter or Professional plans with a company email address, and new REST APIs to automate team, folder, and file management. This rollout is arriving gradually across Enterprise plans.
Admins can now set a default cap on paid AI credits at the organization or billing group level. This limit automatically applies to all new or existing users who do not have a custom quota. For accounts managed through an identity provider, this can also be handled directly via SCIM.
Without any control, a team member could create a Starter or Professional plan using their work email address, outside the scope managed by the organization. This creates files invisible to admins and risks around security or shadow billing. The new option to block external plan creation closes that door, keeping all design activity under one roof.
Impactful titles, polished meta descriptions, sitemaps, Schema.org, Hn structure, and audits: these are the SEO foundations that make your content readable by both Google AND generative AI. We cover both simultaneously.
With over 180 clients, our agency is one of the few in France to hold the Webflow Premium Partner label, supporting you in every area, including custom web design, sophisticated automation, conversion optimization, and SEO and GEO visibility.
We create bespoke web designs focused on performance, user journeys, and conversion. Join over 180 clients who have trusted us to elevate their brand.
