> 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/viewing-badges-in-member-profiles.md).
# Viewing Badges in Member Profiles
Review and manage a member’s badge assignments from their profile.
## Overview
Review a member’s assigned badges directly in their profile.\
You can also edit badge count or remove a badge from this view.
### Open the badges view
1. Go to **Members**.
2. Open the selected member profile.
3. Go to the **Badges** section.
### What you see
The badges table shows:
* Badge name
* System code
* Badge count
* Status
{% hint style="info" %}
**Badge count** is how many times the same badge was granted to the member.\
You can edit it manually if you need to correct data.
{% endhint %}
### Available actions
From the member profile, you can:
* Edit badge count
* Remove the badge
* View badge details
---
# 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/viewing-badges-in-member-profiles.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.
