Agent attribution and authorization

Who authorized this AI agent? Answer it from the record

The question is simple and an ordinary log cannot answer it. Provantix binds each action to the agent's identity, its accountable owner and the credential that authorized it, follows the delegation from the human request, and shows a human approval where one was recorded.

See one action traced, end to end How attribution works Get an invite

Identity, owner and credential

Each action is attributed to an agent, with the method and a confidence: a dedicated credential is treated as certain, a shared one or a timing match is lower and labelled.
Microsoft Entra ID service principals and sign-ins are bound to actions (beta); Microsoft 365 audit is in validation.
Activity that cannot be linked to an agent is kept and listed for review, never dropped.

Delegation and approvals

The delegation chain runs from the human request through agents and sub-agents, with each tool call and its outcome.
Where your application sends the approval with the action, its id, policy, ticket and approver (as a handle, never a name) are sealed on the record.
A sensitive action with no recorded approval raises a finding, and an overview shows how many actions had one.

Authority declared against what was observed

Mark which systems each agent is expected to reach; coverage shows what was expected, what was observed and what has independent evidence.
Findings for shared credentials, reach beyond granted authority, agents with no owner and standing admin grants.
Every human decision (owner, lifecycle, attestation) goes in one decision log, with who and when.

Honesty, up front

What the evidence proves, and what it does not

What it proves

Which identity acted, which credential it used, and the order and delegation path your agent reported.
That an approval was attached to an action, when your application sent it.

What it does not

That a person approved something your application never reported. Provantix cannot see approvals given elsewhere.
That a credential was properly issued, or that access was reviewed. Those are your identity processes.
Anything about an action an agent did not report. A second, independent source is what closes that gap.

Approvals: who approved what — What is shown, and what decides whether you see approvals.
Coverage — Expected, observed and independently evidenced.
Connectors — Entra ID, Microsoft 365, Langfuse and LangSmith imports, direct HTTP and the SDK.
Pricing

Get an invite

Invite-only during early access. We check your email with a one-time code, then review your request and send the invite. Ask for a demo if you want one.