LEARN
What is a client portal?
A client portal is a secure, private website where a business shares work with a specific client: files, project status, metrics, invoices, and messages, all in one place behind a login. Instead of scattering updates across email threads and attachments, the business posts everything to one workspace the client can check at any time. A good client portal shows each client only their own data, carries the right branding, and keeps a record of what changed and when.
Portals are most common in service businesses, such as agencies, contractors, consultancies, and restoration or field-service companies, where the work runs for weeks or months and the client needs a standing answer to "where are we?" The portal replaces the status-update email as the system of record.
What should a client portal include?
The contents vary by business, but a portal earns its place when it answers the questions clients otherwise send by email. Most portals converge on the same core set:
Beyond content, two structural pieces matter. First, named user accounts with roles, so you know who saw what and who did what. Second, a change history, so nothing is silently lost when a file is replaced or a number is corrected.
- Files: deliverables, contracts, reports, and photos, organized per client rather than per email thread
- Metrics and status: the numbers or job states the client checks most often, visible without asking
- Billing: invoices and payment status shown next to the work they cover
- Messaging: chat between the provider's team and the client, kept inside the workspace instead of a personal inbox
- Announcements: dated updates that replace the recurring status email
- Access control: named users, roles, and invitations, so accountability survives staff changes on either side
Branded multi-tenant portals vs. shared logins
The cheapest way to give clients "a portal" is a shared login: one account, or one generic dashboard, that every client visits. It works for exactly one client. With two or more, you face a choice between exposing everyone's data to everyone or maintaining separate copies of everything by hand. Shared logins also erase accountability, because every action traces back to the same account, and offboarding anyone means changing a password for everyone.
A multi-tenant portal solves this at the architecture level. One platform hosts many isolated workspaces. Each client's users sign in with their own accounts and can only reach their own tenant, and the separation is enforced in the database rather than merely hidden in the interface. Each workspace can carry the client's own branding and its own address, so the portal reads as the client's tool, not a screen they borrow.
This is also the practical difference between a client portal and a shared dashboard. A dashboard is one screen showing one set of data. A portal is a set of separate, permissioned workspaces that happen to share an engine.
The record is the point
A portal that only displays the current state of things is a report. A portal becomes a system of record when it also keeps history: which file replaced which, who changed a status, when an invoice was issued and when it was paid. Overwrites and quiet deletions destroy the answer to "what happened," which is usually the question that matters when a project is disputed or audited.
The strongest version of this is an append-only log, where corrections add a new entry instead of erasing the old one. The working principle is simple: one record, nothing lost. When evaluating any portal, ask what happens to the old value when someone edits a field. If the answer is "it's gone," the portal is a display, not a record.
How this looks in practice
Vercid is a multi-tenant business-operations platform that implements the pattern described above. Each client gets a branded workspace at their own subdomain, with a dashboard composed per client from widgets for metrics, files, announcements, and billing, plus in-workspace chat between the provider's team and the client. Members are named and role-based, sign-in supports Google SSO, tenant separation is enforced with Postgres row-level security, and every change lands in an append-only audit log with full-text search. A mobile app wraps the workspace with chat push notifications.
Common questions
What is the difference between a client portal and a shared dashboard?
A shared dashboard is one screen, usually behind one login, showing the same data to everyone who opens it. A client portal is a set of separate workspaces: each client signs in with their own account and sees only their own files, metrics, and billing. The difference matters as soon as you have a second client. With a shared dashboard you either expose every client's data to every other client or you stop using it.
Does a client portal need its own subdomain?
Not strictly, but a per-client address makes the portal feel like the client's own tool, keeps bookmarks unambiguous, and lets each workspace carry its own branding. Portals that live at one generic URL tend to be treated as the provider's tool that clients occasionally visit, which is how portals go unused.
Can email and shared folders do the same job as a client portal?
They can move the same files, but they lose the record. Email splits history across inboxes, shared folders overwrite versions silently, and neither shows status or billing next to the work. A portal keeps a single live record per client, so "where are we?" has one answer instead of a search through threads.
The fastest way to evaluate a client portal is to walk through a live one.
Book a walkthrough