> 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/gamification/fortune-wheels/deactivating-fortune-wheels.md).

# Deactivating Fortune Wheels

Because redemptions must remain auditable, full deletion is restricted.\
However, Fortune Wheels can be **deactivated** or **hidden**.

***

### Deactivating a Fortune Wheel

Deactivation makes the wheel unavailable to members while keeping it in the admin panel.

To deactivate:

1. Edit the wheel
2. Scroll to **Status**
3. Toggle **Active fortune wheel** off

<figure><img src="https://226878483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ4Fuoa1PTF0DrNTgjzJu%2Fuploads%2Fgit-blob-49e9078bcfaab2d4c92581a8ce3d657c57573850%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

Inactive wheels can be:

* Edited
* Duplicated
* Reviewed
* Reactivated at any time

***

### Alternative ways to remove access

If you prefer not to deactivate:

#### 1. Change availability

Set end date to a past date.

#### 2. Adjust visibility

Set visibility to “hidden”.

#### 3. Restrict targeting

Assign a different segment or tier.

***

### Canceling a redemption (optional)

From the redeemed wheel list, select:

* **Cancel redemption**

<figure><img src="https://226878483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ4Fuoa1PTF0DrNTgjzJu%2Fuploads%2Fgit-blob-82ce01e6c9cc6fa775d44f0ab8944080a95cae9f%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Cancelling a redemption does **not** automatically refund points or reverse rewards.\
Adjustments may need to be handled manually.
{% 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/gamification/fortune-wheels/deactivating-fortune-wheels.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 `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.