> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/users/application/untitled/user-badges.md).

# User badges

Badges can be downloaded and printed for users to use during the live event. This article explains how to generate badges (for a specific user group).

## The home page

To find the home page for user badges in the admin panel, select 'User badges' from the actions drop-down menu on [the user's home page](https://knowledge-base.letsgetdigital.com/the-admin-panel/users/application/untitled).

![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2F93O9nvDpPj8IQo1Y7tNd%2F2022-01-28_15-23-43.gif?alt=media\&token=dc4796d1-c94f-42bf-a9a8-fdbde1c688c5)

### Understanding the home page

On the home page, there are a variety of quick view headings for the generate badges. These are as follows:

| Time                                    | Sort                                            | Filter checked-in                                                                      | Status                                                                       | Actions                                                                     |
| --------------------------------------- | ----------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Date and time the badges were generated | Badges are sorted by either first- or last name | 'Yes' includes badges of not checked-in users, while 'No' does not include these users | The status of the generated badges, either 'Success', 'Waiting', or 'Failed' | Successfully generated badges may be exported as a PDF-file or re-generated |

## How to generate user badges

1. Open the home page.
2. Click on 'Generate new badges'.
3. Select the sort the badges either by first or last name.
4. Tick the box to only include badges of not checked-in users.
5. Additionally, there is an option to generate badges for a specific group of users with a tag.
6. Click on 'Generate badges'.

![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2FST3mRzpptVDkIs0rXUW2%2F2022-01-28_15-29-19.gif?alt=media\&token=383db589-99b5-4986-a867-2e2b4b7ebb33)

{% hint style="info" %}
**Please note:** Generating a badge may take a moment. Please refresh the page to receive an update on the status.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge-base.letsgetdigital.com/the-admin-panel/users/application/untitled/user-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 `automate deployments from our CI pipeline` 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.