Notion Project Management Template for Small Agencies in 2027: Client Portal Without Guest Seat Fees
You can give clients a real project portal in Notion without paying for guest seats — if you build the portal from shareable public pages, database views and synced blocks instead of inviting clients as workspace guests. The setup takes about 15 minutes on a paid plan and costs $0 in extra seats, because public page sharing does not consume a member or guest license.

Most small agencies hit the same wall: the workspace works fine for the team, then a client asks “can I just see where things stand?” and the honest answer is a screenshot or a shared Google Doc. Inviting them as a guest is the obvious fix until you read the seat math — Notion’s Business plan is billed per seat, and guest seats are billable on paid plans. Five clients becomes five seats becomes a line item nobody budgeted for. The alternative is a client-facing portal that lives inside your existing workspace but is shared as a public link, so the client sees progress and you see no invoice change.
Which client portal approach in Notion actually avoids guest seat charges
The only approach that reliably avoids guest seat fees is publishing a read-only page to the web and sharing that URL, because public pages are viewable by anyone with the link and are not counted as workspace members or guests. Every other method — inviting clients as guests, duplicating pages into a client workspace, or handing over a CSV export — either costs seats or costs you maintenance time.
| Approach | Guest seat cost | Client can comment? | Setup time | Best for |
|---|---|---|---|---|
| Public page link (Share → Publish) | $0 | No | ~5 min per page | Status dashboards, deliverables, timelines |
| Invite client as workspace guest | Billable seat on paid plans | Yes | ~2 min | Long retainers with daily collaboration |
| Duplicate template into client’s own Notion | $0 to you | Yes, in their workspace | ~20 min + ongoing sync | Clients who already pay for Notion |
| Shared database view via public link | $0 | No | ~10 min once, reused | Task boards and milestone trackers |
| PDF or CSV export sent weekly | $0 | No | ~15 min per send | Clients who refuse links entirely |
There are five common approaches to the client portal problem. Only two are worth your time for an agency under ten people: the public page link and the shared public database view. The guest invite is fine when a client is genuinely embedded in your workflow, but it is the wrong default.
Why guest seats are the wrong default for agency client portals in 2027
Guest seats are billable on Notion’s paid plans, so every client you invite as a guest adds a recurring cost that scales with your client count rather than your team size. For an agency with eight active clients, that is eight seats doing almost nothing — reading a status page once a week.
Notion’s official pricing page lists the Free plan for individuals, Plus at $10 per seat per month billed annually ($12 billed monthly), Business at $20 per seat per month billed annually ($24 monthly), and Enterprise as custom pricing. Guests are billed on paid plans; on the Free plan you can invite up to 10 guests at no cost, but the Free plan caps file uploads and block usage in ways that break down for client work. The practical read: if you are on Plus or Business, treat every guest invite as a $120–$240 per year decision.
The one change that makes the biggest difference is deciding, per client, whether they are a collaborator or a reader. Collaborators get a guest seat and earn it. Readers get a published link. In most small agencies, roughly 80% of clients are readers.
How to build a read-only client portal with published Notion pages in about 15 minutes
A read-only client portal is a single parent page containing a project summary, a filtered task database view, a deliverables list and a timeline, published to the web as one link. The client bookmarks it; you update the databases as normal and the published page reflects changes automatically.
The setup takes about 15 minutes for the first client and about 3 minutes for every client after that, because you duplicate the parent page and swap the client relation. Here is exactly how:
- Create a Clients database with properties for Client name, Status, Start date and Portal URL. One row per client.
- Create a Projects database with a Relation property pointing to Clients, plus Status, Owner, Due date and Phase.
- Create a Tasks database related to Projects, with Status, Assignee, Due date and a checkbox for “Client visible”.
- Build one parent portal page per client. Add a linked view of Projects filtered to that client, and a linked view of Tasks filtered to that client and Client visible = checked. This is the filter that keeps internal notes off the public page.
- Add a synced block for the “this week” summary. Synced blocks update everywhere they appear, so one edit covers the portal and your internal dashboard.
- Publish the parent page via Share → Publish to web, then paste the URL into the Clients database Portal URL field.
The filter on step 4 is the whole system. Without it, your internal task names, rate notes and half-finished ideas go public. With it, the published page is a clean subset of the same database your team already uses — no duplicate data entry, no second tool.

What to put on the published portal page so clients stop emailing for status updates
A client portal that prevents status emails needs four things: current phase, what is due next with a date, what is waiting on the client, and a link to deliverables. Anything beyond that is decoration the client will not read.
Put the “waiting on you” section at the top, not the bottom. In practice this single reordering removes most back-and-forth, because the client’s first question on opening the page — “what do I need to do?” — is answered before they scroll. Keep the page to one screen on a laptop. If a client has to scroll twice to find their action item, they will email instead.
Two configuration details matter more than they look. First, published pages are read-only for visitors, so there is no comment thread on the portal — route feedback to a single named email address or a form linked at the bottom. Second, if you publish a database view, check whether the view exposes properties you did not intend; hide columns in the view itself before publishing rather than relying on the filter alone.
Which Notion template structure to start from for an agency client portal
The fastest starting point is a project management template with a Clients–Projects–Tasks relation chain and at least one pre-filtered client view; building that relation structure from a blank page takes 45–60 minutes, while adapting a template takes about 10. Look for three things when choosing one: a relation property linking tasks to clients, a checkbox or select property you can use as a visibility flag, and a dashboard page designed to be published rather than viewed internally.
Skip templates that are built around a single flat task database. They look tidy in the thumbnail and fall apart the moment you need per-client filtering, because there is no client object to filter on. Skip anything that ships with 20+ databases for a five-person agency; you will maintain the template instead of the projects. The templates worth adapting are the ones with three or four linked databases and a clear naming convention.
What breaks first when you run an agency portal on published pages
The first thing to break is version drift: a project page gets duplicated for a new client, the filter still points at the old client, and the portal shows the wrong tasks. The fix is to always duplicate the parent portal page rather than the project page, then re-point the relation filter in one place.
The second failure is publishing a page that contains a linked view of a database the client should not see in full. Published database views expose the rows the view returns, not the whole database — but the view’s own filters and hidden columns are what determine that, so audit the view, not the database. The third is forgetting that publishing is a per-page action: a child page added later is not automatically public in the way you expect, so re-check the portal after any structural change.
The bottom line on client portals without guest seat fees
Publish one parent page per client, filter the linked views on a “Client visible” property, and keep guest seats for the handful of clients who genuinely collaborate inside your workspace. That decision alone keeps a small agency’s Notion bill tied to headcount rather than client count, and it takes about 15 minutes to set up the first time.
Today’s next action: open your Projects database, add a checkbox property called “Client visible”, and tick it on the five tasks a current client would want to see. That is the entire foundation — the portal page is just a filtered view of what you already have.
Primary source: Notion Help Center.
Related reading: How to Use Notion for Project Management: Complete Guide.
If this helped, this next one will too: The Ultimate Notion Setup for Students: Organize Your Classes in 2026.
For a ready-to-use framework, see our free Notion team project management templates you can duplicate in one click.