> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/documents-and-library/deactivate-and-reactivate-a-template.md).

# Deactivate and reactivate a template

Retire a document template, check dependent playbooks, and reactivate it when needed.

Deactivate a document template to prevent new documents from being created from it while keeping the option to reactivate it later. Existing documents keep their content.

The same steps apply to PowerPoint presentation templates on the same page. New to templates? Start with [Templates in Rhythms](https://help.rhythms.ai/documents-and-library/templates-in-rhythms.md).

## Before you begin

You need access to workspace template settings. If **Templates** is missing, ask a Rhythms Admin for help.

**Review playbooks that use the template before deactivating it.** Deactivation does not disable those playbooks.

1. Open **Playbooks** and select a playbook that creates or refreshes documents from this template.
2. Open **Configuration** and review its **Instructions**. Work with the owner to update references to an active replacement template. For a workflow change, ask the assistant to edit the playbook and review the change before confirming it.
3. If the playbook should stop running on its schedule, open its **⋯** menu and select **Disable**. You need **Can edit** permission.

A template’s document count is not a complete list of playbooks that depend on it. [Playbooks that create or refresh documents](https://help.rhythms.ai/documents-and-library/playbooks-that-create-or-refresh-documents.md) explains how to find them. If you cannot confirm which playbooks use the template, ask your admin or [Rhythms Support](mailto:support@rhythms.ai) before continuing. See [Edit a playbook](https://help.rhythms.ai/playbooks/create-and-run-a-playbook.md#edit-a-playbook) for details.

## Deactivate a template

1. Open **Settings** from the left navigation.
2. Under **Workspace**, select **Templates**.
3. Use **Search templates** to find the document template.
4. Open its **⋯** menu and select **Deactivate**.

The template stays on the Templates page with an **Inactive** badge and is removed from the default template listing in the Library. Deactivate and Activate live on the Templates page; a template's tile in the Library only shows the badge.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FaByaDVb3o1C3XlLazoQV%2Fclipboard.jpeg?alt=media&#x26;token=7274207a-9841-4b19-92d9-0fa88fe667f3" alt="Template actions menu in Rhythms Settings, with Deactivate above Delete."><figcaption></figcaption></figure>

*Choose Deactivate from the template’s ⋯ menu.*

## Reactivate a template

1. Return to **Settings › Workspace › Templates**.
2. Search for the template by name. Inactive templates appear on this page alongside active ones; no separate archive view is needed.
3. Look for the **Inactive** badge, open **⋯**, and select **Activate**.

The Inactive badge disappears and the template becomes available again. Reactivating the template does not reactivate a disabled playbook. Review the playbook separately before resuming it.

## Frequently asked questions

### Will existing playbooks continue to work?

Existing document content is preserved. Deactivating hides the template from the Library and from the assistant's template search, so a playbook that finds its template by name no longer finds it when it creates the next document. Refreshing a document in place and creating a new copy each period are different workflows. Before deactivating a template used by either workflow, confirm its dependencies with the playbook owner or [Rhythms Support](mailto:support@rhythms.ai).

If a run fails, open the playbook’s **Overview → Run history** and use **Review and fix**. Restore the required template or update the playbook to use an active replacement before retrying.

### How are deactivation and deletion different?

**Deactivate** is reversible: the template is archived and can be activated again. **Delete** removes the template permanently; there is no trash or Activate action to restore it. Existing documents keep their content, but future workflows that reference a deleted template may fail. Check dependencies before either action.

### Can I delete a template through chat?

You can’t delete templates in **Rhythms Chat**. A supported external chat client connected through **Rhythms MCP** can request template deletion, subject to your permissions. See [Use Rhythms from Claude, ChatGPT, or Cursor](https://help.rhythms.ai/connectivity/use-rhythms-from-claude-chatgpt-or-cursor.md). To retire a template with the option to restore it, use **Deactivate** in Settings.

## Related articles

* [Templates in Rhythms](https://help.rhythms.ai/documents-and-library/templates-in-rhythms.md)
* [Playbooks that create or refresh documents](https://help.rhythms.ai/documents-and-library/playbooks-that-create-or-refresh-documents.md)
* [Create reviews from templates](https://help.rhythms.ai/documents-and-library/create-reviews-from-layouts.md)
* [Create and run a playbook](https://help.rhythms.ai/playbooks/create-and-run-a-playbook.md)
* [Keep a document up to date automatically](https://help.rhythms.ai/documents-and-library/keep-a-document-up-to-date-automatically.md)


---

# 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://help.rhythms.ai/documents-and-library/deactivate-and-reactivate-a-template.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.
