Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions mintlify/global-accounts/agents/approvals-and-audit.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ When an agent submits an action that is not eligible for automatic execution, Gr

1. Agent submits an action (quote execution or transfer).
2. Grid creates an `AgentAction` with `status: PENDING_APPROVAL` and returns it to the agent.
3. Grid fires `AGENT_ACTION.PENDING_APPROVAL` to your webhook endpoint with the full action payload.
3. Grid fires `AGENT_ACTION.PENDING_APPROVAL` to your [webhook endpoint](/global-accounts/platform-tools/webhooks) with the full action payload.
4. Your backend sends a push notification to the customer.
5. Your app shows the customer the requested amount, accounts, and reason.
6. The customer approves or rejects from that trusted surface.
Expand Down Expand Up @@ -111,7 +111,6 @@ Support at least two controls:
Pause is useful for temporary uncertainty. Revoke is appropriate when a device is lost, a credential is exposed, or the customer no longer wants the agent connected.

Grid enforces these controls. Your product should surface the current connection state and expose the relevant actions in your own experience.

## What to show in the approval UI
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Missing blank line before heading

The blank line that previously separated the "Pause and revoke" section body from the ## What to show in the approval UI heading was accidentally removed in this diff. Mintlify (and most Markdown renderers) typically render headings cleanly without the blank line, but it is inconsistent with the surrounding section separators in this file and departs from the repo's formatting conventions.

Suggested change
## What to show in the approval UI
Grid enforces these controls. Your product should surface the current connection state and expose the relevant actions in your own experience.
## What to show in the approval UI
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/global-accounts/agents/approvals-and-audit.mdx
Line: 114

Comment:
**Missing blank line before heading**

The blank line that previously separated the "Pause and revoke" section body from the `## What to show in the approval UI` heading was accidentally removed in this diff. Mintlify (and most Markdown renderers) typically render headings cleanly without the blank line, but it is inconsistent with the surrounding section separators in this file and departs from the repo's formatting conventions.

```suggestion
Grid enforces these controls. Your product should surface the current connection state and expose the relevant actions in your own experience.

## What to show in the approval UI
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code


Your approval UI should answer:
Expand All @@ -126,7 +125,7 @@ All of this information is present in the `AgentAction` payload delivered via we

## Integration guidance

- Subscribe to `AGENT_ACTION.PENDING_APPROVAL` webhooks and send the customer a push notification immediately — quote-based actions expire quickly.
- Subscribe to [`AGENT_ACTION.PENDING_APPROVAL` webhooks](/global-accounts/platform-tools/webhooks) and send the customer a push notification immediately — quote-based actions expire quickly.
- Use `GET /agents/approvals` to build an in-app approval queue as a fallback for users who miss the push notification.
- Treat approval and rejection calls as idempotent in your integration so duplicate taps or retries do not cause confusing UX.
- Show `FAILED` and `REJECTED` outcomes clearly — they are distinct states with different meanings for the customer.
Expand Down
2 changes: 1 addition & 1 deletion mintlify/global-accounts/agents/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ Your product should surface:
- Policy configuration and permissions screens
- Approval and decision UX presented to end users on demand
- Agent activity, audit records, and transaction history
- Consumption of Grid events, webhooks, or approval callbacks
- Consumption of Grid events, [webhooks](/global-accounts/platform-tools/webhooks), or approval callbacks
- Customer messaging and notification design

## Next steps
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ These permissions are intentionally narrow and map to concrete Grid-backed actio

## Account restrictions

If a customer has multiple internal accounts, an agent should not automatically access all of them.
If a customer has multiple [internal accounts](/platform-overview/core-concepts/account-model), an agent should not automatically access all of them.

Use account restrictions to define:

Expand Down
Loading