Agent Access
Grants and scopes
Use the lowest useful grant, make expiry deliberate, and keep hard boundaries around billing, secrets, raw data, and grant management.
Choose the lowest useful grant #
Scope the grant to the task, endpoint, and time window the agent needs. Use expiry and revocation as normal controls, not exceptional cleanup.
Authority tiers #
Use these as customer-facing examples of grant shape. Exact scope identifiers belong in the Agent Operations API contract.
| Tier | Allows | Does not allow |
|---|---|---|
| Observer | Read docs, manifest, setup summaries, event history, receipts, and redacted diagnostics state. | Replay, sharing diagnostics, endpoint edits, secret rotation, billing, or grant changes. |
| Recovery preparer | Preview replay or diagnostics intents and explain the required human decision. | Execute side-effecting recovery without an execution grant. |
| Recovery operator | Execute specific governed recovery actions that were previewed and are inside the grant. | Self-escalation, broad Shopify authority, support submission, billing approval, or raw secret access. |
Audit #
Sensitive reads, action previews, confirmations, replays, diagnostics shares, endpoint edits, and secret rotations leave audit context that preserves human or authorized-agent attribution.
Operating rules
Use these controls to keep agent access scoped and reversible.
- 01Identify the job the agent is allowed to perform, such as setup inspection, event investigation, or recovery preparation.
- 02Choose the lowest authority tier and scopes that cover that job.
- 03Use a bounded expiry unless the merchant explicitly accepts the risk of longer access.
- 04Revoke the grant when the work is finished or when the partner no longer needs access.
- 05Review audit entries for sensitive reads, action-intent previews, confirmations, replays, and diagnostics shares.
FlowRelay