Organisations & workspaces

On this page

dembrane has two levels above your actual work. An organisation is your company or institution; inside it live workspaces, and inside each workspace live the projects where conversations, transcripts, chat, and reports sit.

To create a workspace you need to be an org admin or owner. To manage one, you need to be its owner or admin. See roles & permissions.

New workspace, or new project?

This is the question that comes up most. The short version: a workspace is the unit of billing and access; a project is the unit of work. When in doubt, prefer a project - workspaces are heavier, each with its own members and tier.

Your situation Make a…
A new study or consultation within the same team project in an existing workspace
A new client or external engagement (especially as a partner) workspace
A sensitive programme that should be private from the rest of the org workspace
A separate team that shouldn’t share members or settings workspace
A programme that needs audit logs or a higher tier than the rest workspace

Projects can be moved between workspaces later if work changes hands - see data ownership & compliance.

Membership at the two levels is separate

Being in an organisation doesn’t put you in any of its workspaces, and being in a workspace doesn’t put you in the org. So:

Bringing an outside collaborator into the organisation as a full member is therefore a deliberate step, not a toggle - the path is in external is a role.

How billing flows

Billing attaches to a billing account:

So internal costs roll up into the org, while an external-client workspace stands on its own. The full picture is in tiers & billing and data ownership & compliance.

Getting started

A new organisation begins with an onboarding wizard that creates your first workspace and project together, so you’re recording within minutes. From there you add people via invites, set visibility, and choose a tier. Hosts can follow the host getting-started guide.

Related

Comments