Client portal: what to put behind the login, and what not to

A client portal promises to end the email archaeology: no more hunting for the latest invoice, the signed contract or the current status. It delivers on that only if the contents stay current — and the most common outcome is a login that clients try twice, find outdated, and stop opening. Then the questions come back by email, and now you maintain both.

So the design question is not what a portal could show. It is what you will keep up to date without being asked.

What belongs behind the login

• Documents that are already final: contracts, signed proposals, deliverables, reports. These do not go stale, and they are the most-requested thing.
• Money: invoices with status and payment history. "What do we still owe" is the second-most-common client question after "where is that file".
• Status of work in progress, at a level you will genuinely update — a stage and a date beats a detailed plan that ages badly.
• Contacts and next steps: who to ask about what, and what the client owes you before the next milestone.

The addition that usually backfires is a chat or ticket channel inside the portal. Clients already have email and a phone number; adding a fifth channel means messages arrive in a place nobody watches. If you do add it, route it into your normal inbox rather than expecting anyone to check the portal. Where the audience is staff rather than clients, the same questions produce an intranet instead.

Portal or shared folder?

Many businesses do not need a portal at all. A shared folder with named access, sensible naming and a clear structure delivers most of the benefit at none of the maintenance cost — and it is one fewer login for the client, which is what they actually care about.

A portal earns its place when clients are numerous enough that per-client folders become admin, when status matters as much as files, or when you need to show branded, controlled access rather than a link into your storage.

Building one that stays useful

1. Decide what updates on a schedule and who updates it. Anything without an owner will be stale within a month.
2. Give each client exactly what is theirs — check access separation on day one, and again after the first colleague joins.
3. Keep the login simple: email invitation, no forced account creation ceremony, and a password reset that actually works.
4. Put the newest thing first. Clients open a portal to find what changed, not to browse a filing system.
5. Send a notification when something is added — a portal nobody is told about is a portal nobody visits.
6. Review after two months: if you are still answering the same questions by email, the portal is not covering them.

For a lightweight version, Ettex Sites can host a client-facing page on your own domain with certificates issued automatically, 70+ sections and a live canvas, theme control so it matches your brand, forms that feed a built-in leads inbox, and built-in analytics showing visits and page stats — so you can see whether clients open it at all. The documents themselves live in Storage, where every file appears in one searchable list and sharing is deliberate: named people at Editor, Commenter or Viewer level, or a link when that is genuinely what you want. For many businesses that pairing replaces a portal entirely.

Independent suppliers bill differently from companies. A freelance invoice carries the same essentials plus tax status and payment details, and it is usually processed by someone who has never seen that supplier’s paperwork before.

Sending a document should not require an attachment. The safe way to share files online is a link with permissions, an expiry date and a record of who opened it, rather than a copy that lives in someone's inbox forever.

Why portals get abandoned

• Content that stops being updated, so the client learns the email is faster.
• A separate login the client has to remember for one supplier among dozens.
• Everything behind the login, including things the client would rather receive as an attachment — a signed contract they need to forward internally, for example.
• No notifications, so updates land silently.
• Access that was never reviewed, so a former employee at the client still sees current documents.

A client portal is worth building when you will maintain it. Final documents, money, honest status, and a notification when something changes — everything else is decoration that ages. Where the audience is staff rather than clients, the same questions produce an internal site, and the document approval workflow decides what may be published on it.