BuildBuild a client portal
Build/Build a client portal
9 min read·02 / 08

Build a client portal

A portal is a branded app for one client, built from blocks. You choose which blocks appear, point them at your mapped fields, scope the data, and publish — usually in a single sitting.

1 · Add the client

Open Clients → Invite client. A client account is the container a portal hangs off — it holds the people who can sign in and the scope that filters their data.

console / clients
The Clients list — each row is one account, with its portal status, plan, and MRR.
The Clients list — each row is one account, with its portal status, plan, and MRR.
  1. 1Invite client opens the new-account flow.
  2. 2Portal status: Draft, Live, or Paused.
  3. 3Tabs filter by status so a long client list stays manageable.
  1. 1
    Name the account
    Give the client account a name. Every project, file, and invoice you assign to it is scoped to this client — PortalTable filters every block to their rows automatically.
  2. 2
    Add client contacts
    Enter the email addresses that may sign in. They become free client users — invite as many as you like, no per-seat cost.
  3. 3
    Leave it as a draft for now
    Drafts are private to your team. You'll publish once the blocks and branding look right.

2 · What the portal shows

Every portal carries the same sections down its left rail. A section stays quiet until it has something in it, so a design retainer leaning on Projects and Approvals looks different from a fractional-ops engagement leaning on Projects and Invoices — without either of you configuring anything.

Projects
Live status, milestones, and owners straight from your workspace. The block most portals start with.
Approvals
Send deliverables for sign-off and capture timestamped decisions against the record.
Files
Deliverables you share down to the client, marked visible one by one. Client-side uploads are coming.
Invoices
Issue invoices with your own payment link, and see paid status reflected in the portal.
Updates
Post a note to a client and it lands in their portal feed, against the project it belongs to.
Blocks stay live
Each block reads straight from your workspace. Update a project, post an update, or mark an invoice paid, and the client sees it next time their portal loads.

3 · Preview and publish

Use Preview as client to see exactly what the client will — scoped to their data, with nothing internal showing. When it looks right, flip the account from Draft to Live. The client gets a magic-link invite to their portal.

portal / client view
The published result — a branded home the client signs in to. This is what Preview shows you.
The published result — a branded home the client signs in to. This is what Preview shows you.
  1. 1Your logo and name — no PortalTable branding on paid plans.
  2. 2The client's rail — the same sections in every portal.
  3. 3Cards summarize just this client's projects, approvals, and balance.
Your own subdomain
Claim you.portaltable.com and every portal is served from it over HTTPS. Set it under Portal branding. Fully custom domains (clients.youragency.com) are coming on Studio.