# Agent approvals: show the exact proposed change

Bind approval to a specific proposed action. Show the target, the old and new values, expected effect and expiry where applicable. If the action changes after review, require another decision rather than silently reusing approval.

## Worked example

A support-note update preview identifies customer C-104 and shows the proposed text. If the agent later switches to billing_email or a different customer, the original approval no longer describes that action.

## Copyable prompt

```text
Design an approval preview for [ACTION]. Include authenticated requester, exact target, proposed field changes, old/new values, expected external effect, expiry and a stable identifier or digest for the reviewed payload. Describe what invalidates the approval. Treat this as a UI and server contract; a button click must not authorize a different later payload.
```

## Checklist

- Show the exact target and field changes.
- Bind approval to the reviewed payload.
- Invalidate approval when relevant inputs change.
- Verify permission again at execution.

## Further reading

[OpenAI: safety in building agents](https://developers.openai.com/api/docs/guides/agent-builder-safety)