Adjusts execution flow, prompts, or decisions based on the persona using the system.
Varies behaviour by who is using it — different detail, different tone, different available actions by role.
Systems serving genuinely different roles with different needs from the same underlying data.
As a substitute for authorisation. Adapting what is shown is a usability decision; restricting what is permitted is a security one, and conflating them is dangerous.
Persona adaptation must never be the mechanism enforcing access. Permission checks belong below the application, independent of any persona logic.
Persona used as a proxy for permission, so someone whose role is misdetected sees what they should not.
The same reconciliation shown as a working queue to a preparer, an approval decision to a controller, and a provenance trail to an auditor — with access enforced separately by role.
Two different absences share this shape. Foundational solutions get built whatever the domain, so no domain links them; the rest are solutions this domain genuinely does not reach for. v_ai_solutions_unlinked separates the two.