Left-rail nav — 20 pages projected
Shipping 5 today → 11 at end of Phase 1 → 20 at end of Phase 2.
Each entity cluster stays contiguous: parent entity page sits
at the top of its cluster, then its {X} -
drilldowns directly beneath.
By entity prefix
—
Top-level (no prefix)
8
U
Users drilldowns
3
C
Computers drilldowns
2
G
Groups drilldowns
2
M
Mailboxes drilldowns
2
L
Licenses drilldowns
1
E
Entra drilldowns
1
H
Hidden alert-rendering
2 shown
Persona coverage at 20 pages
Reality check. ClientA ran 12 visible pages
end-to-end. 20 is ambitious but each one has a named
persona and a specific question it answers — anything that
can't name a persona gets rejected. If 20 feels too many in
review, the usual trims are (a) fold
C - Stale Computers into Account Health's
computer-staleness tile, (b) drop
C - OS End-of-Life as a subpage under Licenses
(OS EOL drives license renewal), (c) kill the
Audit Pack top-level page and use Power BI
Subscriptions instead (BACKLOG 3.5 + 3.41).
Design assumptions
Entity parents stay top-level even when
their drilldowns exist (Users, Computers, Groups,
Mailboxes, Licenses, Entra Sign-Ins). Each entity gets its
own overview-of-that-entity page; drilldowns answer
narrower questions underneath. Account Health is the one
exception — it's a cross-entity flagship, promoted out of
the Users cluster to sit directly after Overview.
Hidden alert-rendering pages are shown at
the bottom of the rail during authoring. In view mode
(customer-facing), they disappear. Two are sketched; the
real count will be zero in v1 (HTML templates in YAML are
enough) and grow to maybe 3–6 in Release B/C if specific
alerts benefit from a visual-rich body.