A large share of access tickets are structural questions in disguise: why can this user not reach the share, why did the license disappear, why does the new hire lack what teammates have. Support either sees the structure or escalates to someone who can.
The triage questions#
Most access tickets resolve to one of three lookups:
- Path: does this user reach the granting group through any chain, and where does the chain break?
- Peer delta: what memberships does the working teammate have that the ticket's user lacks?
- Recency: did something change for this user, group, or license in the last days?
Why these escalate today#
Each lookup needs transitive membership or change history, which means Graph queries or admin portal digging beyond a support role's access and tooling. The ticket waits in the escalation queue for an engineer to run what is, structurally, a thirty-second question.
VisualizerEngine
How VisualizerEngine serves support
The Viewer role, enforced server-side, gives support read-only sight of paths, peer comparisons via structural search, and the change-history panel for recency, with no ability to modify anything. Tickets that were escalations become lookups, and the escalations that remain arrive pre-diagnosed with the path attached.