Client portal overview
The client portal is a signed-in dashboard for your client's own people. They open {workspace}.upall.app, sign in with their password or Google account, and land on a live view of their systems — nothing else in your workspace. It's the difference between telling a client "everything's fine" and letting them watch it be fine.
What a client sees
- Your branding, and theirs. The page carries your MSP name and logo; if the client has a logo of their own, it appears too. A small "Powered by UpAll" footer stays on everything client-facing.
- An overall banner. One verdict across all their monitors — operational, degraded, issues, unknown, or paused, worst state first — together with their month-to-date uptime percentage.
- Each site, with its monitors. Grouped by site, every monitor shows its current status, its uptime percentage for the month, and 90-day history bars with the uptime for that window. Only monitors attached to the client's sites appear; internal monitors (those without a site) are never visible in any portal.
- Their last 10 incidents. Title and full body text, the start time, and — once closed — "resolved in N minutes". Unlike a status page, the portal shows incident bodies, because the reader is known: these are the client's own incidents, and staff wrote those bodies for them. See how incidents open and close.
Read-only, and self-refreshing
The portal has no buttons to press. Clients can't edit monitors, pause checks, or close incidents — they observe, you operate. The page also refreshes itself every minute without a reload, so it can sit open on a screen in the client's office and stay current.
Portal vs. status page
Both show live status; they answer different questions for different audiences.
| Public status page | Client portal | |
|---|---|---|
| Access | anyone with the link | signed-in account only |
| Identity | anonymous | a known person, tied to one client |
| Scope | exactly the monitors you picked | all monitors on the client's sites |
| Incidents | titles and times only | full text, plus resolution durations |
| Uptime figure | per monitor (if enabled) | per monitor and overall for the month |
| Revoking access | regenerate the link for everyone | remove one person's account |
A status page is a broadcast: one anonymous link, contents you curate toggle by toggle, incident titles only. The portal is a relationship: each viewer is a named account belonging to exactly one client, sees everything on that client's sites automatically, and reads the full incident record you wrote for them. Many MSPs use both — a status page for wide, low-friction sharing, the portal for the client's IT staff who want detail.
Getting clients in — and checking their view
Portal accounts don't self-register. You create them with an invite link, or by approving a Google access request from someone who signed in without an account. And before you invite anyone — or whenever a client calls about what they're seeing — you can open their portal exactly as they see it from the console.