> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/campaigns/challenges/deactivating-and-deleting-challenges.md).
# Deactivating and Deleting Challenges
You can **deactivate** a challenge individually.
You can **delete challenges only in bulk** from the challenges list.
### Deactivating a single challenge
1. Navigate to **Loyalty Modules → Challenges**.
2. Click the context menu on the right-hand side.
3. Select **Deactivate challenge**.
4. Confirm when prompted.
### Reactivating a challenge
1. Navigate to **Loyalty Modules → Challenges**.
2. Click the context menu on the right-hand side.
3. Select **Activate challenge**.
4. Confirm when prompted.
{% hint style="info" %}
Deactivation keeps the challenge configuration and reporting available in the Admin Panel. Inactive challenges don’t accept new member progress.
{% endhint %}
### Deleting challenges in bulk
1. Navigate to **Loyalty Modules → Challenges**.
2. Click on **Bulk actions** in the top-right area. The count of selected challenges appears next to the button.
3. Select one or more challenges by clicking the checkbox next to each challenge name. You can also click the checkbox in the column header to select all visible challenges.
4. Select **Delete challenges** from the dropdown.
5. Confirm when prompted.
To cancel the selection without deleting, click **Close**.
{% hint style="danger" %}
Bulk deletion is permanent and can’t be undone.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/implementation-guide/campaigns/challenges/deactivating-and-deleting-challenges.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
