A person reviewing an action before it is carried out

Capability is not permission

A tool being available does not mean it is authorised for every user or every situation. The service must check who is acting, what they may do and under which conditions.

Make the consequence visible

Before a purchase, payment, submission, message or record change, show what will happen, which account or service is involved and whether the action can be reversed.

Use least privilege

Give an agent only the access needed for the task and only for as long as needed. Avoid broad access and permissions that outlive the user's intent.

Keep a useful record

Record what was requested, what the agent attempted, what the service accepted, what the user approved and the result returned by the system. Protect those records and retain only what is justified.

Plan for failure

An agent may misunderstand. A service may time out. A tool may return incomplete information. Build clear stop points, safe retries, duplicate protection and escalation to a person.

A simple test

Could the user explain what the agent is about to do, why it is allowed, and how to stop it? If not, the interaction needs more work.

← Back to education