Workspace isolation
Workspace isolation is enforced in the database itself, not just the interface. One studio can never query another's records.
Enforced at the source
Isolation isn't a filter in the interface that could be bypassed; it's enforced in the database itself. A studio's queries are scoped so that another studio's records are simply not reachable.
Per-client, too
The same principle applies within a studio: a client can only ever reach their own documents, transactions, and messages. Strict tenant isolation runs top to bottom.
Server-side always
Role-based access is enforced on the server for every request. The client is never trusted to decide what it may see.
Separation you can't argue with
Isolation lives in the database, not in a filter the interface could drop. One studio's queries can't reach another's records, one client can only see their own, and the server decides on every request.
- Enforced below the interface
- Scoped per studio and per client
- Checked server-side, every time
Off the ledger, onto the workspace
A filter in the interface that a crafted request can slip straight past.
Isolation enforced in the database, unreachable by hand.
One tenant's query could, on a bad day, read another's.
A studio's queries are scoped; another's records don't exist to it.
The browser decides what it's allowed to show.
The server decides, on every request, through RBAC.
Built to carry the weight
Not just the interface
Isolation lives in the database, where a hand-crafted request still can't reach another studio's records.
Right down to the client
Within a studio, each client reaches only their own documents, transactions, and messages. Tenancy runs the whole way down.
The server decides
Role-based access is enforced server-side on every request. The browser is never trusted to decide what it may see.
Everything, in the file
At the source
- Isolation in the database, not the UI
- No studio reads another's data
- Holds against hand-crafted requests
All the way down
- Per-client isolation within a studio
- Documents, transactions and messages scoped
- Strict tenancy, top to bottom
Server-decided
- RBAC on every request
- The client is never trusted
- Checks run before anything loads
Isolation isn't a filter in the interface that could be bypassed; it's enforced in the database itself.
Questions, answered
Straight answers about workspace isolation, in plain language.
Ask us anythingNo. Isolation is enforced in the database, not the interface. A studio's queries are scoped so another studio's records are simply not reachable, even by a request built by hand.
Yes. A client can only ever reach their own documents, transactions, and messages. Strict tenant isolation runs from the studio down to each client.
On the server, for every request, through role-based access control. The client is never trusted to decide what it may see.