This page is part of the guide to permission-aware agents and the second approver. That guide shows a complete trail for one account change. This page does the opposite job: it sets the evidence a review would expect against what companies usually keep, so an introducer can predict the shortfall and describe it without overselling.
The evidence a review expects
A reviewer judging whether an action had the right authority needs six kinds of evidence for each change. Missing any one weakens the case; missing the approval itself usually ends it.
| Evidence | What it proves | Typical system |
|---|---|---|
| Request record | Why the change was needed, and who asked | Service desk or change ticket |
| Approval record | A different person granted authority, and when | Identity tool, ERP approval workflow |
| Approver list history | Who was allowed to approve on that date | Identity tool configuration, access reviews |
| Role or policy settings history | Which rules applied: approval required, maximum duration, justification | Identity tool configuration |
| Action log | What was done with the authority, by whom, when | Audit log |
| Outcome record | Whether the change worked or was reversed | Ticket closure, follow-up ticket |
What companies usually have and what is usually missing
The pattern below is a typical shape, not a measurement. It is what a reviewer should expect to find at a mid-sized company that never set out to keep approval evidence.
| Evidence | Usually present | Usually missing | Why it goes missing |
|---|---|---|---|
| Request record | Tickets for years | How the requester's identity was verified | Verification is done on a call and not noted |
| Approval record | The last few weeks | Everything older than the tool's retention window | Audit logs expire unless archived |
| Approver list history | The current list | Who could approve on past dates | Lists are edited in place |
| Role or policy settings history | Current settings | Earlier settings and the date they changed | Configuration changes are not versioned |
| Action log | Recent entries; shared-account entries | The person behind a shared admin login | Shared accounts hide the actor |
| Outcome record | Ticket closed | Whether the user's problem was solved, or a reversal linked to the change | Closure codes say "resolved" and nothing else |
The approval row is the one to ask about first. Microsoft's documentation for Entra says audit logs are kept seven days on the Free tier and 30 days on P1 and P2, that they can be kept longer by routing them to Azure storage through Azure Monitor, and that expired data that was not archived cannot be recovered. A company that never set up archiving may have five years of tickets and one month of approvals.
How the gaps break a trail
Each gap breaks the authority story at a different point:
- Missing context. The activation carries a reason and a ticket number, but the ticket was closed with no note of what was requested or how the requester was checked. A reviewer sees authority granted for an unknown purpose.
- Loose linkage. Microsoft's PIM documentation says ticket information entered at activation is informational and not checked against any ticketing system. A mistyped number links an approval to the wrong request, or to nothing.
- Unclear permissions. Approver lists changed and nobody kept the history, so it is impossible to say who was allowed to approve on a given day.
- Moved versions. Settings such as whether approval was required or the maximum activation length were edited later, and the earlier values were not recorded. A change can look out of policy when it was within the rules of its day.
- Shared accounts. A change made under a shared admin login has no individual actor, which defeats the purpose of a second approver.
- Unrecorded outcome. The change was made, but nothing shows whether it solved the problem or was rolled back.
The blocked attempts matter too. Entra does not let approvers approve their own activation requests. Where a system keeps a record of a blocked self-approval, that record is the clearest evidence that the boundary held; ask whether such attempts are logged at all, because many summary reports never show them.
Describing a gap honestly in an introduction
An introduction that names the likely gaps builds trust and saves a review cycle. Keep it to three parts: what the contact confirmed, what is probably missing, and who can confirm the rest. Three Illustrative examples:
| Situation | Honest wording for the introduction |
|---|---|
| No archiving | "The IT director confirms about 100 approval-gated changes a month and tickets back to 2019. Audit logs were not archived, so approvals older than 30 days are likely gone. The CIO can confirm." |
| Hand-typed links | "Activations require a change number, typed by hand and not validated. Most should link; some will not. The service desk manager can estimate how often numbers are wrong." |
| Partial outsourcing | "Approvals run in the company's own identity tool, but an MSP performs many changes under its own accounts. Who owns those action logs depends on the MSP contract." |
Avoid three things: estimating what share of records survives, calling a gap "minor" before anyone has looked, and promising that a review will find a workaround. The reviewer decides how much is usable.
Where to look before calling a gap final
Some gaps close once the right person is asked. Audit logs may have been streamed to a security monitoring system even if nobody in IT remembers. Approver lists may survive in quarterly access review files. Outcome notes may sit in the ticket system's resolution field rather than the closure code. The historical ticket archive guide covers the service desk side of the same records, and the ERP replacement handoff checklist helps when approvals live in finance software due for retirement.
The company still needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Authority inside a task is a different test from the right to license; see de-identification versus permission to license. To score fit first, use the permission-aware agents qualification scorecard; the review packet contents list shows what the company would assemble later. More record families are in data types.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If you can describe a client's approval records and their gaps in three honest sentences, register as a partner, check who qualifies, and read the program terms before you introduce the CIO or COO.