Skip to main content

Workspaces

A workspace is an isolated space with its own private assets, API keys, credits and members; assets in one workspace are not visible from another.

Every account has a personal workspace, created when you register. You can also create or join any number of team workspaces. Manage them in the aixplain app at Settings.

Personal and team workspaces​

PersonalTeam
MembersOnly youYou and the members you invite, each with a role
Private assetsVisible to youVisible to all members
CreditsYour own balanceA shared team balance
API keysUp to 10Up to 10
BillingYouOwners and Admins

When you create a team workspace, you become its Owner. Invite members as Admin or Member.

Roles and permissions​

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

CapabilityOwnerAdminMember
Create and use assets; use team and public assetsYesYesYes
Transfer assets between workspacesYesYesNo
Create and view API keysYesYesYes
Delete API keysYesYesOwn keys only
Set rate limits on keysYesYesNo
Invite and remove members, assign rolesYesYesNo
Manage payment, buy credits, set up automatic top-upYesYesNo
Redeem vouchers; view transactions and analyticsYesYesYes

To change a member's role, remove the member and invite them again with the new role.

How isolation works​

  • Private assets belong to the workspace where you created them. Public assets are visible from every workspace.
  • Credits in one workspace cannot pay for usage in another.
  • Anything you create, in the app or with a key, belongs to the active workspace. Switch workspaces with the workspace switcher in the app.

Transfer an asset​

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

To transfer, select the asset in the aixplain app, choose the destination workspace and confirm.

Organize teams​

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

PatternStructureUse it to
EnvironmentsOne team per environment (dev, test, prod)Isolate environments and track cost per stage.
ClientsOne team per clientKeep client data and billing apart.
DepartmentsOne team per department or projectGive each group its own budget and owner.

Keep production workspaces to a few Admins, and remove inactive members on a schedule.

Next steps​