Docs/Customers & tenants

Customer scope and administrators

Screens 1.3 and 1.3A — define the agency customer boundary, designate initial administrators, and configure department-wide purchases.

PEEK Platform Administrator

/peek/customers/tenant-a/1-3

Live walkthrough · Customer scope and administrators

Customer scope and administrators — /peek/customers/tenant-a/1-3a — /peek/customers/tenant-a/1-3a

The customer record defines the tenant boundary: department, agency, authorized scope and the designation evidence for the agency’s initial administrators. Contacts recorded here are references, not memberships — the actual activation of an administrator happens through the verified handoff in 1.9.

Department-wide purchases — A department can buy for several agencies (1.3A). Each included agency must be listed explicitly and becomes its own child tenant with an isolated access boundary. The parent purchase never aggregates protected agency records or creates cross-agency memberships.

1.3 · Customer Scope & Administrators

Define the agency customer boundary and designated initial administrators. Open it at /peek/customers/tenant-a/1-3 (any tenant ID you can access works in place of tenant-a). The primary action is Prepare customer record, which requires customer.draft.

How 1.3 works

1. Set customer agency scope, contact references and initial administrator designation evidence
2. Save for handoff

Screen 1.3 contract

Fields shown: Tenant, department, agency, authorized scope, designation evidence
Primary action: Prepare customer record
Required capability: customer.draft
Validation: Contacts are not memberships. Required designation evidence and tenant uniqueness must be checked.
Successful outcome: Customer draft links to 1.9 for verified initial-admin activation.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.1.3.action (acceptance test AT-UI-1.3)
Requirements: R02, R06, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.3

Boundary — Initial administrator activation is completed through the verified handoff in 1.9.

Rejected even if the browser allows it — Enter a PEEK employee email as designated agency admin without agency designation; prevent activation.

1.3A · Department-wide Customer Scope

Configure a department purchase with explicitly included agencies. Open it at /peek/customers/tenant-a/1-3a (any tenant ID you can access works in place of tenant-a). The primary action is Review department scope, which requires customer.draft.

How 1.3A works

1. Enumerate agencies covered by a department purchase and display the entitlement allocation and isolation impact

Screen 1.3A contract

Fields shown: Included agencies, isolated scopes, shared entitlements, delegation
Primary action: Review department scope
Required capability: customer.draft
Validation: An agency must be explicitly included. Parent purchase does not aggregate protected agency records or create memberships.
Successful outcome: Commercial scope lists child agency tenants with separate access boundaries.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.1.3a.action (acceptance test AT-UI-1.3A)
Requirements: R02, R06, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.3A

Boundary — A department purchase does not confer cross-agency record access.

Rejected even if the browser allows it — Add a department entitlement and query a child agency without membership; deny protected data.

Related guides

Initial agency administrator handoff

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

Modules and subscriptions

Screen 1.4 — record purchased module entitlements, terms and quotas with commercial evidence; the module catalog explained.

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.