See exactly who can see what.
Everything is private until you share it. Sharing is one click, shown as an exact preview, and it holds the same way for people and for their AI tools.
- Engineering handbookEveryone
- Payroll migrationMTDOHRFinance
- Salary bandsRKRestricted
- My draft notesSOOnly you
Levels that mean something
Read, edit and manage are separate. Share with a person, a team or everyone, down to a single property such as salary.
Teams flow down, not up
Sharing with Engineering reaches its sub-teams. Being in a sub-team never grants access to the team above.
One rule for every door
The app, search, MCP, the API, the CLI, exports and AI summaries all ask the same question first, before anything is ranked or counted.
AI suggests. People decide.
When a space is new, Contextely proposes a sharing plan: who should read it, and why. You see the exact change in numbers of pages and people before you accept.
The suggestion never applies itself.
Suggested: everyone can read
These pages look like internal how-to guides with no personal data, so most companies share them widely.
- Pages affected
- 38
- People who gain access
- 112 of 150
- Who still cannot read it
- Contractors group (38)
- Level
- Read only
Adaptive or strict, per view.
Adaptive views show each person what they may see. Strict views open only for people who can see every row and property they cover.
- Search relaunch
- Pricing page refresh
- Office move
- On-call rota
Sam sees the four projects shared with him. Counts and groups add up to those four.
This view is not available to you
A strict view only opens for people who can see every row and property it covers. Sam cannot see the 2027 hiring plan, so the view does not open for him and is not listed.
Use strict for a report that must always be complete.
Admins manage. They do not read everything.
An admin can see that a restricted collection exists and who owns it. To read it, they ask for break-glass access with a reason.
The owner is notified at once, the access is short, and every step is in the audit log.
Agents and syncs raise proposals.
When an agent or a sync disagrees with something a person wrote, it does not overwrite it. It raises a proposal with the evidence, and the owner accepts or rejects it.
Support agent, from ticket #4471, 2 hours ago
Enterprise first response: 8 hours 4 hours
Written by Anita Cole on 3 March. The agent found 6 tickets that say 4 hours.
Questions
Can an admin read everything?
No. Admins manage structure and sharing. To read restricted content such as salaries they make a break-glass request with a reason, the owner is told straight away, and the access ends on its own and is logged.
What does a person see when they lack access to something?
Nothing. The row, the page or the search result is not there, and counts are worked out without it. We answer 'not found' rather than 'forbidden', because 'forbidden' would confirm the thing exists.
Do AI tools get the same rules?
Yes. Every agent acts for one person and can never see more than that person. Read access never implies write access.
Does AI decide who sees what?
AI suggests a sharing plan and shows the exact result. A person approves it. Nothing widens access without a person saying yes.
Start with what you already have.
Free for up to five editors. Unlimited readers on every plan.