For agencies
Ten client voices, ten sealed rooms.
The hardest part of running content for other people is keeping each voice distinct and each client's material private. Both are architectural here, not procedural.
Isolation
Enforced by the database, not the interface.
Every client is a separate workspace. Voice profile, knowledge base, drafts, calendar, research and analytics all belong to that workspace and nowhere else.
Access is checked with row-level security on every table, which means a query for a workspace you are not a member of returns nothing at the database layer. There is no code path where a filter can be forgotten and one client's material surfaces in another's draft.
Retrieval is scoped the same way, so a generation for client A cannot pull context from client B's documents even accidentally.
What is scoped per client
- Voice profile and rules
- Knowledge base and embeddings
- Drafts and versions
- Calendar and schedule
- Research and sources
- Analytics and patterns
- Engagement inbox
- Audit log
Roles
Seven roles, so approval is a real gate.
| Role | What it can do |
|---|---|
| Owner | Everything, including billing and deleting the organisation. |
| Admin | Manage members, workspaces and integrations. No billing. |
| Manager | Run assigned client workspaces end to end, including approvals. |
| Editor | Create and edit drafts, submit them for review. Cannot approve. |
| Reviewer | Approve or reject drafts and leave notes. Cannot publish. |
| Client | See only their own workspace, review and approve their own content. |
| Viewer | Read-only access to assigned workspaces. |
Workflow
Draft, review, approve, schedule, publish.
Client review without a login maze
Clients see only their own workspace and only the content awaiting them, with a clear approve or request-changes decision and a place to explain why.
Rejections train the profile
A change request is captured as voice signal for that client, so the same objection should not recur every week.
Audit trail on everything
Who generated it, who edited it, who approved it and when it published — recorded per workspace and readable when a client asks.
Talk to us
Tell us about your roster.
Client count, who drafts, who approves, and anything procurement will need. We reply within one working day.
See how close it gets on your first try.
Paste a couple of posts you have already written. You will know within a minute whether this sounds like you.