---
key: turn-an-automation-on-or-off
title: Turn an automation on or off
audience: staff
section: automation
routes: ["/lifecycle-automation/automations"]
permissions: ["lifecycle_automation.definitions.publish"]
features: ["lifecycle_automation.definitions"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Find an automation in the Automations list, check whether it is ready to run, then turn it on or pause it with one confirmed click.
keywords: [enable automation, disable automation, switch off reminders, stop automatic texts, pause follow-ups, activate]
related: [use-the-automation-center, pause-many-automations-or-restore-the-defaults, start-an-automation-with-guided-setup, send-payment-reminders-automatically]
---

In the sidebar, open **Automation**, then **Automations**. The page address is `/lifecycle-automation/automations`. This is the plain on/off list for every automation in your organization, without opening the builder.

## Before you start

- Anyone with automation view permission can read the list. Turning an automation on or off needs permission to publish automation definitions; without it the **Turn on** and **Pause** buttons stay off.
- You have to be online. When you are offline the page shows a notice and every switch is disabled until you reconnect.

## Steps

1. Find the automation. Type in **Search automations** or press **Filters** and narrow by **Status** (**On**, **Off**, **Draft**, **Archived**), **Domain** (for example **Work Orders** or **Invoices**) or **Channel** (**Email** or **SMS**).
2. Read the readiness chip next to the status chip on the row. **Ready** means it can run; **Running** means it is already on; **Needs setup** means something is missing, and the row says what, for example a texting number that is not set up yet, or no published version.
3. To switch it on, press **Turn on** on the row. The **Turn on automation?** dialog explains that new matching records will start enrolling. If there are unresolved checks, they appear under **Setup warnings** so you can decide.
4. Press **Turn on automation** to confirm. The status chip changes to **On**.
5. To stop it, press **Pause** on the row. The **Pause automation?** dialog warns that pending work is blocked and active enrollments are paused, even for records where someone forced the automation on.
6. Press **Pause automation** to confirm. The chip changes to **Paused**.

## What you see

- Four counters at the top: **Total**, **On**, **Off** and **Needs setup**.
- Each row shows the automation's name, a **Default** tag when it is one Nova ships with, the status chip, the readiness chip, the channel, the area it belongs to, how many records are enrolled, how many actions are pending and when it was last updated.
- **Advanced** on a row opens the full builder for that automation, where the trigger, timing and messages can be changed.
- **Simple view** at the top opens **Customer Messages** (in **Settings**, under **Communications**), a shorter list of the same switches.

## If something looks different

- **Turn on** is greyed out and the readiness chip reads **Unavailable**: the automation cannot run in your organization right now. Open **Advanced** to see why, or ask your admin.
- The chip reads **Globally paused**: someone paused this automation for the whole organization. **Turn on** lifts that pause.
- The list is empty and reads **No automations match these filters**: set each filter back to **All statuses**, **All domains** and **All channels** and clear the search, or use **Verify default pack** to restore the standard automations. See [[pause-many-automations-or-restore-the-defaults]].

[[route:/lifecycle-automation/automations|Open Automations]]

## Built-in and custom automations

Built-in automations offer **Turn on** and **Turn off**. Turning one off cancels its unsent messages and keeps its history. Turning it back on resumes future scheduled work; missed reminders stay unsent. Built-ins cannot be archived or deleted. Catalog updates preserve your off choices and custom wording.

Custom automations can be archived. **Delete unused draft** is available only for a custom draft that has never been published or used, and needs permission to delete drafts.

When publishing a custom automation, **Replace a built-in message (optional)** lets you choose the built-in message it replaces. Publishing turns that built-in off and cancels its unsent work. Nova prevents both from being active together. Pausing the replacement keeps the built-in off; turn it on explicitly when ready.