Each stage has a distinct responsibility: context informs policy, authority defines the boundary, the platform enforces, and evidence supports accountability.
Delegation lifecycle
Authority should end by design.
Scope, owner and duration travel with the delegation; authority ends deliberately rather than becoming standing access.Delegance uses the control surface each target actually exposes; the diagram does not imply a catalogue of ready-made connectors.
01
From authority to action
Identity establishes the person. Roles and attributes add context. Policy evaluates the request. Delegated authority records who approved what, for which scope and period. The target platform enforces the resulting action.
02
A governed lifecycle
Request → evaluate → approve → activate → use → monitor → review → expire or revoke. Every stage has an owner, a control point and evidence suitable for assurance.
03
Fit existing platforms
Delegance can be integrated with Microsoft Entra, SaaS services, enterprise and custom applications, APIs, directories and privileged platforms. The implementation pattern depends on the controls each target exposes; no ready-made connector is assumed.
04
Decision boundaries
Delegance does not replace authentication or the target platform. It coordinates authority, policy and governance so those platforms receive narrower, better-evidenced access decisions.
Apply the model
Make authority explicit.
Start with the business action, accountable owner, current entitlement and platform control surface.