Skip to content

Workspaces and projects

A workspace is your account: the people who work together, their roles, and the sending setup. You create one from the dashboard, or with workspaces.create from a signed-in session. Each user may create up to three workspaces by default (workspace_limit_reached beyond that; a self-hosted installation sets the number with MAX_WORKSPACES_PER_USER).

Every member has one of two roles:

Role Can
member Read and write the project’s customers, events, workflows, and messages; list the workspace’s members and projects.
admin Everything a member can, and activate workflows, manage members, create the project, and manage its API keys.

A workspace always keeps at least one admin: removing or demoting the last one answers conflict. Members are added by the address they sign in with, and only once they have signed in; invitations are planned.

The sending setup belongs to the workspace too: its verified sending domains and its approvers (Sending).

A project holds your data: customers, events, workflows, runs, and messages. It is the isolation boundary. No call can read or change another project’s data, and a lookup of something outside your project answers not_found, as if it did not exist.

A workspace has one project for now. An admin creates it with projects.create; a second answers conflict. Several projects per workspace, for example one per product, are planned.

  • An API key belongs to one project and acts only on it. Your application and your AI assistant use keys.
  • A dashboard session belongs to a person. It reaches the workspaces they are a member of, with their role in each, and names the workspace or project it means in a header.

Authentication covers both.