Workspaces
Every account has a personal workspace and can create any number of team workspaces. Each is a completely isolated space with its own private assets, API keys, credits, and members — assets in one workspace are not visible in another.
- Personal workspace — your individual space, created when you register. It operates independently of any team you join.
- Team workspace — a shared space for collaboration. You become its Owner when you create it, and invite members as Admin or Member.
Manage teams and members at app.aixplain.com/team/settings.
Roles and permissions
Team workspaces have three roles. There is one Owner per team; Admins have all Member permissions plus billing, member, and key management.
| Capability | Owner | Admin | Member |
|---|---|---|---|
| Create and use assets; access team and public assets | ✓ | ✓ | ✓ |
| Transfer assets between workspaces | ✓ | ✓ | ✗ |
| Create and view API keys | ✓ | ✓ | ✓ |
| Delete API keys | ✓ | ✓ | own only |
| Set rate limits on keys | ✓ | ✓ | ✗ |
| Invite/remove members, assign roles | ✓ | ✓ | ✗ |
| Manage payment, purchase credits, auto top-up | ✓ | ✓ | ✗ |
| Redeem vouchers; view transactions and analytics | ✓ | ✓ | ✓ |
Direct role changes and ownership transfer are coming soon. Until then, change a member's role by removing and re-inviting them.
Workspace isolation
- Private assets belong exclusively to the workspace where they were created; public assets are visible everywhere.
- Each workspace has its own credit balance — credits in one workspace cannot be used in another.
- Each workspace can hold up to 10 API keys (see API keys).
- Switch workspaces from the workspace switcher; any asset you create belongs to the active workspace.
Transferring assets
Transfer moves a private asset between two workspaces you belong to. It is a move, not a copy: the source workspace loses all access, and the destination gains full ownership, editing, and billing for that asset. Select the asset, choose the destination workspace, and confirm.
Organizing teams
Create a separate team whenever you need billing separation, access control, data isolation, or compliance boundaries. One team = one isolated workspace.
| Pattern | Structure | When to use |
|---|---|---|
| Dev / test / prod | One team per environment | Isolate environments, gate deployments, track cost per stage |
| Client separation | One team per client | Separate billing and data, grant client-scoped access |
| Department segmentation | One team per department or project | Team autonomy, budget allocation, clear ownership |
Best practices: use descriptive team names; keep production teams locked down with minimal Admin access; set a low-credit alert on every team; review access and remove inactive members periodically.
Personal vs team workspaces
| Personal | Team | |
|---|---|---|
| Members | Only you | Multiple, with roles |
| Private assets | Visible to you | Visible to all members |
| Credits | Your balance | Team's shared balance |
| API keys | Up to 10 | Up to 10 |
| Billing | You manage | Admins and Owners manage |