Manage your workspace

A workspace is where your work on aixplain lives: your agents and other assets, your API keys, your credits and the people you work with. Everyone has a personal workspace, and you can create or join team workspaces to work with others. This article explains how workspaces work, how to invite members and choose their roles, how credits and API keys belong to a workspace and where to see usage.

What is a workspace?

A workspace is an isolated space with its own private assets, API keys, credits and members. Assets in one workspace aren't visible from another, and credits in one workspace can't pay for usage in another.

In the aixplain app and the docs it's called a workspace. Koder and some settings call the same thing your team, for example "your team's credits".

Personal and team workspaces

Your personal workspace is created when you register. You can create or join any number of team workspaces.

Create a team workspace

Create a team workspace from the aixplain app. When you create one, you become its Owner.

On Scale, you choose how many seats you need when you create a team workspace. Each seat is paid up front by card through Stripe, and the workspace opens once it's paid. Every member you invite takes a seat. For seat prices, see Pricing.

When to create another workspace

Create a separate team workspace when you need separate billing, access, data or compliance boundaries. Some common patterns:

• Environments: one workspace each for dev, test and prod, so you can isolate them and track cost per stage.
• Clients: one workspace per client, to keep client data and billing apart.
• Departments: one workspace per department or project, to give each group its own budget and owner.

Switch workspaces

Use the workspace switcher in the aixplain app to change the active workspace. Anything you create, in the app or with an API key, belongs to the active workspace, so check which one is selected before you build.

In aixplain Desktop, the app works with your selected team. Koder shows the selected team before it opens checkout, so you know which balance you're topping up.

Invite members

Owners and Admins invite members to a team workspace and choose each person's role.

1. Switch to the team workspace and open Settings.
2. Invite the member and pick their role: Admin or Member.

The person you invite sees the pending invitation across the app and can open an invitation page to view and accept it.

Roles and permissions

A team workspace has one Owner. Admins have every Member permission plus billing, member and key management.

Members can open workspace settings too. Actions only an Admin or Owner can take are hidden for them.

Share agents and other assets

Private assets belong to the workspace where you created them, and every member of a team workspace can see and use them. Public assets are visible from every workspace.

• Agents: the agent library in the app lists all of your workspace's agents. A private agent is visible only to the workspace that owns it. On the aixplain OS, an agent can stay private in your Library, be shared with the workspaces you choose or be published to the Marketplace. To build one, see Build and deploy agents.
• Connections: the apps you connect, including MCP servers under integrations, are team assets. Verifying a connection and running its actions may use credits.
• Knowledge, models and tools: when you're signed in, Omni sees your team's agents, models, connections, knowledge bases, tools and pipelines so it can pick the right one. See Get started with Omni.
• Skills: skills published by other teams appear on the Marketplace and in the agent builder's picker. Skills you don't own don't offer edit actions.
• Marketplace search: results take your workspace into account, so your team's own assets show up.

Your own work stays yours

In a team workspace, everyone gets their own Omni, with private memory, sessions and connected tools. It works from the agents, skills and files your workspace shares with you. Other members can't see your sessions, though admins can open and export them when your company needs to, for example for an audit. Admins decide which models and connections Omni can access and set its policies and limits.

Transfer an asset to another workspace

A transfer moves a private asset to another workspace you belong to. It's a move, not a copy: the source workspace loses access, and the destination workspace owns, edits and pays for the asset from then on. Owners and Admins can transfer assets.

1. Select the asset in the aixplain app.
2. Choose the destination workspace.
3. Confirm the transfer.

Credits and billing

Each workspace has its own prepaid credit balance, and every model, tool and agent run in that workspace draws from it. One credit is one US dollar. In a team workspace, members share the team balance.

Owners and Admins add credits:

1. Open Settings → Billing in the workspace you want to fund.
2. Select Add credits.
3. Enter the amount, choose a payment card and confirm.

To use a voucher, open the same page, choose to redeem a voucher and enter the code. Any role can redeem a voucher.

From aixplain Desktop, open Settings → Account & usage to see your selected team's credits and saved cards, or run koder billing in the terminal. Top-ups and new cards go through a hosted payment page in your browser.

For plans and how credits work, see Account, plans and billing.

Budgets and limits

You can cap spending at several levels:

• Agents: set a budget on an agent to cap what a run can cost.
• API keys: Owners and Admins set request, token and credit limits on each key. A key's credit limit can be a lifetime cap or reset daily, weekly or monthly.
• Members and groups: on Scale, set access and budget policies for every member and group.

You can switch off any agent or key at once.

API keys

API keys belong to one workspace and use that workspace's assets and credits. Each workspace holds up to 10 keys.

1. Open Settings → API keys in the workspace the key should use.
2. Select Create API key.
3. Enter a name that says where the key runs, and optionally an expiration date.
4. Select Create, then copy the key. The full key is shown only once.

Every role can create keys. Members can delete only their own keys, while Owners and Admins can delete any key. Owners and Admins can also create admin keys, which don't run models or agents but set limits on the workspace's other keys. For code examples, see the API keys docs.

See your workspace's usage

The workspace usage page shows what your workspace spends. It breaks usage down by API key, with each key's owner and masked key in the picker, so you can see which application or person is behind the spend. Every run's cost also shows in its trace.

Model and tool calls made during an agent's run are attributed to that agent, so usage by agent adds up. On Scale, usage dashboards also break down by group and person.

Enterprise

With Enterprise, the aixplain OS runs on-prem, in your VPC or air-gapped. You get a workspace for each team or entity, with groups, roles and policies that cascade from the workspace to its groups and members. Every agent has an owner. Budgets, rate limits and an off switch apply per workspace, key or model, and every run is recorded and exportable. Single sign-on (SSO) is coming soon. See Enterprise and Security.

Frequently asked questions