It starts with a few more teams. Then more products. Then compliance. Then customers ask for custom access rules. Soon your once-manageable set of 12 roles turns into 300. Then 1,000. Permissions multiply. Roles overlap. Orphaned configurations appear like weeds. Nobody knows which role does what, or if removing it will break a critical workflow. This is the large-scale role explosion. And your licensing model controls how quickly it turns from a challenge into a crisis.
The licensing model defines more than cost. It defines the shape of your system. Wrong licensing can punish flexibility and reward bloat. If the model charges per role, people will overload single roles to avoid fees, creating risky over-permissions. If it charges per user, teams may mint countless roles to work around licensing limits. Over time, these incentives cause exponential complexity.
Role explosion increases the attack surface, slows development, and requires constant audits. Engineering loses confidence in security. Compliance teams lose sleep. Managers spend time negotiating between IT, finance, and product instead of shipping features. Many systems break during audits, migrations, or mergers because no one can reconstruct how the access model evolved.