Organization changes and impact
Screen 1.7 — review renamed, moved or merged offices and stage effective-dated mapping changes without broadening access.
PEEK Platform Administrator
/peek/customers/tenant-a/1-7When agencies or offices are renamed or reorganized, 1.7 compares the old and new mappings, enumerates the affected tenant grants and pending work, and stages an effective-dated change. The new mapping version preserves prior provenance and audit.
1.7 · Organization Changes & Impact
Review renamed or reorganized agencies before applying mappings. Open it at /peek/customers/tenant-a/1-7 (any tenant ID you can access works in place of tenant-a). The primary action is Stage reviewed mapping change, which requires organization.change.
How 1.7 works
1. Compare old and new mappings, enumerate affected tenant grants and work
2. Stage an effective-dated change
Screen 1.7 contract
- Fields shown
- Old and new mapping, affected scopes, pending work, effective date
- Primary action
- Stage reviewed mapping change
- Required capability
organization.change- Validation
- Require explicit remapping and authority for affected scopes; never infer membership from a renamed office.
- Successful outcome
- New mapping version preserves prior provenance and audit with a reviewable impact report.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.1.7.action(acceptance testAT-UI-1.7)- Requirements
- R01, R02, R06, R28, R30, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.7
Related guides
Organization scope and offices
Screens 1.1, 1.1A and 1.2 — pick the department then agencies from source reference data, handle source outages, and review office mappings.
Customer scope and administrators
Screens 1.3 and 1.3A — define the agency customer boundary, designate initial administrators, and configure department-wide purchases.