PKPEEK Docs
Docs/Experience & Studio

Experience overview, personas and navigation

Screens 7.1, 7.2 and 7.3 — Core experience and Studio entitlement, persona layout recommendations and module visibility rules.

PEEK Platform Administrator

/peek/customers/tenant-a/7-1
Live walkthrough · Experience overview, personas and navigation
/peek/customers/tenant-a/7-1
/peek/customers/tenant-a/7-2
/peek/customers/tenant-a/7-3

Standard recommended pages and basic branding are part of Core; Studio adds advanced composition. Removing Studio never removes the standard pages of the base human workflow.

Navigation stateMeaning
PurchasedCustomer holds the entitlement (1.4).
EnabledThe agency turned it on in its module settings.
AuthorizedThe user’s grants allow it.
AvailableIt is running (no outage or suspension).
Note — A module appears only when all four are true; otherwise navigation shows a distinct, safe reason and any authorized manual or external-work alternative. Hidden routes are denied by the backend too — guessing a URL does not work.

7.1 · Experience & Studio Overview

Review experience capability and Studio entitlement. Open it at /peek/customers/tenant-a/7-1 (any tenant ID you can access works in place of tenant-a). The primary action is Open experience governance, which requires experience_governance.read.

How 7.1 works

  1. 1. Show Core experience, Studio entitlement, current templates and agency adoption state

Screen 7.1 contract

Fields shown
Core experience, Studio license, active template, release status
Primary action
Open experience governance
Required capability
experience_governance.read
Validation
Standard pages and basic branding cannot require Studio. Release state is distinct from agency adoption.
Successful outcome
Open experience governance and synthetic preview for the actual module combination.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.7.1.action (acceptance test AT-UI-7.1)
Requirements
R02, R06, R19, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-7.1
Boundary — Standard recommended experience and basic branding remain in Core.
Rejected even if the browser allows it — Remove Studio entitlement and verify that the base human workflow still has standard pages.

7.2 · Persona Experience Recommendations

Recommend page layouts by persona. Open it at /peek/customers/tenant-a/7-2 (any tenant ID you can access works in place of tenant-a). The primary action is Release experience template, which requires experience_template.publish.

How 7.2 works

  1. 1. Recommend persona layout and approved components with preview and rationale

Screen 7.2 contract

Fields shown
Persona, template, allowed components, data prerequisites
Primary action
Release experience template
Required capability
experience_template.publish
Validation
Recommended visibility grants no data or action permission. Required agency review is shown separately.
Successful outcome
Release recommendation without changing the agency's published experience.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.7.2.action (acceptance test AT-UI-7.2)
Requirements
R02, R06, R19, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-7.2
Boundary — Recommended visibility never grants record access.
Rejected even if the browser allows it — Display an approval label without the required independent agency decision; reject the verified status.

7.3 · Navigation & Module Visibility Rules

Explain when modules appear in agency navigation. Open it at /peek/customers/tenant-a/7-3 (any tenant ID you can access works in place of tenant-a). The primary action is Preview navigation rules, which requires navigation_policy.publish or preview.use.

How 7.3 works

  1. 1. Preview navigation for entitlement, enablement, persona grants and runtime availability combinations

Screen 7.3 contract

Fields shown
Entitlement, enablement, authorization, availability, empty states
Primary action
Preview navigation rules
Required capability
navigation_policy.publish or preview.use
Validation
Backend denies hidden routes; absent/disabled modules do not create pending sync. Explain only safe states.
Successful outcome
Navigation offers authorized manual/external-work alternatives and distinct restriction reasons.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.7.3.action (acceptance test AT-UI-7.3)
Requirements
R02, R06, R19, R28, R33, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, SYS12, UI-7.3
Boundary — Map navigation to purchased, enabled, authorized and available states. Missing peer modules show external-work paths without phantom sync queues.
Rejected even if the browser allows it — Guess the URL for a hidden or unpurchased module; backend rejects access.

Related guides

Branding, Studio components and publishing roles

Screens 7.4, 7.5 and 7.6 — branding and layout bounds, the Studio component catalog, and designer vs publisher authority.

Persona templates

Screen 2.2 — release recommended business personas with suggested functions, views and required data scopes.

Experience preview, release and rollback

Screens 7.7 and 7.8 — preview the agency experience with synthetic identities, then release or roll back platform components.