PKPEEK Docs
Docs/Oversight, support & audit

Customer governance overview

Screen 8.3 — governance posture across your authorized customers: entitlements, policy review, exceptions, handoffs and incidents.

All PEEK operators with governance.read

/peek/customers/tenant-a/8-3
Live walkthrough · Customer governance overview
/peek/customers/tenant-a/8-3

The governance overview is the oversight dashboard for a customer. Module status, handoff review status and service health are separate signals; operational health never implies business authorization (a healthy service with expired agency authority does not show as authorized). Counts are scoped and timestamps explicit.

8.3 · Customer Governance Overview

Review governance posture across authorized customers. Open it at /peek/customers/tenant-a/8-3 (any tenant ID you can access works in place of tenant-a). The primary action is Open scoped issue, which requires governance.read.

How 8.3 works

  1. 1. Review purchased capability, policy review, handoff counts, exceptions and service health

  2. 2. Open authorized scoped issues

Screen 8.3 contract

Fields shown
Scope, entitlement, policy review, active exceptions, incidents
Primary action
Open scoped issue
Required capability
governance.read
Validation
Counts are scoped and timestamps explicit; operational health is separate from business authorization.
Successful outcome
Oversight routes owners to the relevant PEEK or agency task without exposing protected packages.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.8.3.action (acceptance test AT-UI-8.3)
Requirements
R02, R06, R28, R33, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-8.3
Boundary — Separate module status, handoff review status and service health. Oversight shows sanitized counts and evidence references, not protected package contents.
Rejected even if the browser allows it — Healthy service plus expired agency authority must not display the capability as authorized.

Related guides

Policy drift and exceptions

Screen 8.4 — compare released rules with effective configuration and route remediation.

Incidents, containment and recovery

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

Activation readiness and completion

Screens 1.5 and 1.5A — evaluate readiness blockers for the purchased configuration, activate the tenant and read the activation receipt.