Skip to content
AX Framework
Principle 05

Clear Permissions

What an agent is allowed to do should be explicit, scoped to the task, visible to the person who delegated it, and revocable at any time.

AX proposalTrust & Control

Why it matters

Delegation without clear limits forces a bad trade-off: grant too little and the agent cannot finish; grant too much and a mistake becomes expensive.

Clear permissions also let the product make better decisions, such as allowing an agent to browse freely while requiring confirmation before it spends money.

Examples

Good exampleIllustrative

An agent receives a grant limited to reading orders and creating returns, valid for 24 hours, with a spending limit of zero.

json
{
  "grantId": "grt_41c",
  "agent": "assistant.example",
  "onBehalfOf": "user_2291",
  "scopes": ["orders:read", "returns:create"],
  "limits": { "spend": { "amount": 0, "currency": "EUR" } },
  "expiresAt": "2026-10-07T14:00:00Z"
}
Bad exampleIllustrative

The agent is given the user's password and therefore inherits every permission the user has, including changing the password.

Implementation guidance

  1. 1Model permissions around capabilities, not around screens.
  2. 2Make grants time-bound by default.
  3. 3Show the delegating person exactly what an agent can do, in plain language.
  4. 4Return a specific error when a permission is missing, naming the scope required.

Evaluation criteria

  • Agents never need a human's primary credentials.
  • Grants are scoped, time-limited, and listed in a user-visible place.
  • Permission errors name the missing scope.