Skip to main content

Workspaces, projects, tenants

Three nested containers, each enforcing a different kind of boundary.

What you'll learn​

  • What each container holds
  • What boundary each container enforces
  • When to create one vs. share one

The hierarchy​

Tenant (organization)
└── Workspace (team)
└── Project (initiative)
└── Resources (files, conversations, jobs, ...)

Tenant​

The organization boundary. One company = one tenant in most setups.

What lives at the tenant level:

  • Billing relationship (one invoice per tenant)
  • Single sign-on (one IdP configured per tenant)
  • Tenant-wide policies (data retention, compliance)
  • A directory of all workspaces

Think of a tenant like the AWS account — the legal/billing wrapper around everything.

→ Admin guide: Tenant setup

Workspace​

The team boundary. One team or department = one workspace.

What lives in a workspace:

  • Members (people on the team)
  • Conversations (DMs, channels)
  • Files (shared with the team)
  • Most resources

Most users will spend almost all their time inside one workspace.

→ User guide: Workspaces overview

Project​

The initiative boundary. A project is a self-contained chunk of work — typically what you'd open a ticket for.

What lives in a project:

  • A focused set of resources (files, jobs, forms)
  • A smaller member list (subset of the workspace)
  • A different RBAC scope

Projects are the right level to share outside your team — invite a vendor, a customer, or another department's lead to one project rather than the whole workspace.

→ User guide: Working with projects

Picking the right level​

QuestionAnswer
Should this person see everything our team does?Workspace member
Should this person see one specific thing?Project member
Should this person be billed separately?Their own tenant
Should we share this asset with another company?Their tenant gets a guest project member seat

Next steps​