With the manifest approved, the list of **"Actions"** it declares appears below: one card per button that saves, sends or deletes something. **They all start turned off** — turn one on only if you actually want the copilot to be able to run it. | Toggle | What it decides | | --- | --- | | **Enabled** | If it's off, that action doesn't exist for the copilot even if the manifest declares it — it's the first gate. | | **Internal / Both** | "Internal" keeps it for your team only. "Both" also opens it to visitors talking to the copilot on that site (useful only when it makes sense for a customer to create or edit something themselves). | | **Confirm on fill too** | Raises the product's own floor: it asks for confirmation even when filling in a field, not only when tapping the save button. It can never be relaxed below the minimum (always confirm on save/send/delete). | > **Notice — The plan history sits below** > > At the bottom of this same screen, "Plan history" lists every plan the copilot ran on this channel (date, status, a link to the conversation) — Proposed, Delivered, Completed, Cancelled, Failed, Expired or Rejected.