Story: Review the tenant administrator's home screen
Table of Contents
This page documents a story in Sprint 27. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
A tenant administrator lands on a dashboard of panels that say what needs them, with the active and upcoming modules on their own tabs.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 27 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-10 |
3. Acceptance
- The tenant home has the tabs Dashboard, Active modules and Upcoming modules, held in the address.
- The Dashboard has a People, a Sign-ins, an Access requests and a Parties panel, with the same marks, tiles and footers as the system home, and the Access requests panel only for a person who may assign roles.
- One status next to the title counts the panels that need the person.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Scaffold story: Review the tenant administrator's home screen | DONE | 2026-10-10 | 2026-10-10 | Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR. |
| Rework the tenant home into three tabs with a dashboard | DONE | 2026-10-10 | Initial task for: Review the tenant administrator's home screen |
5. Decisions
6. Out of scope
- Plots on the tenant dashboard. The tenant side keeps no history on the server.
- A permission only the operator holds. Tenants and the installation cards stay drawn by session mode until the server has one.
- Translated strings for the Rescue access screen.
7. Result
The tenant administrator's home has the system home's shape: a header with one status, three tabs, and a dashboard of panels that say what needs the person in the same words. The dashboard refreshes every 15 seconds and colours its figures.
Every person gets the same menu. An area is drawn when the person holds a read one of its screens needs, and a card is drawn when the person holds the read of its screen. The knowledge page menu_structure defines the rule, and the UX structure note ux_hub lists the UX pages. Operations is drawn for everyone, with Sign-ins, Roles and Rescue access under their areas and a breadcrumb on each screen.