Docs/People & authority

Persona templates

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

PEEK Platform Administrator · PEEK Technical Reviewer

Live walkthrough · Persona templates

Persona templates — /peek/customers/tenant-a/2-2 — /peek/customers/tenant-a/2-2

A persona template recommends purchased functions, views and the data scopes a business persona (for example *Market Research Analyst* or *Acquisition Planner*) typically needs. Recommended views use the fixed agency navigation IDs — My Day, My Work, Requirements, Acquisition Actions, Contracts & Orders, Market Research, Studio, Reference, Users & Access, Policies & Workflows, SI Governance, Automations, Connections, Access History and Module settings.

Heads up — A persona is not a role and not a data grant. Features the customer has not purchased appear as conditional suggestions with a reason. Adopting a persona never lets Sigma or a user see records without an actual record grant.

2.2 · Persona Templates & Delegation

Publish recommended business personas for agency adoption. Open it at /peek/customers/tenant-a/2-2 (any tenant ID you can access works in place of tenant-a). The primary action is Release persona template, which requires persona_catalog.publish.

How 2.2 works

1. Recommend purchased functions, recommended views and required data scopes per persona
2. Release the template

Screen 2.2 contract

Fields shown: Persona, capability suggestions, data-scope requirements, inheritance
Primary action: Release persona template
Required capability: persona_catalog.publish
Validation: A persona is not a role or data grant. Unpurchased features are conditional suggestions with a clear reason.
Successful outcome: Agency administrators see adoptable recommendations; existing user grants remain unchanged.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.2.2.action (acceptance test AT-UI-2.2)
Requirements: R02, R05, R06, R28, R34, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-2.2

Boundary — Persona suggestions follow the purchased module set. Agency grants and record permissions govern actual handoff and Sigma access.

Rejected even if the browser allows it — Adopt an analyst persona and query restricted evidence through Sigma without a record grant; deny the query.

Related guides

Administrative roles and delegation

Screen 2.1 — publish agency administrative role templates, delegation ceilings, combination rules and maximum durations.

Permitted uses, persona access and evidence

Screens 4.3, 4.4 and 4.9 — recommend SI by persona, constrain processing by data class and purpose, and trace use cases to agency approval evidence.

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.