Combine baseline, context and accountable authority.
Roles simplify repeatable access; attributes constrain context; delegation records accountable authority, scope and duration.
01
Role-Based Access Control
RBAC answers who should receive access because of a recognised role—such as HR administrator, finance manager, service desk operator, application administrator or contractor coordinator. It is understandable and scalable, but broad roles can accumulate privilege and rarely express every contextual boundary.
02
Attribute-Based Access Control
ABAC evaluates characteristics such as department, organisation, location, assurance level, employment status, classification, device state, business unit, project, time and current delegation status. It can express precise conditions, but only when attribute quality, policy ownership and explainability are governed.
03
Delegated authority
Delegation answers a different question: who authorised this person to act, for what purpose, against which resource, and until when? It adds accountable authority to role and attribute context.
04
Use them together
A role can establish a baseline, attributes can constrain the context, and delegation can authorise a bounded exception or business action. The resulting decision should remain explainable to the person, owner and auditor.
Apply the model
Make authority explicit.
Start with the business action, accountable owner, current entitlement and platform control surface.