Source: https://docs.amadalis.ai/reference/copilot/

# What you can ask the copilot

Open **Copilot** in the site admin to ask for a result. Use this reference to check whether a request needs approval and whether it can offer Undo.

Checked against the product’s code on 7 November 2026.

Describe the result you want in ordinary words. The copilot can read facts, prepare drafts and propose changes using the requests available on your site. The model proposes; the platform authorizes. The platform checks your role, the request and any required approval before applying it.

This reference describes the requests available in the checked version of the product. It does not establish what version is serving on your site. A feature can be switched off, a connection can be missing or your role can lack permission. Asking the copilot what it can do should reflect that site’s available requests.

## Approval and Undo

An approval card presents the proposed change and its consequence. **Approval: Yes** means the request requires your separate decision before application. A draft or read can have **Approval: No** and still require permission. Preparing a draft does not grant permission to publish it. A person’s own **Publish** click in EmDash’s editor publishes at once, as their explicit act. Anything the copilot publishes always pauses for the approval card.

**Undo: Available** means the request can be reversed. The receipt must offer **Undo** for that particular change. Later edits or missing saved information can prevent that reversal. **Undo: No** means the request itself supplies no automatic Undo. Sending email, permanently erasing data or opening a settings screen cannot be assumed to offer Undo.

An approved change goes ahead even if its Activity record fails to save; the failure is logged on the server. The change keeps any Undo it offered on its receipt.

## Requests by area

Choose the area of the change you want. Each linked table lists supported requests, whether approval is required and whether the result can offer Undo.

-   [Pages and reusable sections](https://docs.amadalis.ai/reference/copilot/pages-and-sections/).
-   [Content and media](https://docs.amadalis.ai/reference/copilot/content-and-media/).
-   [Navigation and SEO](https://docs.amadalis.ai/reference/copilot/navigation-and-seo/).
-   [Forms and comments](https://docs.amadalis.ai/reference/copilot/forms-and-comments/).
-   [Audiences and targeted content](https://docs.amadalis.ai/reference/copilot/audiences-and-targeting/).
-   [Analytics and events](https://docs.amadalis.ai/reference/copilot/analytics-and-events/).
-   [Experiments](https://docs.amadalis.ai/reference/copilot/experiments/).
-   [Store and membership](https://docs.amadalis.ai/reference/copilot/store-and-membership/).
-   [Account, team and visitor privacy](https://docs.amadalis.ai/reference/copilot/account-and-privacy/).
-   [Site settings and structure](https://docs.amadalis.ai/reference/copilot/site-and-settings/).
-   [WordPress migration](https://docs.amadalis.ai/reference/copilot/migration/).
-   [Conversation and Undo](https://docs.amadalis.ai/reference/copilot/conversation-and-undo/).

## Service staff

[Service administration](https://docs.amadalis.ai/reference/copilot/service-administration/) identifies requests that require service staff authority. They are not customer permissions.

For the explanation of the approval flow, read [The copilot’s governed tools](https://docs.amadalis.ai/developers/governed-tools/).