Someone needs to act for someone else
A finance manager at Harbour Community Trust is away for three weeks. Approvals still have to happen.
The authority is written down, not assumed
Who may act, for which approvals, up to what value, from which date to which date, and who authorised it.
It is approved by someone accountable
The delegation is granted by a person with the standing to grant it, and that decision is part of the record.
Access follows the authority
The entitlement appears in the platform that enforces it, carrying the same scope and the same end date.
It ends without anyone remembering
At the expiry date the authority lapses and the access goes with it. Nobody has to notice, which is the point.
In development
Govern who may act, for what, and until when.
Access says a system will let someone do something. Authority explains why they may, who approved it, what it covers and when it ends. Delegance makes that explicit.
We are working with early design partners on first deployments.
Not authentication
Who someone is stays with your identity provider. Delegance starts after that question is answered.
Not enforcement
Your platforms remain the enforcement point. Delegance governs the business decision behind the entitlement.
The bit in between
Why this person may act, for what, on whose authority, and the date it stops. Usually the part nobody records.
Where would you like to start?
Three ways into the same idea, depending on what you are trying to work out.
Understand delegated authority
What authority actually is, how it differs from access, and the six things every delegation should make explicit.
See the modelSee where it applies
Cover, temporary roles, acting on behalf of an organisation, and other authority that needs a boundary and an end date.
See the examplesWork out where it fits
How Delegance sits alongside your access platforms, and how it differs from DiligenceID and Vigilance.
See the boundariesExample: cover for a colleague
Temporary authority that ends on its own.
One delegation followed the whole way, using a fictional organisation.
Questions people ask early
Does this replace our identity platform?
No. Delegance works with the platforms you already run and leaves them as the enforcement point. How that works.
How is this different from a role?
A role describes an ongoing responsibility shared by many people. A delegation is a specific, accountable exception with an owner and an end date.
What stops authority accumulating?
Expiry by design, plus review at a set interval. Temporary authority that never ends is the problem this addresses.
Can we start now?
Delegance is in development. We are working with early design partners, which is the most useful stage to get involved if the problem is yours. Talk to us.
Where it fits
One of three, each with its own job.
Delegance governs the authority to act — who may do something on whose behalf, and until when.
DiligenceID carries provable facts about a person, such as a qualification or a current registration. Vigilance watches what then happens and carries real risk through to a response.
They connect where an organisation wants them to. None of them needs the others to be useful.
Is this your problem?
If temporary authority in your organisation is granted by email and ends when someone remembers, we would like to talk to you.