Sign in

Set copilot budgets and model tiers per role and operator

An Admin sets how much Copilot each operator can use per month and which quality tier serves them, as a default per role with a per-user override.

When this happens: Admin opens Admin — AI Assistant — Usage & budgets — Copilot allowances.

Step by step

  1. 1

    Open the roles table: each role with its default budget and tier, and the number of users it covers.

  2. 2

    Sets the Sales Operator role to a budget of USD 10 and tier Economy, and the Supervisor role to USD 25 and tier Standard.

    EasyCRM checks each value against the plan cap and MaxTier, saves the AiCopilotAllowance rows (RoleId set), and audits the change.

  3. 3

    Open the user list and sets an override for one operator: USD 50 and tier Advanced.

    EasyCRM saves a row with User set. The user's effective values are the override; users without an override get their roles' values. The list shows per user the effective budget and tier, the amount used this month, and whether the value comes from a role or an override.

Other paths

User with several roles

For an operator who holds both roles above and has no override, resolves the most generous budget (USD 25) and the highest tier.

Clear an override

Clears a your override. EasyCRM removes it; you falls back to the role values from the next request.

No value anywhere

A user with no role value and no override has no Copilot budget of their own and gets the company default tier; only the company total and the plan cap limit them. A budget of 0 instead means no Copilot for that role or user.

Set the company default tier

Sets the Copilot default tier for the company. Applies to every operator with no role or user tier.

If something goes wrong

Above the plan limits

A budget above the plan cap is rejected with EasyCrm:Ai:BudgetExceedsPlanCap; a tier above MaxTier with EasyCrm:Ai:TierNotAllowed.

Good to know

  • Admins pick tiers, never model ids; the platform maps tiers to models and companies follow a remapping.
  • A user override wins; several roles give the most generous budget and the highest tier.
  • The tier is always capped at the plan's MaxTier.
  • Role and user rows have the same shape as ConversationVisibilityScope (RoleId xor User).
  • An operator is notified at 80 % and 100 % of their own budget.