One day your system has a handful of roles. The next, it’s hundreds. What starts as a clean role-based access control model crests into a wave of confusion—nested permissions, duplicates, unexpected overlaps, orphaned roles no one remembers creating. This creeping complexity is the Discovery Large-Scale Role Explosion problem, and it hits faster than most teams expect.
Role explosion doesn’t announce itself. It happens invisibly until someone asks a simple question: “Who actually has access to production?” You pull the data, thinking it’s a five‑minute task. Hours later you’re staring at a spreadsheet with more rows than you thought possible. The names don’t match your mental model. The permissions don’t match your policy. And the system—the one you designed—doesn’t match reality anymore.
This isn’t just an audit headache. Large‑scale role discovery directly impacts security posture, operational stability, and development velocity. The larger the system, the deeper the drift. Microservices multiply it. Mergers and integrations amplify it. Even minor changes, applied over years, compound into a dense thicket of roles no one can fully map without effort and tooling.