# Understand assistant changes and approvals

An assistant's permissions and available tools determine which changes it can
request. The connected service’s actual tool catalogue determines the supported
changes; it can vary by environment and release. A read or write grant does not
bypass your existing restaurant permissions or a required approval.

## Before a supported change

1. Check the restaurant, location, and menu or other supported target.
2. State the exact value to change. For menu notes, say whether to replace the
   text or clear it.
3. Ask the assistant to read the current value and explain the intended change.
4. Follow any approval instructions returned by the supported service.

Do not approve a different target or additional changes just to finish the
request. If the service does not expose the needed action, perform it through
the authorised restaurant interface.

## Queued is not completed

If the response is `pending_approval`, the request has been queued. It has not
been confirmed as applied. A completed tool request also needs an outcome check:
the assistant should read the target again and report the saved value.

If the connection times out, ask it to check current state before resubmitting.
Do not assume a second request is harmless.

## Unsupported requests

Ask an authorised restaurant operator to handle payments, refunds, bookings,
cash entries, close of day, guest messages, and other actions when their tool is
absent from the connection. See [external capabilities](/agents/capabilities)
and [agent workflows](/agents/workflows).