Skip to main content
A workspace groups resources within an organization. Pools, instances, instance templates, deployments, images, subnets, and tags all belong to a workspace. Every new organization comes with a workspace named default. It’s not special: you can rename it through the API or delete it like any other workspace.

Create a workspace

Workspace names are unique within your organization.

List workspaces

The arrow in the leftmost column marks the active workspace.

View a workspace

Get a workspace by name, or omit the name to get your active workspace.

Set your active workspace

If you haven’t set an active workspace, the CLI falls back to default. Set one with sf workspaces use <name>. Override per-command with --workspace <name>.

Every request targets a workspace

Every API request that creates, lists, or operates on workspace-scoped resources targets a workspace. Not all resources are workspace-scoped; see resource paths for which resources live at which scope.
  • Creating resources: include "workspace" in the request body. Resources created on a pool (instances, deployments, and orders) are the exception. They inherit the pool’s workspace, so you choose the workspace when you create the pool.
  • Listing resources: pass ?workspace= as a query parameter.
  • Getting a single resource: use a resource path or an ID.
On the CLI, pass --workspace.

Cross-workspace references with resource paths

Every resource has a resource path that embeds the workspace. Use a resource path anywhere you can pass a name or ID. It lets you reference resources in another workspace without switching context.

Delete a workspace

Deletion fails if the workspace still contains pools, instance templates, images, subnets, or custom firewalls. Move or delete them first.

API reference

See the Workspaces API for programmatic access.