Skip to main content
A workspace is the top-level container in Nora. Every Flow, every dataset, every trace, every connector belongs to exactly one workspace. Your account can belong to many workspaces at once — you switch between them like Slack workspaces.

​
What lives at the workspace level

  • Flows — the agent workflows you build.
  • Pipelines — the Foundry ingest pipelines.
  • Documents — the knowledge library.
  • Memory spaces — Wiki / Index / Session / Evolution.
  • Causal graphs — per-folder graphs.
  • Members — the people who can access the workspace.
  • Connectors — external system credentials.
  • Providers — LLM API keys.
  • Traces — every run’s recording.
  • Datasets — test cases.
  • Signals & Improvements — the reliability queue.
  • Billing — plan, usage, invoices.
Nothing crosses workspace boundaries by default. Trace search doesn’t leak across workspaces; memory spaces are scoped; even connectors are workspace-scoped.

​
Creating a workspace

Owners of a Nora account can create additional workspaces: Account menu → New workspace. Name it, pick a plan tier (free tier available), and you’re in. Members can be invited immediately. Common patterns:
  • Prod / staging / dev — three workspaces for the same team. Same members, different data.
  • Per-team — one workspace per product team. Members are the team.
  • Per-customer — one workspace per customer engagement (agencies, consultancies).

​
Workspace basics

Settings → Workspace shows:
  • Name — display name. Editable anytime.
  • ID / slug — stable identifier. Set at creation, immutable.
  • Timezone — default timezone for scheduled runs and dashboards.
  • Locale — default UI language.
  • Created at — audit info.
  • Region — hosting region. Set at creation; enterprise customers can choose.

​
Switching workspaces

Any workspace member can switch via:
  • Sidebar — the workspace picker at the top.
  • URL — the workspace slug is in the URL; jumping to another slug switches automatically (if you have access).
  • CLI — nora auth workspaces switch <id> (see nora auth).
Each surface remembers the last workspace per browser / per CLI config directory.

​
Archiving vs. deleting

  • Archive — the workspace becomes read-only. Live traffic stops. Data is retained.
  • Delete — permanent after a 7-day grace period. All data (traces, documents, memory) is removed.
Only Owners can archive or delete. Deletion is one-way — export first if there’s any data you need.

​
Regions

Nora hosts data in region-specific pods:
  • Asia-Pacific (Seoul) — default for Korean sign-ups.
  • North America (Oregon) — default for US sign-ups.
  • Europe (Frankfurt) — GDPR-region default for EU sign-ups.
Cross-region access is available but adds latency. If your team is fully in one region, keep the workspace there. Enterprise customers can pin workspaces to specific regions during setup.

​
Where to next

Members & roles

Invite people, assign roles.

Access & policies

Who can do what across the workspace.

Billing overview

Plan, usage, invoices.

Connections

Hook up Google, Slack, S3, databases, and more.