Notion Permissions for Client Work: Why Page Access Is Not Enough
Notion’s permission model is excellent for teams. It is incomplete for multi-client agencies. The confusion usually starts here: you build a beautiful filtered view titled “Acme — Projects,” share the page with Acme, and assume the filter is a security boundary. It is not.
What Notion permissions actually control
Notion grants access at the page (and, on higher plans, database page) level: view, comment, edit, full access. Inheritance flows down from parent pages. That means a guest invited to a child page may still navigate upward if parent permissions allow it, or discover linked databases that were never meant for them.
- Permissions are page-centric, not “this client’s rows only.”
- Linked database views can expose more than the filter you intended.
- Misconfiguration risk rises linearly with every new client page you add.
Why filters are not a security feature
A filtered linked view is a convenience for the person looking at the page. Depending on how the database is shared, viewers can often clear or change filters, open the source database, or follow relations into other records. Treat filters as UX, never as authorization.
Business and Enterprise page-level database access
Notion’s higher tiers add finer database page permissions, which help when collaborators need restricted access inside a shared database. That is still a different problem than “authenticate Client A and only return Client A’s rows through an API.” For agencies with dozens of clients, configuring page permissions per record does not scale operationally.
What “good enough” looks like for client portals
A production client portal needs identity (who is logged in), authorization (which rows they may see), and a surface that does not invite exploration of your internal workspace. Notion alone covers the first two poorly for external clients. A permission layer on top of Notion — like Portalize — checks the client’s identity on the server and only returns their scoped data.
Replace fragile page sharing with server-side scoped client portals.
Start freeRelated
Compare approaches in Portalize vs Notion sharing, or start from the how-to guide. If guest seats are your immediate pain, read the Notion guest limit workarounds.