How credit allocations work

When you review workspace usage, the credit usage overview shows a total credit allocation. That total is divided across the workspaces in your account, either evenly by default or in fixed amounts that account admins set. By default, workspace credit allocations are guidelines, but account admins may also enforce limits on a per-workspace basis. When a workspace has an enforced limit, cloud runs are blocked when the workspace has exceeded its allocated amount of credits.

Default and fixed limits

Every workspace has either a default or fixed credit limit. Account admins set fixed limits from the Workspaces table of the account billing dashboard, or when adding a workspace.

Default limits

By default, the total number of credits for an account is shared equally across its workspaces. For example, if an account with two workspaces is allocated 30,000 credits for the month, each workspace shows 15,000 for its credit limit.

mabl recalculates this split whenever workspaces are added or removed. For example, consider an account that has 30,000 total credits and two workspaces with the default credit limit.

• If you add a third workspace with a default credit limit, the limit for all three workspaces updates to 10,000 credits each.
• If you remove the third workspace, the limit for the two remaining workspaces updates to 15,000 credits each.

Fixed limits

If an account admin sets a specific credit limit, the billing dashboard shows a Fixed badge next to that limit. Fixed limits are useful when workspaces have unequal testing needs. For example, a workspace for onboarding new team members may warrant fewer credits than your primary testing workspace.

Unlike default limits, fixed limits do not change when workspaces are added or removed. Fixed limits are subtracted from the account total first, and the remainder is split across the workspaces that still use a default limit. Starting again from an account with 30,000 total credits and two default workspaces:

• Adding a workspace with a fixed limit of 1,000 credits reduces the remaining credits available to default workspaces, updating their limits to 14,500 credits each.
• Adding another default workspace in the above scenario distributes the remaining credits evenly across all default workspaces, resulting in 9,666 credits per workspace.

Because fixed limits don't adjust on their own, review them after adding or removing workspaces to make sure your allocations still match your testing priorities.

Enforced limits

Enforcement turns a credit limit from a guideline into a hard stop for a single workspace. Account admins turn it on with the Limit enforced toggle in the Workspaces table of the account billing dashboard, or with the Enforce this credit limit checkbox when adding a workspace. Enforcement is set per workspace, so you might enforce a limit on an onboarding workspace while leaving your primary testing workspace unenforced.

Enforcement is off by default, and it applies only to workspaces that have a credit allocation. Trial workspaces aren't affected.

What happens when a workspace reaches an enforced limit

When an enforced workspace uses its full credit allocation for the billing period, mabl shows a banner in the workspace and stops any cloud run triggered there. Stopped runs carry a label indicating that the workspace reached its credit limit. Credit limits do not impact local and CI runs.

Cloud runs can resume as the workspace is back under its limit, whether that's because credits reset for the next billing period or because an account admin raised the limit or turned off enforcement.