This contents list belongs to the guide to permission-aware agents and the second approver. It tells an owner what their IT and security team would be asked to put together once a licensing discussion with SourceX starts, so the effort is visible before anyone commits.
The ten documents at a glance
| Order | Document | What it shows | Prepared by |
|---|---|---|---|
| 1 | Cover sheet | Identity, ticketing and ERP systems, years covered, rough monthly volumes, owner | IT director |
| 2 | Task specification | The approval-gated job in two or three sentences | Head of security with the service desk manager |
| 3 | Policy and role settings history | Which approval rules applied on which dates | Identity administrator |
| 4 | Request field map | What a request records: reason, ticket ID, requester | Service desk manager |
| 5 | Approval field map | Approver role, time, and evidence the approver differed from the requester | Identity administrator |
| 6 | Action field map | What the audit log records about the change itself | Identity administrator or security analyst |
| 7 | Outcome link description | How confirmation or reversal ties back to the change | Service desk manager |
| 8 | Volume and retention counts | Gated changes per month, months kept in the tool and in any archive | Security analyst |
| 9 | Acceptance check | The fixed test a change must pass | Head of security, refined with SourceX |
| 10 | Rights and sensitivity notes | Employee identifiers, provider contracts, security limits | General counsel |
Documents 1 to 3: scope, task and rules
1. Cover sheet. One page naming the systems involved (for example Microsoft Entra for admin roles, a service desk tool for tickets, an ERP for payment releases), when each was adopted, which change types need a second approver, rough monthly counts and the executive who owns the records.
2. Task specification. Illustrative wording: "Given a request ticket, the approval policy in force and the current role settings, carry out the requested account change only after approval from someone other than the requester, within the allowed activation window, and confirm the outcome with the user." It defines the job, not the records.
3. Policy and role settings history. Every version of the rules that governed approvals, with effective dates: whether approval was required, how many approvers, whether a justification and ticket number were mandatory, and the maximum activation length. Microsoft's documentation shows why each matters. In Entra Privileged Identity Management, role settings can require justification and ticket information, approval can be required, and the activation maximum duration can be set from one to 24 hours. A change judged against the wrong version of those settings is scored wrongly.
Documents 4 to 7: the field maps
These four documents describe fields, never contents. Each answers: which system, which field, since when, and whether it was mandatory.
4. Request field map. Where the reason for the change is captured, whether a ticket or change ID is required, and how the requester's identity was verified (and whether that check is noted).
5. Approval field map. Approver identity and role, timestamp, and whether self-approval is blocked by the system. Entra's documentation says approvers can't approve their own activation requests and that delegated approvers have 24 hours before the user must request again. If blocked or expired attempts are recorded, say where.
6. Action field map. What the audit log captures about the change: actor, time, target account, the setting changed. Note any shared admin accounts, because a change under a shared login has no individual actor.
7. Outcome link description. How the result is recorded: user confirmation in the ticket, a follow-up ticket, or a reversal entry, and whether the reversal points to the original change.
Documents 8 to 10: volume, test and limits
8. Volume and retention counts. Approval-gated changes per month, months retained in each tool, months held in any archive, and the date archiving began. Entra keeps audit logs seven days on the Free tier and 30 days on P1 and P2; data not archived before it expires cannot be recovered. The archive start date usually decides how many months a reviewer can assess.
9. Acceptance check. Fixed in advance. An Illustrative version passes a change only if all four hold:
- ☐The approver differs from the requester.
- ☐The action happened after approval and before the activation expired.
- ☐The ticket ID on the activation matches a real ticket describing the same change.
- ☐The outcome is recorded, and any reversal is linked to the original change.
The third box is the hardest. PIM documents ticket information as informational and not checked against a ticketing system, so a typed number can be wrong. The evidence gaps analysis covers what happens when it is.
10. Rights and sensitivity notes. Categories only: employee names and IDs in approvals, security configuration that should not leave the company, and managed service provider contracts that may govern logs. Whether the company may license the records at all is a separate test from authority inside a task; see de-identification versus permission to license.
An Illustrative volume sheet (document 8)
Illustrative and fictional. A 450-person insurance brokerage fills in document 8:
| Change type | Per month | Months in tool | Archived since | Self-approval blocked |
|---|---|---|---|---|
| Admin role activation | About 110 | 1 | March 2022 | Yes, by the identity tool |
| User sign-in method reset | About 60 | 1 | March 2022 | Yes, by the identity tool |
| Payment release over limit | About 35 | 84 | Kept in ERP | Yes, by ERP workflow |
| Vendor bank detail change | About 12 | 84 | Kept in ERP | Policy only |
Nothing here is a log, a ticket or a person's name, and nothing needs redaction. The last row shows a borderline case worth flagging honestly: separation that relies on policy rather than the system.
What the packet does not settle
The packet sizes and describes approval records. It does not decide whether they qualify or are wanted. The company must have 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.
Still unknown: how many changes pass the acceptance check on sampling, the rights review result, de-identification effort, buyer interest and any offer. For why approval trails matter to AI developers, see why AI agents need work data and agent trajectory data. Owners exploring this for their own business should read whether a business owner can refer their own company before assuming a reward applies. To check fit before any packet work, use the qualification scorecard. Other 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 the IT director can picture the team filling in these ten documents from what it already knows, register as a partner, check who qualifies, and read the program terms before making the introduction.