A project portal should let a client find their brief, review material and outstanding decisions without exposing another customer’s work. A clean dashboard helps navigation, but its appearance says little about the actual access boundary.
This matters when an agency builds a Notion portal from shared project databases. Filtering a view to one client changes the records shown in that view. It does not, by itself, prevent someone with wider database access from reaching other records. Hiding a property is also a display choice, not a confidentiality control.
Decide what is shared before styling the page
List the material the client needs: perhaps a brief, a milestone schedule and review links. Keep the team’s internal estimates, private notes and other clients’ information outside that package. Use a separate client area or a permissions design that actually enforces the intended boundary.
The Notion client-portal permission checks explain the distinction between filtered views and access rules. Some database page-level rules depend on Business or Enterprise plans; do not assume a copied portal brings those capabilities or permissions with it.
Choose the least access that supports the agreed interaction. A client who only approves a design may need to comment, not edit the page structure. If the client needs to change information, decide which information and how the team will review those changes.
Review the route through the portal
- Open the client-facing page using an authorized test identity with the intended client permissions.
- Follow each linked document and database entry. Check the destination, not just the embedded preview.
- Try the paths that should be unavailable, including another client’s page and internal planning areas.
- Review inherited access from parent pages and any broader grants. A narrow rule does not cancel wider access granted elsewhere.
Repeat the review after moving a source database or changing a parent page. Keep a short note of the intended audience and who owns the sharing decision. For related workflow design, NotionSolutions’ independent workspace guides cover connected tasks, client intake and project reviews. Treat permissions as part of the handover, with someone responsible for checking them again.
