Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How should security teams design RBAC when users…
Governance, Ownership & Risk

How should security teams design RBAC when users need access across multiple functions or projects?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 5, 2026 Domain: Governance, Ownership & Risk

Use atomic roles that map to clear business functions, then assign more than one role when a user legitimately spans responsibilities. This keeps permissions understandable, avoids hybrid mega roles, and makes reviews easier. The key control is additive access, where each role contributes a known slice of privilege and the final entitlement set remains transparent.

How to structure RBAC when one person works across multiple functions

Design the model around work that is naturally separable, not around the individual user. A role should represent one business function, one project function, or one operating context, and users who span more than one context should receive multiple atomic roles. That keeps access additive, reviewable, and easier to remove without disturbing unrelated duties.

The practical advantage is that permission meaning stays intact. If a user needs finance plus project delivery access, or support plus application administration, each role should still be understandable on its own. When a single role starts carrying mixed responsibilities, reviews become slower, entitlement drift is harder to spot, and revocation is more likely to remove too much or too little access.

A useful design test is whether another reviewer can explain why the role exists without needing the incumbent's job title. If the answer is no, the role is probably too broad. Good RBAC design keeps the mapping between role and responsibility obvious, so the final access set can be assembled from known pieces rather than from one oversized exception.

Why additive access is safer than hybrid mega roles

Additive access works best when each role contributes a defined slice of privilege and nothing more. That means the user's effective access can be reasoned about as the sum of independent parts, which improves transparency for approvers, auditors, and application owners. It also lets teams compare actual business need against what the user receives.

Hybrid mega roles tend to hide privilege growth. They often begin as a convenience fix for one user who spans functions, then become reused for others with similar but not identical needs. Over time, that creates role sprawl, weakens least privilege, and makes it difficult to tell whether a permission came from the base function or from a special-case bundle.

For teams that want a reference model for role design, Role Mining and Role Design Guide is useful because it frames how to design manageable roles and avoid role explosion. The same principle is reinforced in IAM and IGA Basics, which treats RBAC as part of a broader access governance model rather than a naming exercise.

How to keep RBAC workable across projects, functions, and reviews

Start with a role catalogue that distinguishes business roles from project or technical roles. Business roles should describe stable responsibilities, while project roles should be time-bound and removable when the work ends. That separation prevents temporary project access from hardening into permanent entitlement.

Then define approval and review boundaries at the role level, not at the individual permission level. Reviewers should validate whether a user still needs each atomic role, and access recertification should make it easy to drop one role without reconsidering the whole access package. This is where additive RBAC is strongest: it lets you remove one slice of access while preserving the others.

If you need a broader authorisation reference for comparison, Authorisation Models Guide is helpful because it places RBAC alongside ABAC and ReBAC and clarifies when role-based design is the right fit. For teams doing periodic cleanup and review, Access Review Checklist supports the review discipline that keeps multi-role access from drifting.

Risk and Threat Considerations

Multi-function users are where RBAC mistakes become visible fastest. If a role bundles unrelated duties, excess privilege can spread quietly through reuse, and a compromise in one function can expose another function's access path. The biggest failure mode is not the existence of multiple roles, it is allowing one oversized role to become the easy answer for everyone who straddles teams or projects.

Failure mechanism: Hybrid roles collapse separable responsibilities into one entitlement object, which weakens review quality, obscures privilege origin, and makes revocation coarse-grained. Attackers and careless insiders benefit from that ambiguity because the access looks legitimate even when only part of it is needed.

Impact: Overbroad access increases blast radius, makes SoD conflicts harder to detect, and raises the chance that a single account can move across projects or functions with more authority than intended. It also makes audit evidence less trustworthy because reviewers cannot easily tell which permissions are truly justified.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8, NIST SP 800-53 Rev 5 and OWASP ASVS set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-5 — Account ManagementRBAC role assignment and review are core account-management controls.
Recommendation — Enforce role-based approvals and regularly review assigned access for unnecessary accumulation.
NIST SP 800-53 Rev 5AC-2 — Account ManagementRBAC depends on controlled provisioning, role assignment, and periodic review of accounts.
AC-6 — Least PrivilegeAtomic roles and additive access directly implement least privilege for users spanning functions.
Recommendation — Define account types, approve role assignments, and recertify access on a recurring schedule. Limit each role to the minimum permissions needed for its business function.
ISO/IEC 27001:2022A.5.15 — Access controlRBAC is an access-control design choice that must be governed consistently across functions and projects.
Recommendation — Apply a documented access-control policy that keeps roles narrow and reviewable.
OWASP ASVSV8 — AuthorizationRole design determines how application permissions are granted and combined for users with multiple duties.
Recommendation — Use distinct authorization rules and role definitions that avoid ambiguous privilege bundles.

Practitioner Guidance

What to prioritise: Design the role model around stable business functions first, then add project-specific roles only where the work is genuinely temporary or distinct. Keep each role narrow enough that its purpose is obvious in a review meeting.

What to verify: Confirm that no role is being used as a catch-all for unrelated duties, and check that every multi-role user can explain each assigned role in business terms. If the explanation depends on history or personal trust, the role model needs tightening.

Common mistake: Teams often try to solve cross-functional access by creating one broader role instead of multiple atomic roles. That is faster in the short term, but it usually creates more review debt and more cleanup later.

Practitioner takeaway: The best RBAC design is the one that makes extra access visible, intentional, and removable one slice at a time, without forcing the organisation to invent a custom mega role for every exception.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org