Restricted documents
When a document should exist for a named few and nobody else.
Open is the default; restricting is a deliberate act
Documents are readable across the workspace, and that is the default state. Restricting one is a decision somebody makes — never something that happens on its own.
Once a document is restricted, it does not exist for anyone outside its access list: not in the document list, not in search results, and the assistant does not know it is there.
How the access list behaves
- The list is a set: granting access to someone who has it does not create a second row
- You can seed it from an engagement's team — but that is a snapshot, and it does not follow the team afterwards
- Reopening a document does not erase the list; restrict it again and the same list returns
- A meeting transcript follows that meeting's access list and never takes one of its own
"Does not exist" and "not allowed" are two answers
If a document is hidden from you, the answer is "not found" — saying "not allowed" would itself confirm that such a document exists.
But if you can read the document and simply may not change its access list, the answer says so explicitly. The distinction is deliberate.
Read this next
- Security & dataWho can see whatReads are open, with two exceptions — and both exceptions share one mechanism.
- MeetingsWho can see a meetingA meeting is born restricted. Opening it up is a decision.
- 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.