Designing Role Lens UIs for SaaS integration

SaaS apps usually treat “role” like a hidden condition: the UI changes, but it rarely explains why. Buttons appear or disappear as you navigate, wording shifts by route, and secret-handling language can drift away from the intent you think you are expressing.

Role lens UIs separate meaning from activation. The role lens chooses which meaning is safe/expected for “who you are”, while the goal lens answers “I want to...” and filters what the UI should activate right now. The result is a single activated bundle that the whole UI subscribes to.

When every screen binds to the same activated bundle, you stop re-encoding intent for every route. Integration surfaces become predictable: labels, safe server actions, and workflow modules change together, and recovery language stays aligned with the meaning you selected.