
It is a quiet new setting, but one that will make plenty of admins lives easier. Figma just announced that admins can now set an AI credit cap specific to each user within a team or organization.
In practical terms: an individual "Custom credit limit," adjustable per person, with a built-in request mechanism when someone needs more. No more all-or-nothing setup where either everyone shares a common pool with zero visibility, or everyone gets unlimited access that can quickly spiral.
The concept is simple to grasp, but incredibly useful in practice.
This approach turns a global AI budget, which can be hard to track, into named, traceable management. Each user becomes accountable for their own usage, without being blocked if they have a genuine one-off need.
This feature is part of a string of recent updates around AI credit management: a usage API for enterprises, billing group controls, and on-demand credit purchases on the Professional plan. Figma is methodically building a financial admin layer around its AI tools, a sign that usage is exploding and organizations are asking for more granularity.
| Before this update | After this update |
|---|---|
| AI budget managed at the team wide level | Individual, adjustable cap per user |
| A single power user can drain the whole budget | Predictable, traceable usage per person |
| Informal requests to raise limits (Slack, email) | Request workflow built directly into Figma |
At Mazette.co, we use Figma every day to design interfaces before building them in Webflow. And on this kind of feature, our verdict is clear: this is excellent news, and a very pragmatic one at that.
Why? Because AI credits, however powerful, come with a real cost that can climb fast at team scale. Without fine grained control, you end up with two unsatisfying scenarios: either you restrict everyone out of caution and stifle creativity, or you let usage run free and discover the bill at the end of the month.
This individual cap system with a credit request option changes the game. It gives every designer or developer autonomy without losing budget control. And more importantly, it builds accountability: everyone knows where they stand, and a justified request gets approved more easily than unrestricted access by default.
The only catch is that this feature is mainly aimed at larger organizations, with a dedicated admin who has time to review these requests. For a small team or a freelancer, the benefit is more limited. But for our enterprise clients scaling their AI usage on Figma Make or image generation, this is exactly the kind of safeguard that reassures finance teams without frustrating creative ones.
A quiet update, but a step in the right direction: more control without sacrificing flexibility.
Code