How it works

Integration.

Delegance governs the decision. Your platforms keep enforcing it. That split is deliberate, and it is the first thing to get straight.

In development. Connector and enforcement capability is confirmed per environment during discovery rather than assumed.

Who does what

Delegance provides

The authority decision

  • The model: who may act, for whom, on what, until when
  • Policy evaluation against roles, attributes and constraints
  • Approval routing to an accountable owner
  • Expiry, review and revocation
  • The record that explains why an entitlement exists
You provide

The environment and the enforcement

  • The platforms that hold the entitlements
  • The people with standing to authorise
  • Your own policy on what may be delegated
  • The systems of record the authority relates to
  • What happens operationally when a delegation ends

Worth designing for early: Delegance does not become a new enforcement point in front of your systems. The target platform stays the place where access is granted and denied, which means your existing controls and their audit trails keep working.

Where it connects

The control surfaces organisations most often need governed. What is achievable in a given environment is confirmed during discovery.

Identity platforms

Microsoft Entra and comparable directories, where group membership, role assignment and eligibility already drive access.

Business applications

SaaS products and internal applications with their own permission models, where delegated approval authority usually lives.

APIs and services

Service-to-service authority, where a system acts on behalf of a person or another organisation.

Privileged access

Elevated administrative authority, which is where time-bounded delegation matters most and is most often informal.

Tell us what you run

Early conversations are most useful when they start from your actual platforms and the authority you cannot currently explain.