Custom role credit limits
Custom roles can include an optional monthly credit limit. This limit controls how many Hatz Credits each assigned user can use during the calendar month.
If a custom role does not have a credit limit, users assigned to that role are not capped by the role itself. They are still subject to the tenant's overall usage limits and any other limits that apply to the feature or request.
To learn more about creating and managing custom roles, see the Custom Roles support guide.
How limits are enforced
Usage warning: Users may see an in-product warning when they have used most of their monthly role limit.
Request start: If a user is already at or over their role limit, new credit-consuming actions may be blocked.
In-product messages: Users may see a banner or message that they have reached a monthly usage limit and should contact an administrator.
Long-running work: Some longer operations may stop if the user reaches the applicable limit while the operation is running.
Who can set credit limits?
Admins and users with permission to manage roles can set credit limits on custom roles. Available role-management options depend on the user's admin level and tenant scope.
Use limits with Auto Mode controls
Role credit limits are hard monthly caps. They are useful when a team needs a clear spending boundary, but they work best when paired with proactive controls that reduce usage before users hit the cap.
For higher-volume users, consider using Auto Mode and limiting the Auto Mode options available to that role, such as keeping the role on lower-cost modes when that fits the team's work. Admins can also disable higher-multiplier models that a role or tenant does not need. These controls help keep everyday usage lower without relying only on a hard stop at the monthly limit.
Key considerations
Monthly usage caps: Role limits are useful when admins want stronger usage caps for a group of users.
Hard cap behavior: If a user reaches the role limit, new credit-consuming actions may be blocked. The limit does not automatically switch the user into a cheaper mode after the threshold is reached.
Custom roles only: Credit limits are configured on custom roles, not on every built-in role.
Per role: Users assigned to the same custom role use the same role limit. Create separate roles when different groups need different limits.
Tenant limits still apply: A user can be blocked by their role limit even if the tenant still has credits, and a tenant can be limited even if the user's role limit has not been reached.
Zero blocks credit usage: Setting a role limit to zero prevents users on that role from using credit-consuming actions.
Review after changes: If you change a role limit, review current usage in the users and roles views so admins understand whether assigned users may still be close to the new limit.