Self-Service Provisioning
Tools PoliciesEnterprise
Creating and editing the policies that decide how each tool works for the people on them.
A tools policy is an organization's set of rules for the AI tools it grants, one set per tool. Policies belong to an organization and are listed under Policies on the organization's People page. Each policy has revisions: every save writes the next revision, and applies it to everyone on the policy.
Creating a policy
A policy is created on the organization's People page:
- On the organization's People page, open Policies and select New policy.
- Enter a Name, such as Standard Engineering. The policy's Tag, such as
policy:standard-engineering, comes from the name. - Under AI Agents, select Add to policy on Claude Code or Claude Desktop, and set up its Routing, Models, Budget and Budget rules.
- Select Save Claude Code, or Save Claude Desktop. Tools are added one at a time, each saved before the next.
- Select Create policy. Agents are created when people on the policy set them up.
Names are up to 120 characters. Every router the policy creates carries its tag, which is fixed once the policy is created, up to 73 characters, and unique in the organization. The Budget and Budget rules cards appear when budgets are on for the installation.
Routing
The Routing card sets how the tool's requests are served, with the same choices as a Claude Proxy:
| Setting | Values |
|---|---|
| Route | A route from the catalog, such as Anthropic or Bedrock (Geo), or Custom with a model group. |
| Region | The region, on routes with regions. Anthropic and Custom serve without one. |
| Credentials | Organization Key, with a provider key, or Developer Credentials on the Anthropic route. |
| Model group | On the Custom route, the group of models, with a provider key for each member. |
Claude Desktop uses the Organization Key, since the app sends one credential. Developer Credentials let each person's Claude Code use their own Claude login, billed to them. See Claude Proxy.
Models
The Models card lists the route's models with their version, provider model id and price, and Serve switches each on or off. A switched-off model stays listed and is refused when requested.
Budget
The Budget card sets each person's spending for the tool:
| Field | Description |
|---|---|
| Per-person cap | The most each person can spend per period, such as $200. More than $0. |
| Period | Daily, reset every day; Weekly, reset on Mondays; Monthly, reset on the 1st; all at 00:00 UTC. Lifetime never resets. |
| Per-model caps | A cap for one model, per person, inside the per-person cap. |
The Budget rules card adds notifications and blocks at points of the per-person cap, every model cap, or one model's cap, such as an email to a team lead at 80% and a block at 100%. Email goes to an address the admin enters, of a person active in the organization. Notifications send once per period, and a block answers 429 until the period resets, or the cap is raised on a Lifetime budget. Each tool's budget appears on the Budgets page, managed by the policy. See Rules and Alerts.
Editing and revisions
Edit policy opens the policy for changes, and Save changes writes the next revision and applies it at once to everyone set up on the policy. Each person's agent keeps its router and key, and takes the new route, models and budget. Save changes is available once something has changed. Removing a tool that people have set up asks for confirmation, and saving retires that tool's agents for everyone.
When an edit affects tools in use, saving asks for confirmation first:
| Change | Confirmation |
|---|---|
| Removes a model or tool used in the last seven days | Saving is blocked, with See who listing the routers and models affected. Save anyway to continue. |
| Removes a model or tool with no recent use | Acknowledge and save. |
| Lowers the per-person cap | Acknowledge and save. |
The policy page shows the Revision each person is on. When an edit could not be applied to someone, the page names them, and they stay on the earlier revision until the policy is saved again.
The policy page
A policy's page summarizes it:
| Area | Shows |
|---|---|
| People | How many people are on the policy, and how many have set up a tool. |
| AI Agents | The tools on the policy. |
| Spend this period | Spend against the per-person cap times the people set up, and when it resets. |
| Revision | The live revision, and how many people are on an older one. |
| Tool sections | Each tool's Route, Credentials, Budget, Budget rules and Models. |
| People table | Each person's name, spend per tool, total spend and revision, with a remove button that retires their agents. |
| History | Each revision, with its tools, date and who saved it. |
Open in Budgets opens the budget of the policy's first tool. See Budgets & Spend Control.
Validation
A policy saves when each tool's settings fit together. The editor names the setting to fix, such as:
| Message | Fix |
|---|---|
| Pick at least one AI agent to create this policy. | Add Claude Code or Claude Desktop. |
| Choose a route and region. | Pick a route, and a region on routes that have one. |
| Choose a provider key for the Organization credential. | Pick a provider key for the route. |
| Claude Desktop needs the company's credentials; pick Organization. | Use the Organization Key for Claude Desktop. |
| Set a per-person cap. | Enter a per-person cap. |
| The cap must be more than $0. | Enter an amount above $0. |
a policy with tag "x" already exists in this organization | Choose a different name. |