PKPEEK Docs
Docs/Getting started

PEEK Administration Center overview

The internal PEEK operator portal that governs commercial capability, platform boundaries and technical release for every agency customer — 68 contract-driven screens in eight groups.

PEEK Platform Administrator · PEEK Technical Reviewer · PEEK Entitlement Administrator · PEEK Support Operator · PEEK Incident Operator

/peek
Live walkthrough · PEEK Administration Center overview
/peek
/peek/customers
/peek/customers/tenant-a/1-4
/peek/customers/tenant-a/8-3

The PEEK Administration Center is the internal portal PEEK staff use to set up and govern agency customers of the Procurement Digital Command Center (PDCC). It is built from the PEEK Admin Full SRS v1.0 package: 68 canonical screens, 134 requirements and 148 acceptance specifications, organized into eight groups. Opening /peek redirects to the Customer Directory at /peek/customers.

What PEEK governs — and what it does not — PEEK governs commercial capability, platform boundaries and technical release. The agency app owns routine users, actual source and SI connection setup, business acceptance and within-bound publication. Nothing published in the PEEK center adopts itself for an agency, creates agency users, enters secrets or grants record access.

The eight groups

#GroupScreensWhat it covers
1Customer Setup1.1–1.11Organization scope, customer boundary, identity, initial administrator handoff, modules and activation.
2People & Authority2.1–2.2Agency administrative role catalog, delegation ceilings and persona templates.
3Policies & Workflows3.1–3.11Policy center, inheritance, recommendations, workflow and document templates, release, exceptions, rollback and handoff governance.
4SI Services4.1–4.10Supervised Intelligence (SI) provider profiles, processing boundaries, Sigma routing, preview, continuity and credential custody.
5Agents & Governors5.1–5.7Agent templates, governors, execution identity, communication rules, simulation and suspend/recover.
6Data & Connections6.1–6.8Connector catalog, methods, permitted use, delegated connection admin, change review and oversight.
7Experience & Studio7.1–7.8Persona experiences, navigation visibility, branding bounds, Studio components, roles, preview and release.
8Oversight & Audit8.1–8.8Support access, audit, governance posture, drift, incidents, recovery, reports and offboarding.

The sidebar lists all 68 screens under their group. Every screen opens inside a customer context at /peek/customers/:tenantId/:screen (for example /peek/customers/tenant-a/1-4). Two pages sit outside any tenant: the Customer Directory and Operator assignments at /peek/operators.

Core principles you will see everywhere

  • Separation of entitlement, enablement and access. Purchasing a module (1.4) does not enable it for the agency, and enabling it does not grant any user data.
  • Draft → independent review → publish. Every "Publish…" action goes through the catalog lifecycle: a preparer drafts, a *different* PEEK Technical Reviewer approves the exact diff hash, then it is published.
  • Core independence. Every paid module works with Shared Core alone; no paid peer module is ever an implicit prerequisite (1.10).
  • Recommendations are not decisions. Persona, policy, SI and experience recommendations are released for agency review; the agency adopts them in its own app.
  • Restrictive stops are immediate. Containment (8.5) and SI or agent suspension take effect at once; restoration is always a separate, reviewed action that never replays queued work.
  • Sanitized oversight. PEEK sees metadata, counts and evidence references — never credential values, prompts or protected agency records — unless an approved, time-boxed support window is active.

Your first session

  1. 1

    Sign in

    Go to /peek/signin and sign in with a PEEK workforce identity and phishing-resistant MFA. See Signing in.

  2. 2

    Check your capabilities

    Open the operator menu (avatar, top right) to see your roles. Each screen shows your capabilities as green ✓ / grey ✕ badges. See Operator roles.

  3. 3

    Pick a customer

    Use the Customer Directory or the tenant selector in the header to set an explicit tenant and environment context.

  4. 4

    Work a group

    Choose a screen from the sidebar. Use Contract on any screen to see its fields, flow, validation and audit event.

Synthetic fixtures only — This build runs on synthetic fixtures: no live network connections or real credentials. DHS/CBP labels (such as tenant CBP demonstration) are illustrative and are not proof of an actual customer or authorization.