# Permission-aware agents, explained | SourceX

Canonical: https://refer.sourcex.si/guides/concept-permission-aware-agents
Last updated: 2026-11-04

Permission-aware agents take an action only when the authority for it is in place, and stop or ask when it is not. In an ordinary business workflow, that is an account change that needs a second approver: the technician requests elevated access with a reason, cannot approve his own request, waits for a manager, and acts inside a one-hour window. For a referral, what matters is whether the company kept the request, the approval, the action and the outcome, and who can authorize a licensing discussion.

## What does permission-aware agents mean in an ordinary business workflow?

It means authority is checked before the action, not after. The business version is familiar: some changes need a second person, and nobody is allowed to approve their own request.

The behavior matters for AI agents because an agent that can act in business software can also act without authority. Our explainer on [why AI agents fail](/questions/why-ai-agents-fail) covers failures that come from doing the right thing in the wrong way. Records of real approval workflows show the shape of correct behavior: what was asked, who could say yes, what happened when the wrong person tried, and what was done once approval arrived.

Identity administration is a clear case because the rules are written into the software. In Microsoft Entra Privileged Identity Management (PIM), Microsoft's documentation says approvers can't approve their own role activation requests, delegated approvers have 24 hours to approve before the user must submit a new request, and a request is settled by the first approver who approves or denies. Role settings can require a justification and a ticket number at activation, and the activation maximum duration can be set from one to 24 hours.

One caution belongs here, not in a footnote. This page is about authority inside a task. It is not about the company's right to license its records, which is a different test covered in [de-identification versus permission to license](/guides/how-to-distinguish-de-identification-from-permission-to-license).

## An account change that needs a second approver (Illustrative)

This case is fictional. A 420-person freight brokerage manages staff accounts in Microsoft Entra. Admin roles are eligible, not permanent: a technician activates one when needed, with approval required and a one-hour activation limit.

The finance director replaces her phone and can no longer complete multi-factor sign-in. Changing her sign-in methods needs an admin role the service desk technician holds only as eligible.

| Time | Step | Authority check | Record left |
|---|---|---|---|
| 09:05 | Finance director's request logged after identity check by video call | Service desk policy requires a verified requester | Ticket IT-5521 with the check noted |
| 09:20 | Technician requests activation of the admin role | Justification and ticket number required by role settings | Activation request with reason and "IT-5521" |
| 09:22 | Technician, who is also an approver for colleagues, tries to approve his own request | Self-approval not allowed | Request stays pending |
| 09:41 | IT manager approves | Different person, within the 24-hour window | Approval with approver identity and time |
| 09:44 | Technician updates the director's sign-in methods | Role active, expires at 10:41 | Audit entry for the account change |
| 09:58 | Director signs in on the new phone; ticket closed | Outcome confirmed by the user | Sign-in success; ticket resolution note |

Two details make this a useful example rather than a tidy story. First, PIM's own documentation says ticket information at activation is informational and is not checked against any ticketing system. "IT-5521" is a typed string, so linking the activation to the real ticket depends on people typing the right number. Second, the blocked self-approval at 09:22 is the most instructive row for anyone studying permission-aware behavior, and it is also the row most likely to leave no trace in a summary report.

## Evidence fields that show authority, not just activity

An audit log can show that an account changed. It takes more fields to show that the change was authorized. For the 09:44 change above, these are the ones that carry the authority story.

| Field | What it establishes | In the example (Illustrative) |
|---|---|---|
| Business request and verification | Why the action was needed and that the requester was genuine | Ticket IT-5521 with the video-call check noted |
| Elevation request with justification | The actor asked for authority before acting | Activation request citing IT-5521 |
| Rejected or blocked attempts | Where the boundary was, and that it held | Self-approval at 09:22 left pending |
| Approver identity and time | A different person granted authority, within the window | IT manager at 09:41 |
| Authority window | How long the authority lasted | Role active until 10:41 |
| Action entry | What was done with the authority, and when | Sign-in methods updated at 09:44 |
| Outcome | The action achieved its purpose | Director signs in at 09:58; ticket closed |

Retention decides whether any of this survives. Microsoft's documentation says Entra audit logs are kept seven days on the Free tier and 30 days on P1 and P2, and that data not routed to longer-term storage cannot be recovered once it expires. A company that never archived its logs may have the tickets but not the approvals, which leaves the middle of the story missing.

One example cannot show how many changes went through the gate, how many blocked attempts were recorded, or whether ticket numbers were typed correctly. Those are measured in SourceX's review with the company.

## Does the company qualify, and what stays unknown?

The company needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license its records, 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.

What stays unknown until SourceX reviews it: how many changes pass the acceptance check, how employee identities are de-identified, whether security policy or a managed service provider's contract limits use, and whether any buyer wants this task type. Interest in permission-aware agents across the industry does not mean every audit log qualifies. The [company qualification checklist](/resources/company-qualification-checklist) covers the basics, and related records are listed in the [data types hub](/data-types). Partners stay at metadata level: which identity and ticketing systems, how long approvals are kept, and who owns them.

## Go deeper on permission-aware agents

- [Questions to ask a client about permission-aware agents](/questions/does-permission-aware-agents-data-qualify): a discovery list for an IT or security lead.
- [Record gaps that make permission-aware agents hard to assess](/questions/permission-aware-agents-evidence-gaps): the missing approvals and short retention windows that most often break the trail, and how to spot them early.
- [Permission-aware agents review packet](/resources/permission-aware-agents-review-packet): what an evidence packet for SourceX's review should contain, item by item.

## 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 or finance lead confirms that second-approver changes are system-enforced and archived beyond the tool's default window, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the CIO or COO.

## Sources

- https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-approval-workflow
- https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-resource-roles-configure-role-settings
- https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-how-to-change-default-settings
- https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-reports-data-retention
- https://refer.sourcex.si/terms
