Where your data lives
One boundary, and why another workspace's record answers "does not exist".
The boundary is the workspace
Everything — contacts, engagements, documents, meetings, indicators — belongs to one workspace and never leaves it.
That is not a filter in the interface; it is enforced on every read path. Lists come back empty, search finds nothing, and the assistant does not know the data is there.
Why "not found" rather than "not allowed"
Open a record from another workspace and the answer is "not found".
"Not allowed" is itself a leak: it confirms such a record exists. Repeat that confirmation enough times and you can work out whether a competitor holds a particular client.
What our support team can see
Platform staff can operate workspaces — creating them, suspending them, managing seats — but that is not the same as seeing content.
The vendor console returns no document, feed or meeting, and anyone without a membership in your workspace sees nothing on any content path.
Read this next
- Security & dataWho can see whatReads are open, with two exceptions — and both exceptions share one mechanism.
- Workspace & teamMore than one workspaceSwitching, the data boundary, and how one sign-in covers all of them.
- When something does not work"Not found" or "not allowed"Two different messages with two completely different meanings.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.