Notion adds column permissions: control who and which agents see each database property
TL;DR
Since Notion 3.8 (October 13, 2026), database owners can set which properties each person or agent can view or edit. It means one database can hold sensitive fields, like compensation or restricted customer data, without splitting it into separate databases.
- Status
- Live
- Released
- Plans
- Not specified
- Last verified
What changed
Notion databases now support permissions at the property (column) level. A database owner can decide, per person and per agent, which properties are visible and which are editable.
Notion's own examples:
- Recruiting: keep compensation hidden from interviewers while they work in the same candidate pipeline.
- Support agents: let an AI support agent work tickets without seeing restricted customer data.
Why it matters
Until now, the only way to hide a sensitive field in Notion was to move it into a separate database and relate the two, or to lock down the whole page. That workaround broke views, formulas and automations, and it made Custom Agents harder to scope safely.
Column permissions also apply to agents, not only people. That is the important part: you can give a Custom Agent access to a whole database and still keep specific fields out of its context.
Where to use it first
- Hiring pipelines: salary bands, offer details and interview scores.
- CRMs: contract values, discounts or personal contact details.
- HR and people ops: performance notes and personal information.
- Any database a Custom Agent touches: hide fields the agent does not need, so it cannot read or overwrite them.
Notion Coach take
This removes one of the most common reasons we split databases in client builds. If you have a "Private" twin of a database that only exists to hide two fields, it is worth planning a merge. Test views, rollups and agent behaviour on a duplicate first.
Frequently asked questions
Can you hide a property in a Notion database from specific people?
Yes. Since Notion 3.8 (October 13, 2026), database owners can control which properties each person can view or edit.
Do Notion column permissions apply to AI agents?
Yes. Notion says owners can control which properties each person or agent can view or edit, so a Custom Agent can be kept away from sensitive fields.
Which Notion plans include column permissions?
Notion's release notes do not specify plan availability. Check your workspace settings or Notion's help center for your plan.