Workspaces

A workspace is a resource isolation unit within an enterprise space. Each workspace is bound to a service account. Calls made with that service account's API Key can access only resources in the bound workspace. Agents, sessions, deployments, environments, files, skills, secrets, and memories belong exclusively to one workspace and cannot be referenced across workspaces. Use workspaces to separate projects, end customers, or environments such as prod and staging.

​

Basic rules

• Each workspace is bound to one service account, and each service account can be bound to only one workspace.
• Every enterprise space includes a default workspace. Existing resources and API Keys are already in the default workspace, so no migration is required. You can rename the default workspace.
• A workspace without a bound service account is read-only. Bind a service account before starting sessions or performing operations.
• Workspaces are available only in enterprise spaces, not personal spaces. Creating and managing workspaces requires the organization administrator or configuration administrator role.
• When there is more than one workspace, you can archive workspaces that are no longer needed.

​

Access workspaces

The workspace selector on the right side of the console's top bar shows the current workspace. Open it to:

• Search for and switch between workspaces. The list identifies the service account bound to each workspace and marks the default workspace.
• Create a workspace.
• Open workspace management.

After switching, every resource list in the console shows only the current workspace's resources. The enterprise credentials entry at the bottom of the left navigation shows the service account bound to the current workspace and its API Keys.

​

Manage workspaces

The management page lists all workspaces in the organization. Search by name or ID, or filter by archive status. The list shows each workspace's ID, name, bound service account, and status, and marks the current workspace. Create service accounts and manage their API Keys in the Qoder administration console, accessible through the link at the top right of the page.

​

Create a workspace

Click the new workspace button at the top right and enter a name and description. You can bind a service account immediately or skip this step and bind one later. Workspace names must be unique within the same enterprise space.

​

Edit a workspace

Update the workspace's name and description. Changing the display name does not affect the workspace ID or its resources.

​

Change the service account

Choose the option to change the service account in the workspace's row actions, then select another existing service account in the organization. After the change, enterprise API calls for this workspace must use the new service account's API Key. Service accounts already bound to other workspaces cannot be selected.

​

Unbind the service account

Choose the unbind option in the workspace's row actions and confirm. The workspace becomes read-only. You cannot start sessions until a service account is bound again.

​

Archive a workspace

When there is more than one workspace, you can archive a workspace that is no longer needed. An archived workspace cannot be entered or used for API calls, and its resources are no longer visible. Its bound service account is released and can be bound to another workspace.