Features / Authorization
Allow access to be described through more than one role assignment where the policy model requires it.
Explore the design intent, review practical decisions and validate exact behavior against your deployed configuration.
Why it matters
Users often hold responsibilities across projects, teams and resources. Flattening them into one overpowered role obscures the origin and intended scope of each permission.
Design intent
Keep role assignments distinct, define how multiple grants combine, and test both conflict and removal cases. Ensure that role selection does not bypass network or assurance requirements attached to the underlying access.
Worked scenario
An employee has a reviewer role for one resource and an operator role for another; the effective access is evaluated in the relevant resource context.
Boundary to verify
Confirm enforcement at the relevant server, API, resource or operational decision point. A hidden button or an informative dashboard is not, by itself, an authorization control.
Practical path
Use these stages as a review guide. Exact settings and enforcement points depend on the configured deployment and connected systems.
Identify the actor, target resource and operation that multi-role support is meant to govern.
Keep role assignments distinct, define how multiple grants combine, and test both conflict and removal cases. Ensure that role selection does not bypass network or assurance requirements attached to the underlying access.
An employee has a reviewer role for one resource and an operator role for another; the effective access is evaluated in the relevant resource context. Also test the path that should be denied, deferred or sent for review.
Check that the resulting state is understandable and that the decision can be investigated later. For audit-enabled operations, confirm the relevant actor and context are captured.
Before rollout
A capability is easier to operate when ownership, failure behavior and verification are defined upfront.
This page describes a design approach based on WebFrolic’s documented product model. Verify feature availability and exact behavior in your environment before relying on it for a control requirement.
Related capabilities
Follow the related areas to understand how this capability fits within identity, access, lifecycle and operations.
Evaluate with your scenario
Share the identities, resource boundary and decision you want to test. The walkthrough can focus on the relevant behavior rather than a generic feature tour.
