Workspaces¶
A workspace is where your team's Gateway usage lives. Each workspace has its own members, LLM API keys, budget, and region. Use separate workspaces to keep teams, projects, or environments (like staging and production) apart.
What belongs to a workspace¶
- Region. Each workspace runs in one region. Every key in it uses that region's endpoint.
- Members. Each person has a role in the workspace: Admin or Member.
- LLM API keys. Personal keys belong to the person who created them. Service keys belong to the workspace.
- Budget. The workspace has one budget that all its keys spend from.
- Billing. Admins manage top-ups, subscriptions, and purchase history for the workspace.
Region is set once¶
When a workspace gets its region, it keeps it. You can't change it later, and keys can't move to another region.
This is what keeps your data where you want it. If you need models in two regions, create a workspace for each.
The region is usually chosen when the workspace is created. If a workspace doesn't have one yet, an admin picks it on the AI keys page and clicks Set Region.
Create a workspace¶
Anyone signed in to the application portal can create a workspace. Open the workspace menu at the top of the page and choose New workspace. You become its admin.
Switch between workspaces¶
If you belong to more than one workspace, pick one on the home page, or from the workspace menu at the top of any page. Choose All workspaces to go back to the full list.
Keys, budgets, and members are separate in each workspace. Check which workspace you're in before you create a key.
Roles¶
| Admin | Member | |
|---|---|---|
| Create and delete their own keys | ✓ | ✓ |
| Set a spending limit on their own keys | ✓ | ✓ |
| Create and manage service keys | ✓ | |
| Invite and remove members, change roles | ✓ | |
| Set a member's personal budget | ✓ | |
| See spend per member | ✓ | |
| Set the workspace region | ✓ | |
| Top up, subscribe, and see billing | ✓ |
Nobody can see another member's personal keys, admins included. Admins see how much each member spends, not their keys.
Budgets¶
Spend is controlled at three levels:
- Workspace budget. Shared by every key in the workspace. When it runs out, the workspace's keys stop working until an admin tops up or the budget resets. Admins get an email at 75%, 90%, and 100%.
- Personal budget. An admin can give each member their own limit. Members see it as My usage on the AI keys page.
- Key limit. Anyone can cap how much one of their keys spends each month. See spending limits.
Service keys¶
Service keys are for anything that runs without a person behind it, like CI pipelines, bots, and batch jobs. Only admins can create them. Their spend belongs to the workspace, not to whoever created the key, so they keep working when people leave. See service keys.
Common questions¶
Can I change my workspace's region? No. Create a new workspace in the region you need.
Can I delete a workspace? Not from the portal. Contact us if you need a workspace removed.
Can I have one budget across several workspaces? Yes. We can group your workspaces into an organization with a shared monthly spend limit. Contact us to set it up.