PKPEEK Docs
Docs/Customers & tenants

Customer Directory

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

All PEEK operators with customer.read

/peek/customers
Live walkthrough · Customer Directory
/peek/customers
/peek/customers/tenant-a/1-6

The Customer Directory is the PEEK home page (/peek redirects here). It lists only the agency customers (tenants) your operator assignment covers. Every detail view stays tenant scoped and uses sanitized oversight metadata.

  1. 1

    Filter

    Narrow by Department, Agency, Customer status and Modules. Filters cannot broaden your scope — counts and pagination are computed server side from your assigned customers.

  2. 2

    Open a customer

    Select a row. This sets an explicit tenant and environment context and clears the prior tenant’s workspace drafts.

  3. 3

    Start a new customer

    New customers start at 1.1 Department & Agency Selection as a draft.

Seeded tenantNameStatusSI modeAutomation
tenant-aCBP demonstrationdemo_onlylimitedenabled
tenant-bAgency B demonstrationdemo_onlyoffoff

1.6 · Customer Directory

Locate an authorized customer context. Open it at /peek/customers/tenant-a/1-6 (any tenant ID you can access works in place of tenant-a). The primary action is Open customer, which requires customer.read.

How 1.6 works

  1. 1. Search permitted customers by department, agency, status and module

  2. 2. Select a tenant context

Screen 1.6 contract

Fields shown
Department filter, agency filter, customer status, modules
Primary action
Open customer
Required capability
customer.read
Validation
Server scopes search, result counts and pagination to assigned customers; filters cannot broaden scope.
Successful outcome
Opening a result sets explicit tenant and environment context and clears the prior tenant workspace.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.1.6.action (acceptance test AT-UI-1.6)
Requirements
R02, R06, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.6
Boundary — Every detail view remains tenant scoped and uses sanitized oversight metadata.
Rejected even if the browser allows it — Guess an unassigned customer identifier; show no customer content or enumeration detail.