Self-Service Provisioning
The PortalEnterprise
What people see in the Portal, and how they set up and use their tools.
The Portal is the page where people set up the AI tools their organization grants them, separate from the dashboard. It shows the tools each person can set up, the settings to paste into each, their budget and their key. People who only use the Portal sign in there, and are sent there from the dashboard.
Signing in
The Portal sign-in asks for the work email first, then signs the person in with single sign-on or a password. A person invited with Portal access sets a password, or uses SSO, when they accept. A person with access in more than one organization switches between them with Switch organization in the menu.
Your AI agents
The home page, Your AI agents, lists the tools the person has set up, with the period's spend, such as This month, At this pace with when the cap is reached at the current pace, their Status, and a hint of their key. Add an AI agent opens Choose an AI agent, which lists the tools the policy grants, with Set up on each, and the approved models and cap of tools already set up. A person with no policy sees No AI agents are set up for you yet, with a prompt to contact their IT department.
Setting up a tool
A tool is set up from its page in four steps:
- On Choose an AI agent, select Set up on Claude Code or Claude Desktop.
- Install the tool, following the first step on the page. For Claude Desktop, this includes turning on Developer Mode.
- Copy the settings under Point it at your organization's router, and paste them where the page shows.
- Check it works: run the tool, quitting and reopening Claude Desktop first, and ask it to say hello.
For Claude Code, the settings come in four forms, one per tab:
| Tab | Where the settings go |
|---|---|
| macOS / Linux | ~/.claude/settings.json |
| Windows | %USERPROFILE%\.claude\settings.json |
| Environment variables | ~/.zshrc or ~/.bashrc |
| Managed by IT | /Library/Application Support/ClaudeCode/managed-settings.json |
For Claude Desktop, the page lists the fields to fill under Developer, then Configure Third-Party Inference, then Connection: Inference provider, Gateway base URL, Credential kind, Gateway API key, Gateway auth scheme and Custom inference headers, each with a copy button. The settings hide the key; Copy copies the working settings, and Reveal key shows it. See Claude Code and Claude Desktop.
A tool's page
Each tool the person set up has its own page:
| Section | Shows |
|---|---|
| Your budget | Spend against the cap, what is left, the pace over the last 3 days, when the cap is reached at that pace, when it resets, and Set by your organization's IT with the cap, model caps and rules. |
| Allowed models | Each model's spend, with its own cap or the shared total, and when it was last used. |
| Your key | A hint of the key and when it was issued, with Issue a new key and Remove. |
| Install, set up and troubleshoot | The setup steps, and fixes for common errors. |
When a budget pauses the tool, the page shows Paused until the reset, with the tool receiving 429 budget_exhausted until then; the key and access stay.
Requesting more budget
When the budget has request approvers, a cap and a period other than Lifetime, and no request waiting, Request more budget lets the person ask for a higher limit for the current period, with a New monthly limit above the current one and an optional message of up to 500 characters. The page then shows the request as pending, approved with the new limit, or not approved. See Overrides and Requests.
Keys
Issue a new key replaces the tool's key: the old one stops working at once, and the budget and usage carry over. Remove deletes the key and the tool's router, and Set it up again creates a new agent.