Permissions that quietly block feature discovery

We regularly find “low adoption” that is really default deny. A module ships, marketing announces it, and the majority of seats never receive the permission that exposes the navigation item.

Instrument permission grants alongside product events. Compare eligible users (those who could open the module) against exposed users (those whose UI actually shows it) against activated users. The gaps between those three cohorts are usually more actionable than another onboarding email.

UK regulated industries often tighten roles after security reviews. Revisit discovery after each access-control change; otherwise you will attribute a drop in adoption to product quality when the cause is a closed gate.