What a system permits
A technical capability: this account can approve this kind of transaction. It is visible in the platform and usually well controlled.
What it does not carry is why the person has it, who decided, or when it should stop.
What it does
Most organisations delegate authority constantly and record almost none of it. Delegance turns that into something written down, approved, bounded and time-limited.
The difference sounds academic until an auditor asks why someone could do something.
A technical capability: this account can approve this kind of transaction. It is visible in the platform and usually well controlled.
What it does not carry is why the person has it, who decided, or when it should stop.
The business decision behind the access: this person may act for that person, for this purpose, within these limits, until this date.
Today that usually lives in an email, a conversation, or nobody's head at all.
If a delegation cannot answer all six, it is an assumption rather than an authority.
Who could approve this last March, and why? With authority recorded alongside access, that is a lookup rather than an investigation.
Cover arrangements, secondments and acting roles expire on the date they were meant to, without depending on anyone's memory.
An access review that shows why each entitlement exists and who owns it is a different exercise from a list of accounts.
Every organisation grants exceptions. Recording them as exceptions, with an owner and an end date, is what keeps them from becoming permanent.
If authority in your organisation is granted by email and ends when somebody notices, we would like to hear how it works today.