> 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/main-features/badges/viewing-badges-in-member-profiles.md).

# Viewing Badges in Member Profiles

## 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.

<figure><img src="/files/bPvxPwtRqVm0Pf6NciMs" alt=""><figcaption></figcaption></figure>

### 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.openloyalty.io/main-features/badges/viewing-badges-in-member-profiles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.