Client Portal
End-to-end story. It reuses canonical pages. It does not re-teach screens. For a live workflow + messaging example, start from the template Client Approval Hub and Start from a template.
What this is / when to use it
Section titled “What this is / when to use it”A client portal is a private app where each client sees their own requests, files, and status, and staff see everyone (or their queue).
When not to: a public catalogue with no login. Use a public list + Content landing page.
Before you start
Section titled “Before you start”Notion databases: Clients (or Companies), Requests (or Deliveries), Users, optional Files/Versions. Connect Notion. Decide roles: Client, Staff, Approver.
Build it (story, not a second manual)
Section titled “Build it (story, not a second manual)”- Create an app or clone Client Approval Hub.
- Private apps + Sign up with default Role = Client.
- Identity: map Role and Active.
- Data restriction on Requests by Client/Company. Disable restriction on the staff list.
- Screens (canonical guides, do not fork):
- Client: Home, list of their requests, Form (Add Item), Details, Profile.
- Staff: Work Queue or an update list, Decision if you approve.
- Shared: Content welcome (optional public), Conversation for questions.
- App Navigation: different tabs per role. Hide Select Items and thank-you forms.
- First automation: wizard notify or approval.
- Publish & share. Test with View as Client and View as Staff.
Every control
Section titled “Every control”None that are unique to “client portal.” If you need a control, open the canonical page in the step above.
What users see
Section titled “What users see”Clients: home, their rows, submit, status, messages. Staff: queue and all rows. Approvers: Decision inbox.
Limits and plans
Section titled “Limits and plans”Same as Plans. Approvals and messaging need entitlements. File versions consume upload meters — rebind files after sync (save failed).
Example
Section titled “Example”A delivery portal: clients sign up, submit a delivery against contracted scopes (Select Items), upload files, see status. Staff use an update list + bulk received. Approvers use Decision. That is Client Approval Hub’s shape, not a new screen type.
Fix problems
Section titled “Fix problems”Client sees everyone’s rows → restriction. Staff sees nothing → disable restriction on their list. Save failed after adding a files property → rebind. Empty approval inbox → role + published automation, or the publish used the wrong topic / item type. Reviews use client.review.requested (decision); intake uses client.intake.submitted (task); Wait lists client.decision.approve / changes_requested / reject. See Topics that perform work.
Related
Section titled “Related”Client Review Hub in 15 Minutes (short). Topics that perform work. Mixed public–private. Other use cases stay stories that link the same pages.