Steps
- Give the sites a client first: on each site’s page choose it under Client, or A new client... for a new one. A portal shows one client, so the invitation names one.
- On Members, invite the contact by e-mail and choose that client under What they see. The role is viewer: read only.
- The contact signs in or creates an account with that address and opens the link in the e-mail. The invitation expires like any other, and you can withdraw it.
What the client sees, and what not
- Their own sites: the status, the checks, incidents with their timelines and evidence, planned maintenance, the risk radar and site security findings of those sites, status pages and monthly reports.
- Not your other clients, your members, billing, alert channels, API keys, branding settings or your data exports. The server refuses those, not only the screen: a site of another client answers as if it did not exist.
- Planned maintenance for your whole organisation shows as Scheduled maintenance with its times, without your title or details, unless you made it public on the status page.
- The assistant answers their questions from their own sites’ data, in fixed answers; it never sends their questions to an AI model.
- With white label (Agency and Agency Plus plans) the portal shows your name, logo and colour.
Their own alerts
To send a client the alerts of its own sites, add a channel on Alerts and choose Only the sites of that client under Whose alerts: an address, Slack, Teams or any other kind. Its alerts carry no acknowledge link unless you tick Allow acknowledging from this channel. A client contact can also turn on notifications for their own phone (how); they get that client’s incidents only.
Plans and seats
- The client portal is part of the Team, Agency and Agency Plus plans. A client contact takes no seat of your team; the plan limits how many contacts can see a portal, and the pricing page says how many.
- To end access, use Remove next to their name on Members. It ends at once.