Workspaces and branding

Content, voices, images, destinations, schedules, team members and reports all belong to a single workspace. Nothing is shared between workspaces and nothing is aggregated across them — there is no all-workspaces view anywhere in the product, by design.

The separation is enforced in the database rather than by the interface hiding things, which is what makes it safe to put two clients who must never see each other in the same account.

One account can belong to many workspaces, with a different role in each. You switch explicitly, and switching changes everything at once: the content you can see, the reports, the voices, and what you are allowed to do.

An agency typically runs one workspace per client. Each gets its own voices, its own library and its own branding, and staff hold memberships in the ones they work on.

Admins can create further workspaces under their organisation. There is no billing or usage roll-up across them in the product — treat each as its own account.

A workspace carries a logo and a colour theme, applied live across the interface. For an agency, this is what makes a client's workspace feel like theirs rather than yours.

Themes are chosen from a curated set rather than composed freely, and there is no custom stylesheet. The constraint is deliberate: every provided theme has been checked for contrast and legibility, and a free-form colour picker mostly produces combinations nobody can read.

Changing the theme or the logo is limited to admins — see Team and access.

Managers and admins can export the workspace's data. This is the supported route into a spreadsheet, an archive, or your own systems — there is no reporting API.

Worth doing before any irreversible change, and worth doing periodically regardless. It is also the answer when someone exercises a data-subject right and you need to produce what you hold.

An admin can delete the whole workspace. This exists so that a customer exercising their right to erasure gets a real deletion rather than a flag on a row.

• One workspace per audience boundary — per client, per brand, per organisation. Not per campaign, and not per person.
• Do not split by content type. Blogs and newsletters for the same brand belong together; splitting them means maintaining the same voice twice.
• Add people to the workspaces they work on, and only those. Membership is the access control; there is no per-folder permission.
• Name workspaces for the client, not the project. Projects end; workspaces do not.