Understand namespaces and workspaces
Use the organization hierarchy to understand where your team’s resources belong.
| Concept | What it means |
|---|---|
| Organization | The customer or organizational boundary in the deployment. |
| Namespace | A delegated ownership and cost boundary within an organization. |
| Workspace | The team context containing workloads, assets, releases, connections, and other resources. |
Choose where to work
Select the workspace agreed with your team before creating resources. An asset or connection created in another workspace may not be available to your workload.
Use the workspace selector to change context. Ask your administrator if a workspace you need is missing.
For administrators
Create or change namespaces and workspaces only within your delegated scope. Use Administer → Namespaces or Administer → Workspaces when those entries are available. Check the organization and namespace before confirming a new workspace.
Resource limits are managed separately from names and descriptive metadata. Use the customer-admin resource-pool surface to inspect available controls; changing a workspace’s label does not change its execution limits.
Check the result
Confirm that the workspace belongs to the intended namespace and is available to its members. Ask a member to select it and verify that the expected resources and actions are accessible.
If you cannot make a change
Contact the administrator responsible for the parent scope. Workspace membership alone does not grant organization-wide or namespace-wide administration rights.
Technical enterprise reference and resource-pool guidance provide further detail for administrators.
For namespace metadata, membership, and share-grant API examples, use the technical multi-tenancy reference.