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.
For creating and managing roles, see the Custom Roles support guide. This article covers the credit-limit setting specifically.
Setting a limit on a role
Open the custom role in Users, Roles & Permissions, then open Usage limits. Enable Monthly limit, Weekly limit, or both, and configure each enabled period.
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 and choose the action to apply when it is reached. Use Block usage when you intend to stop credit-consuming work at that ceiling.
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 usage — stops credit-consuming work at the limit. It can stop an in-progress operation as well as prevent new requests. Check completed work before continuing after access is restored.
Auto only — the next request uses Auto after the limit is reached. Work continues consuming credits.
When each period resets
Monthly limits reset at the start of the UTC 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: Block pauses credit-consuming work; Auto-only routes the next request through Auto. The user sees a notice 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: a reached Block policy can stop work in progress. Auto-only applies to the next request. Inspect completed results before continuing stopped work.
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 model access
Role limits apply the action you select for each period. Choose Block for a firm credit-consuming-work ceiling, or Auto-only to continue with Auto. Pair these with appropriate model access and focused tasks.
For higher-volume roles, review which named models their tasks need. Model access and focused inputs help control everyday usage before a period limit is reached.
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 credit-consuming work; Auto-only continues through Auto and still consumes credits.
Custom roles only: Credit limits are configured on custom roles, not on every built-in role.
Per user: every assigned user has the configured ceiling independently. Create separate roles when 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.
Set the action deliberately: the period limit and its Block or Auto-only action work together. Review both before saving.
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.
Combine weekly and monthly limits
Set a monthly Block usage ceiling and a smaller weekly Auto only limit when you want to guide weekly work through Auto without removing the overall monthly ceiling. Each limit applies per user, not to a shared role balance. Any reached Block limit wins.
Monthly limits reset at the start of the UTC calendar month.
Compatible external clients
AI Gateway is a separately governed route for compatible external model requests. Eligible activated requests use its USD budgets. It does not move existing Hatz chats or remove their Block policy. Ask your administrator to review Gateway access and budgets for the external client.
Weekly reset is Wednesday at noon Eastern, following daylight-saving time. Auto-only takes effect on the next request; a Block policy can stop in-progress work. Review completed results before continuing.
Watch: combine weekly and monthly credit limits

