Portal · access · handover
● portal

Portal rollout

Client access with clear boundaries.

What clients can see, how notifications should behave, handover pack expectations, and billing touchpoints without turning the portal into an email inbox.

Visibility Alerts Handover Billing

Roll out portal access after workspace roles and door IDs are stable — fewer “wrong building” support tickets.

What clients see

Portal · Riverside Ltd
Inspection packs
PDFs tied to dated visits
Quotes + RAMS
Same versions as email thread
Invoices
Status visible · download links
Issues
Raised doors tracked to register
Activity
Who opened which pack · when
Remedials
Status visible · not internal chat

Set expectations before inviting users — surprises erode trust fast.

Publish a one-page “what the portal is / is not” before first invite — especially around billing visibility.

Notifications

Engagement
MonQuote issued · in-app + email
TueReminder · no login yet
WedUser activated · 2FA prompt
ThuPack viewed · audit line on record
FriInvoice paid · Stripe receipt emailed
MonIssue raised · threaded to coordinator

Cadence should match your commercial tone — not spam, not silence.

Mute noisy defaults for large programmes — coordinators can still see everything in the workspace.

Access control

Who invites whom
OwnerInvites + removes client admins
CoordinatorManages door-level visibility
Read-onlyPacks only · no billing edits
Client adminInvites own team · property scoped
Finance contactInvoices · pay links only

Full checklist covers handover wording and related security guide.

Guide below Security →

Offboard portal users when contracts end — workspace audit trail remains the long-term record.