Limits
Split your AI credits between the widget and the dashboard, cap what each Product and each visitor may spend, and read every other plan ceiling in one place.
Workspace settings > Limits sets your own ceilings in AI credits, inside the allowance your plan already gives you. Admins only.
Before you start
- Every cap is in AI credits. A chat answer is well under two credits. No cap can go above your plan's allowance, which is on Billing.
- An empty field inherits: the number it inherits is shown greyed inside it. On the Workspace card that is the plan default or Unlimited; in the Products table it is the workspace's own number.
Setting it up
Workspace shows what the widget and the dashboard spent this period as a two-part bar, against your allowance. The five caps follow in three cards, grouped by the window each one runs over: Per billing period, Rolling 30 days and Rolling 24 hours. This period's widget and dashboard spend, per Product, is read on Usage. The anonymous pool's 30-day spend is not shown on either page.
- Dashboard spend cap: what your team's AI actions may spend this billing period. Empty means half of your allowance.
- Widget spend cap: what end-user chat may spend this period across every Product. Empty means the full allowance.
- Anonymous pool: credits every anonymous visitor of one Product shares over a rolling 30 days. Empty means the plan default.
- Per-user daily cap and Anonymous per-browser daily cap: credits one signed-in user or one anonymous browser may spend on one Product in 24 hours. Empty means Unlimited.
Products has one row per Product with its serving state, what it spent this period and four caps of its own: Widget spend cap, Anonymous pool, Per-user daily and Anonymous per-browser daily. A Product's widget cap cannot go above the workspace's, but the Product caps together may add up to more than it: credits then go first come, first served. Serving is read-only here, and the Product's name opens its own settings, where it is paused. New product is refused at your plan's Product count, and the line under it names the plan that lifts it.
Plan ceilings is read-only: every other ceiling, whether it is counted across the workspace or per Product, and how much is in use.
Type numbers with up to two decimals, 0 included. A value above its ceiling is refused under the field. Save once for both layers.
Hand it to your agent with the ARCY MCP opens the Suggest the limits entry on ARCY MCP for the selected Product. A proposal names its layer, the workspace or one Product, and shows here as Proposed by your agent, each cap against the current one. Only an Admin can Accept or Discard it.
What it changes
- At the Dashboard spend cap every AI button in the dashboard stops and names that cap; the widget keeps answering. An Admin gets a link to this page, a Member is told to ask an Admin. At the Widget spend cap the agent is hidden on every Product; at a Product's own widget cap, on that Product only.
- A user or browser at its daily cap gets a reply saying they have reached today's limit. At the Anonymous pool the agent is hidden for anonymous visitors of that Product.
- When the whole allowance is spent everything stops until the next period (Billing).
- The sign in and sign up pages offered to a capped anonymous visitor are set on Product.