Customer portal operations

Monitor the portal together with the services it depends on. A page can load even when sign-in, data retrieval, or a background workflow is unavailable.

Include the static deployment context, customer API, identity provider, data stores, background workflows, and enabled integrations in your operating plan.

Monitor service health

Track these signals and assign someone to investigate each alert:

• frontend availability and static deployment context;
• API health and readiness;
• identity-provider and token failures;
• database connections and pool limits;
• queue backlog, retries, and poison messages;
• scheduled workflow health;
• proof submission and reconciliation;
• outbound email and callback delivery where enabled; and
• client and server errors in the workflows each customer role uses.

Validate the portal

After deployment or configuration changes, check the affected workflows. Release qualification should cover:

1. signed-out and signed-in routing;
2. setup-route behavior for the recorded deployment state;
3. sign-in and sign-out;
4. all six customer roles;
5. tenant, application, and audit-engagement scope;
6. application setup and SDK ingest;
7. policy, review, evidence, and outcome workflows;
8. settings that are visible for the operating model; and
9. accessible keyboard, focus, dialog, and side-panel behavior.

Backup and restore

Back up the stores named by the release architecture. List recovery dependencies separately: storage artifacts, Key Vault versions, protected ledger digests, deployment context, and external provider records.

A database backup alone may not restore those dependencies.

Test restore in an isolated environment. Verify data relationships, application access, background jobs, proof references, and exports after restore.

Certificates and DNS

Name the certificate owner and track expiry and renewal. Keep DNS records, redirect URLs, API origins, and private DNS aligned with the deployed environment.

Test renewal before the active certificate expires.

Release changes

Deploy the frontend, APIs, database scripts, and configuration as one qualified release candidate unless the release runbook explicitly permits independent rollout.