If you are building a Notion client portal, the safest pattern is to share a portal page with each client and use page-level access (database permissions rules) so clients only see records assigned to them, without ever giving them access to your master databases. This approach pairs well with linked database views (see our related walkthrough: share Notion databases with guests without paying for member seats) and can be extended with automations in Notion, Make, or Zapier.
What âpage-level accessâ actually means in Notion
Notionâs page-level access lets you write a rule on a database that says, âA person can only see database pages where the Person property contains them.â This is how you prevent a guest client from viewing other clientsâ records.
The key misconception to avoid
Sharing a database view is not the same as sharing one page. If a client can navigate âbackâ to your database and they have broad access, they can potentially see more than you intended.
The safest client portal setup (recommended)
1) Keep a single master database
Keep your master database private to your internal team. This is where all client records live.
2) Add a Person property used for access
Add a Person property such as:
- Client user
- Portal user
- Allowed viewers
This property is what the permission rule will reference.
3) Create a permission rule on the database
Create a rule that grants access only when:
- The Person property contains the current user
Decide whether the client should have:
- Can view
- Can edit
4) Share a portal page, not the database
Create a dedicated portal page per client and place linked views of the master database inside the portal.
Then share only the portal page with the client as a guest.
Common portal problems (and how to fix them)
âMy client can click back and see everythingâ
This usually means the client has access to a higher-level page or the master database. Remove broad access, then rely on the portal page + linked database views.
âMy client cannot upload filesâ
Check both:
- The clientâs permission level (must be able to edit where the file block lives)
- Whether the file block is inside a database page or page they can edit
Practical checklist before you send a portal link
- Confirm the client is a guest, not a workspace member.
- Confirm the client can only access the portal page you shared.
- Confirm the database permission rule filters records correctly for that client.
- Test file upload and comments from the client account.
When to use Notion Automation (optional)
If you want a notification when a client adds something (a file, deliverable, or request):
- Use a database property change trigger where possible.
- Or add a lightweight workflow in Make or Zapier when you need routing, formatting, or Slack notifications.
CTA
If you want a secure client portal pattern built the right way (so clients only see their own work), book a call here: Book a discovery call
