> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/product/accounts/enable-disable-an-account.md).

# Enable/disable an account

Learn how to enable or disable automated functions on an account

Every account has a master switch. This is found at the top of the sub-account dashboard. When an account is live, the account's syncs, triggers, and workflows will run. When you disable an account, new automatic syncs and scheduled workflows stop being queued, and background trigger and workflow processing pauses as workers refresh their account list.

Work already running can finish. Real-time workflow API endpoints remain available until disabled separately.

An account's live status is indicated by the blue (live) or gray (disabled) circle next to the account name in the upper-left corner.

<figure><img src="https://932524191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mks_UuU2atghAuA9bQz%2Fuploads%2FqoUlXUE9A5YWybmSdWSa%2FScreenshot%202024-10-28%20at%209.57.39%E2%80%AFPM.png?alt=media&amp;token=1168b03b-e0ea-48a3-a31d-158054ede834" alt=""><figcaption><p>Click Enable syncs in the warning message to turn on automated syncs and triggers</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/product/accounts/enable-disable-an-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.