PKPEEK Docs
Docs/SI services & Sigma

Portal preview, publish and suspend

Screens 4.6 and 4.8 — preview the agency SI settings with synthetic personas, then publish or suspend SI configuration.

PEEK Platform Administrator · PEEK Incident Operator

/peek/customers/tenant-a/4-8
Live walkthrough · Portal preview, publish and suspend
/peek/customers/tenant-a/4-8
/peek/customers/tenant-a/4-6

4.6 renders the agency’s SI settings view with a synthetic persona, SI mode and sample data so you can check the explanation drawers. 4.8 publishes reviewed SI configuration or applies a scoped, authorized suspension with an incident reference.

Heads up — Suspension takes effect at enforceable boundaries immediately. Restoration is a separate reviewed action that requires current authorization — queued work never resumes automatically.

4.6 · Customer Portal Preview

Preview how an agency sees SI configuration. Open it at /peek/customers/tenant-a/4-6 (any tenant ID you can access works in place of tenant-a). The primary action is Change preview scenario, which requires preview.use.

How 4.6 works

  1. 1. Choose synthetic persona, SI mode and sample data

  2. 2. Inspect the agency settings view and its explanations

Screen 4.6 contract

Fields shown
Synthetic persona, effective restrictions, explanation drawers
Primary action
Change preview scenario
Required capability
preview.use
Validation
Use only fixture identities and mock provider responses; disable all live write and external-call paths.
Successful outcome
Changing a preview scenario changes local simulated state only.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.4.6.action (acceptance test AT-UI-4.6)
Requirements
R02, R06, R18, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, SYS12, UI-4.6
Boundary — No live impersonation, actual connection or agency mutation.
Rejected even if the browser allows it — Inject a real tenant identity or production connection reference into preview; reject it.

4.8 · Review Publish & Suspend

Release or suspend SI configuration with impact visibility. Open it at /peek/customers/tenant-a/4-8 (any tenant ID you can access works in place of tenant-a). The primary action is Publish or suspend, which requires si_configuration.release or si.restrict.

How 4.8 works

  1. 1. Publish reviewed SI configuration or apply a scoped authorized suspension with an incident reference

Screen 4.8 contract

Fields shown
Diff, agency approval, review, suspension scope, incident link
Primary action
Publish or suspend
Required capability
si_configuration.release or si.restrict
Validation
Enablement requires readiness and current authority; restriction follows immediate stop rules.
Successful outcome
Affected SI work stops at enforceable boundaries; restoration is a separate reviewed action.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.4.8.action (acceptance test AT-UI-4.8)
Requirements
R02, R06, R10, R24, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-4.8
Boundary — Reactivation requires current authorization and does not replay pending actions automatically.
Rejected even if the browser allows it — Suspend then restore service; queued work must not resume automatically.

Related guides

SI services overview and continuity

Screens 4.1 and 4.7 — agency SI mode, service inventory, use cases, usage, quotas and degradation.

Incidents, containment and recovery

Screens 8.5 and 8.6 — apply preauthorized containment immediately, then restore service only after current authority and technical checks.

Synthetic previews

How the customer-facing previews in Groups 4, 6 and 7 work and what they can never do.