Recommended policy settings
Screen 3.3 — publish persona-based recommended settings with rationale for agency review.
PEEK Platform Administrator
/peek/customers/tenant-a/3-3 Live walkthrough · Recommended policy settings
Recommendations are product defaults with a rationale and applicability statement. Publishing makes them visible to the agency as approval-ready suggestions, optionally with permitted adjustments. They are never binding and never an official legal requirement.
3.3 · Recommended Policy Settings
Offer product defaults for agency review. Open it at /peek/customers/tenant-a/3-3 (any tenant ID you can access works in place of tenant-a). The primary action is Publish recommendation, which requires policy.recommend.
How 3.3 works
1. Create persona-based recommended settings and a preview of effects
2. Release for agency review
Screen 3.3 contract
- Fields shown
- Recommended value, reason, applicability, adopting authority
- Primary action
- Publish recommendation
- Required capability
policy.recommend- Validation
- Recommendations need rationale and applicability but do not become binding rules on publication.
- Successful outcome
- Agency sees an approval-ready recommendation with optional permitted adjustments.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.3.3.action(acceptance testAT-UI-3.3)- Requirements
- R02, R06, R07, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-3.3
Boundary — A recommendation is not an agency authorization or official legal requirement.
Rejected even if the browser allows it — Click an agency Adopt control in the PEEK preview; no live agency mutation may occur.