Limit how a model account is used
By default every enabled model account takes any task that fits it, up to your organization's limit. Two settings narrow that: Auto-assign keeps an account for tasks that pick its provider, and Max runners caps how many runners use it at once, for example to leave a subscription's quota for people. How a run picks an account is in How model accounts work.
Who can do this: the Org Owner or Org Admin role. Anyone else sees the account read-only, under Read-only — only an administrator can change an account.
- In the sidebar, select Directory, then AI Accounts.
- Select the account's name. Its Details tab opens beside the list.
- To keep the account for tasks that pick its provider, clear Auto-assign. Leave it ticked to let the account also take tasks that allow any provider.
- In Max runners, type the most runners the account may run at once. Leave it blank to use the default the field shows: Org default and its number for a subscription, No limit for an API key. Only a whole number of 1 or more is accepted. Some API-key accounts don't offer the field.
- Select Save.
- Check the account's row. With Auto-assign off it shows explicit only. Sessions shows how many runners use it now and how many are busy.
To stop an account taking any new run, disable it instead: see Pause or remove a model account.
Related
- Add a model account — set both when you add the account.
- Model accounts — every field on an account's Details tab.