Security & ownership
Your workspace is yours.
One organisation, sealed off from every other. Roles that decide who sees what. And an exit that does not hold anything hostage.
Isolation
No other client can see your workspace.
Every client is a separate organisation, and organisation scope is not a filter applied at the end — it is the rule every read and every write goes through. A query that could return another organisation's data does not exist in the product. Nothing is shared between workspaces: not pages, not boards, not customers, not assets, not conversations.
The same rule holds outside the interface. The REST API and the MCP server are built on the same operations the screens use, so a key scoped to your organisation reaches your organisation and stops there.
Roles
Four roles, and one line each.
You decide who in your team gets which. SharpHaw's own platform access is separate and never granted by an organisation.
- OwnerFull control of the organisation, including who else gets in.
- ManagerSettings, billing, and members. Can invite editors and viewers.
- EditorCreates and edits content.
- ViewerReads what is marked client-visible. Changes nothing.
Every surface can be turned off for an organisation entirely, and that switch is enforced in the interface and in the backend both — hiding a button is not access control, so it is never the only thing standing there.
Visibility
Working notes stay working notes.
Content carries one of two visibility levels. Client is visible to everyone in your organisation, viewers included. Internal is the agency's own working layer — drafts, notes, and half-finished thinking that would only confuse a reader before it is ready. A child can never be more open than its parent, so a client-visible page cannot hide an internal one that leaks by accident.
Ownership
Leave whenever you like, and take it with you.
The subscription is month-to-month, with no annual contract, no setup fee, and no minimum term. Code, content, analytics, and assets are yours from day one.
The workspace is built to be useful rather than sticky. Pages export to markdown. Board cards export as structured data. Assets can be archived. And every one of those paths is the same machine-facing API the product itself runs on, so getting your material out is not a favour anyone has to do for you.
In writing
The terms are on the site.
Nothing here is summarised in a way the documents do not support. Read them.
Questions the documents don't answer?
Book a 30-minute call. We'll go through what's working, what isn't, and what the first move should be. If we're not the right fit, we'll say so on the call.