Workspace details

Business Summary: The Workspace tab shows which organization you are working in and its identifier — essential when opening support tickets, coordinating with admins, or confirming you are in the right tenant before approving sensitive runs.

You will learn what the Workspace settings tab shows about your organization context and when you need those identifiers for support or integration setup.

The Workspace tab describes the organization you are working in — not individual workstreams.

How this fits in Nimbus

Your organization is the tenant that owns billing, members, connectors, and workstreams. The Workspace tab surfaces that context at a glance.

flowchart TB
  Org[Organization]
  WS[Workspace context]
  Billing[Billing and members]
  Connectors[Connectors]
  Workstreams[Workstreams]

  Org --> WS
  Org --> Billing
  Org --> Connectors
  Org --> Workstreams

Every workstream you open belongs to this organization. The Workspace ID helps support and admins distinguish tenants when names look similar.

Verify org context

1. Open Settings → Workspace before approving sensitive connector writes or sharing audit exports externally.
2. Read Organization — confirm pilot vs production naming matches your change-management ticket.
3. Copy Workspace ID when opening a Nimbus support case or correlating with internal IT logs.
4. Do not confuse this ID with a workstream ID on an individual goal page.
5. If the organization name looks wrong, stop and ask an admin before continuing governed runs.

Opening Workspace settings

1. Go to Settings
2. Select the Workspace tab
3. Or open Settings → Workspace

Fields displayed

If organization name is unset, the UI may show the organization ID instead.

When you need these values

Share workspace context when opening a support ticket for billing or connector issues, confirming you are in production vs pilot tenant, coordinating with admins who manage team membership, or debugging invite or access issues after onboarding.

Do not confuse workspace ID with workstream ID — workstreams have their own IDs on the workstream page.

Organization vs workspace terminology

In Nimbus, organization is your company tenant (billing, members, connectors). Workspace is the execution environment slice under the org (default workspace shown today). Multi-workspace expansions may add workspace switchers; settings currently show active context from the organization store.

What you cannot change here yet

Self-serve edits on this tab are read-only today: renaming the organization, changing workspace ID, and switching default data region. Admins contact Nimbus support or internal platform teams for those changes.

Example scenario

Two pilot tenants exist — "Acme Pilot" and "Acme Production." Before approving a connector write, an operator opens Settings → Workspace and confirms the organization name matches production. She copies the Workspace ID into a change-management ticket so IT can correlate Nimbus audit events with their internal log.

What you'll see

Open Settings → Workspace. The card shows:

Copy the Workspace ID with your browser selection or screenshot the field — support uses it to locate your tenant.

FAQs {#faqs}

Q: Is workspace the same as a workstream? A: No. A workstream is a goal-scoped workspace. Workspace here is org environment context.

Q: Where do I see my org role? A: Not on this tab yet. See Organization members and roles.

Q: Can I have multiple workspaces in one org? A: Yes. Open the sidebar workspace switcher and choose + New workspace to create a blank-canvas environment. See Creating a workspace.

Q: Does workspace ID appear in billing? A: Usage ledger entries may include workspace ID for attribution in technical exports.

Q: We finished onboarding — is this the same org? A: Yes. Onboarding creates or joins the organization shown here.

Q: Should I share workspace ID externally? A: Share with support and trusted admins. Treat it like an internal account identifier — not a password, but useful for troubleshooting.