A multiple-role model lets one user or organisation membership receive permissions from more than one role at the same time. This reduces the need for oversized combined roles and can make access easier to manage across departments or projects. The control still needs governance, because overlapping roles can quickly recreate permission sprawl.
How Multiple Roles Work
Multiple roles let one identity accumulate permissions from more than one role assignment at the same time. In practice, this is a common way to separate duties by team, project, function, or environment without creating a single oversized composite role that becomes hard to understand, test, or retire.
The model is useful because access often does not fit neatly into one job description. A person may need one role for day-to-day work and another for a temporary project, while an organisation membership may need access from both a department role and a system-specific role. The design only stays manageable when the underlying role catalogue is disciplined.
Why Multiple Roles Are Used
Multiple roles reduce the pressure to keep inventing “catch-all” roles whenever a new access need appears. That matters because large combined roles quickly become brittle: they accumulate exceptions, obscure who should have what, and make access reviews less meaningful. A smaller set of purpose-built roles is usually easier to govern than one dominant role with many special cases.
The approach also supports cleaner delegation. Teams can grant access by attaching the most relevant role for a business function, then add a second role only where a separate responsibility truly exists. This helps preserve the logic of role-based access control while keeping permissions closer to the actual work being performed.
Governance and Design Trade-offs
Multiple roles are not a substitute for good role engineering. Overlap between roles can recreate the same sprawl the model was meant to avoid, especially when two roles both grant similar permissions from different angles. The practical question is not simply whether users can hold several roles, but whether the role set remains intelligible, auditable, and stable over time.
Designers also need to watch for hidden privilege stacking. A role that looks harmless on its own may become risky when combined with another role that adds complementary access. That makes role combination rules, separation of duties, and periodic review more important than in a single-role design.
Operational Implications for Access Management
In access operations, multiple roles change how you review entitlement drift and explain effective permissions. Reviewers need to see not just which roles exist, but how their permissions intersect for the same user or group membership. Otherwise, access recertification can approve each role independently while missing the combined effect.
It also means removals must be handled carefully. Dropping one role may still leave the user with overlapping access from another role, so access cleanup should be validated at the effective-permission level rather than at the role label level alone. That is especially important when roles are inherited from different organisational structures or lifecycle events.
Risk and Threat Considerations
Multiple roles can create permission sprawl, excessive privilege, and accidental access overlap if the catalogue is not tightly governed. The risk is not the model itself, but the way overlapping entitlements can hide cumulative access that no single role review would flag.
Failure mechanism: An organisation treats each role as safe in isolation, while the combined permission set gives a user broader access than intended. Over time, this can enable unauthorised data exposure, segregation-of-duties failure, or easier lateral movement after compromise.
Impact: Effective privileges become harder to reason about, access reviews lose precision, and attackers or insiders may exploit the overlap to reach actions that should never have been available together.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Multiple roles affect how accounts and entitlements are assigned and reviewed. |
| AC-6 — Least Privilege | Role overlap can undermine least privilege by stacking permissions beyond need. | |
| AC-5 — Separation of Duties | Overlapping roles can defeat separation when combined permissions enable disallowed actions. | |
| Recommendation — Review combined role assignments to keep account privileges aligned to current duties. Limit role combinations so effective access stays at the minimum required. Design role combinations to preserve separation of duties across sensitive actions. | ||
Practitioner Guidance
Governance implication: Use multiple roles only when each role has a distinct business purpose and a clear ownership model. If two roles routinely travel together, reconsider whether they should be split differently, merged, or governed as a tightly controlled bundle.
What to watch for: Review the effective permission set, not just the assigned roles, whenever a user accumulates more than one role. That is where hidden overlap, excessive privilege, and brittle role design usually show up first.
Related resources from NHI Mgmt Group
- How should security teams govern MongoDB users with roles across multiple databases?
- How should universities govern identity when people hold multiple academic roles?
- How should teams govern Oracle access when roles span multiple enterprise systems?
- How should security teams govern roles when entitlements span multiple systems?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org