> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand automation availability

> Separate current Autopilot permissions from older blocked campaign, rule, and playbook actions.

Use [Autopilot](/automation/autopilot) for the selected account's current **Off**, **Approval**, and eligible **Auto** modes and its action ledger. Several older automation controls still appear elsewhere in the app; their presence does not make their ad writes available.

## Choose the right workflow

| Task | Current next step |
| - | - |
| Review current account findings and eligible changes | Open **Autopilot**, inspect its mode, and review the ledger. |
| Repeat a report or account check | Create and approve a [scheduled task](/automation/scheduled-tasks). |
| Configure warnings | Set [Alerts and Budget Shield monitoring](/automation/alerts). |
| Pause delivery or change a budget yourself | Review and confirm the [manual Meta action](/meta-ads/delivery). |
| Post a comment on eligible ads | Review the owner-wide scope of [Auto Comment](/automation/auto-comment). |

## Older controls with unavailable ad writes

The older **Campaign Autopilot** settings, rules engine, playbooks, and creative-loop ad writes are unavailable. Budget Shield automatic pauses and Slack or Telegram pause/budget tools are also unavailable. Granting channel **Full Access**, changing an approval preference, or retrying does not enable these blocked actions.

**Settings → Automation** can show scan notification preferences and older campaign controls. Use notification preferences for the messages you want to receive; consult the current **Autopilot** page before treating an automatic-execution setting as an enabled permission. An older saved setting is not evidence that an ad action ran.

If an older action is rejected, move to the current manual review or Autopilot workflow. Check the exact account and entity, review the intended change, and inspect the confirmed result. Send the action name and error to [support](/help/contact) if the correct current workflow also fails.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.