Custom role credit limits
Custom roles can include an optional credit limit — a monthly one, a weekly one, or both at once — controlling how many Hatz Credits each assigned user can use in that period.
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 generally, see the Custom Roles support guide. This article covers the credit-limit setting specifically.
Setting a limit on a role
Open the role in Users, Roles & Permissions and go to its credit limit setting.
Choose the period: monthly, weekly, or set both — each has its own cap and its own reset schedule, tracked independently.
Enter the credit amount for that period. Setting it to zero prevents anyone on that role from using credit-consuming actions at all.
Choose what happens when the limit is reached — Block or Auto only (see below) — and save.
Choosing what happens at the limit: Block or Auto only
Block — once the role's limit is reached, new AI requests won't start until the period resets. A request that is already running finishes normally unless it crosses the limit while it is running — see Long-running work below.
Auto only — the user isn't cut off. Instead they're switched to specific lower-cost Auto model tiers that you choose when setting up the role (e.g. Lite, Performance). This keeps the team working through a busy week or month while controlling cost — usage in Auto-only mode still bills normally, it's a model restriction, not a discount.
When each period resets
Monthly limits reset at the start of the calendar month.
Weekly limits reset every Wednesday at 12:00 PM Eastern — fixed, regardless of when the role's limit was configured.
What your team will see
Usage warnings: users see an in-app notification at 80% and 95% of whichever limit applies to their role.
At the limit: depending on your Block/Auto-only choice above, either new requests pause until reset, or the user is switched to your approved Auto modes with a banner explaining the restriction and reset time.
Checking standing: a user whose role has a limit sees a small panel in their account menu with credits used, limit, percentage, and reset date. Roles with no limit set show nothing there.
Long-running work: under Block, a long operation that crosses the applicable limit while it is still running stops mid-run rather than finishing. Under Auto only the user is switched to your approved Auto modes instead, so the work is not cut off.
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 caps for their period. They're useful when a team needs a clear spending boundary, but they work best paired with proactive controls that reduce usage before anyone hits the cap.
For higher-volume roles, consider limiting the Auto Mode options available to that role generally (not just as the Auto-only fallback above), keeping the role on lower-credit modes when that fits the team's work. Admins can also disable higher-multiplier models that a role or tenant doesn't need. These controls help keep everyday usage lower without relying only on a hard stop at the limit.
Key considerations
Monthly and weekly are independent: a role can have either, both, or neither — each tracked and reset on its own schedule.
At-limit behavior depends on your setting: Block stops new requests until reset; Auto only keeps the user working on approved cheaper models instead.
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(s). Create separate roles when different groups need different limits.
Tenant limits still apply: A user can be restricted by their role limit even if the tenant still has credits, and a tenant can be limited even if no role limit has been reached.
Zero blocks credit usage: Setting a role limit to zero prevents users on that role from using credit-consuming actions, regardless of Block/Auto-only.
Review after changes: If you change a role limit, review current usage in the users and roles views so you understand whether assigned users may still be close to the new limit.