PKPEEK Docs
Docs/Customers & tenants

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.

PEEK Platform Administrator

/peek/customers/tenant-a/1-5
Live walkthrough · Activation readiness and completion
/peek/customers/tenant-a/1-5
/peek/customers/tenant-a/1-5a

Activation readiness is calculated from saved state — organization scope, active commercial scope, verified identity profile and the initial-admin handoff — and only for the capabilities actually purchased. Missing optional modules never block activation.

From draft to active customer

  1. 1. Organization scope

    1.1–1.2

  2. 2. Customer scope & designation

    1.3

  3. 3. Subscriptions

    1.4

  4. 4. Identity profile

    1.8

  5. 5. Initial-admin handoff

    1.9

  6. 6. Readiness & activate

    1.5 — every blocker is rechecked at commit

  7. 7. Receipt

    1.5A — activation event, receiving administrator, next tasks

Note — Activation does not create source connections, agency users or blanket data grants. The completion page shows actual readiness and receiving-admin state and never implies source setup is complete. Refreshing it never creates a duplicate activation event.

1.5 · Activation Readiness

Review all prerequisites for tenant activation. Open it at /peek/customers/tenant-a/1-5 (any tenant ID you can access works in place of tenant-a). The primary action is Activate approved tenant, which requires customer.activate.

How 1.5 works

  1. 1. Calculate readiness from saved organization, active commercial scope, verified identity and initial-admin handoff

  2. 2. Display blockers then activate

Screen 1.5 contract

Fields shown
Organization, subscription, identity, handoff, policy, readiness evidence
Primary action
Activate approved tenant
Required capability
customer.activate
Validation
Recheck every required blocker at commit. Only prerequisites for purchased capabilities apply.
Successful outcome
One activation event records evaluated versions and returns the agency handoff status.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.1.5.action (acceptance test AT-UI-1.5)
Requirements
R02, R06, R28, R31, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.5
Boundary — Check readiness only for the purchased configuration. Missing optional modules do not block activation; verify PDCC agency access and initial administrator handoff.
Rejected even if the browser allows it — Let identity assurance expire between readiness display and activation; reject activation and identify the stale gate.

1.5A · Customer Activation Complete

Confirm completion and agency handoff. Open it at /peek/customers/tenant-a/1-5a (any tenant ID you can access works in place of tenant-a). The primary action is Open customer governance record, which requires customer.read.

How 1.5A works

  1. 1. Read the successful activation receipt and open the customer governance record or agency next-step guidance

Screen 1.5A contract

Fields shown
Tenant status, activation event, receiving administrator, next tasks
Primary action
Open customer governance record
Required capability
customer.read
Validation
Receipt must match tenant, environment and committed activation event.
Successful outcome
Show actual readiness and receiving-admin state; do not imply source setup is complete.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.1.5a.action (acceptance test AT-UI-1.5A)
Requirements
R02, R06, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.5A
Boundary — Activation does not create source connections, agency users or blanket data grants.
Rejected even if the browser allows it — Refresh the completion page repeatedly; create no users, credentials or duplicate activation events.

Related guides

Initial agency administrator handoff

Screen 1.9 — activate the agency-designated initial administrator through an independently verified, bounded acceptance flow.

Customer governance overview

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

Customer Directory

Screen 1.6 — search the customers you are assigned to and open one as an explicit tenant context.