Workspace naming and limits

Edit online

When you create workspaces in IBM watsonx Orchestrate, follow the naming requirements and understand operational limits.

Important: Workspaces are currently supported only on IBM Cloud.

Workspace naming rules

Workspace names must meet the following requirements:

  • Uniqueness: Names must be unique within your tenant (case-insensitive)

  • Length: 1-40 characters (after trimming whitespace)

  • Format: Must start with a letter (a-z, A-Z). Allowed characters: letters, numbers, underscores (_), and spaces

Workspace operational limits

watsonx Orchestrate workspaces operate within IBM Cloud IAM constraints.

Table 1. Operational limits
Artifact Maximum Details
Workspaces per user 50 Each workspace membership corresponds to one IAM access group. A user can belong to a maximum of 50 access groups.
Members added per batch 50 IAM API limits access group membership updates to 50 members per request

Assistant builder access configuration

Assistant builder operates independently from workspaces and requires separate access configuration. Assistant builder has its own access control using assistants and environments.

When you set up workspaces, also configure access to Assistant builder to ensure users have the required access.

Best practices

Workspace organization

  • Create workspaces by project, team, or domain

  • Use descriptive names that follow naming rules

  • Document workspace purpose

  • Use Global workspace for shared artifacts

Artifact management

  • Copy to Global workspace only when ready for use by all users that are members of the Global workspace or any private workspace

  • Understand deep copy implications

  • Deployed agents are visible to all users regardless of workspace

  • Use tenant-level artifacts (models, connections) for shared functionality

IAM management

  • Do not modify access groups directly

  • Do not delete workspace IAM policies

  • Configure Trusted Profile correctly