> 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/badges/managing-badges.md).

# Managing Badges

Edit badge details, open badge pages, and deactivate unused badges.

## Overview

Use the **Badges** list to browse all badges in your environment.\
From the list, you can edit details, grant badges, open badge pages, or deactivate.

### What you see in the badges list

The list typically includes:

* Badge name
* System code
* Status

<figure><img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/k0skSGxvV6kSJLx28vYr/image.png" alt=""><figcaption></figcaption></figure>

### Available actions

From the actions menu next to a badge, you can:

* **Edit**: update the displayed name or description.
* **Grant**: assign the badge to a specific member.
* **View**: open the badge details page.
* **Deactivate**: disable the badge.

### Deactivate a badge

{% hint style="warning" %}
Before deactivating, confirm the badge isn’t referenced in campaign rules or effects.\
If it is, those campaigns may stop behaving as expected.
{% 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/badges/managing-badges.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.