> 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/user-tags/creating-user-tags.md).
# Creating user tags
Here's how you can create a user tag in the system in order to assign a label to or categorize the different type of visitors of your event.
### How to manually create a user tag
You can quickly and easily create a user tag from the admin panel by completing the following steps:
1. Open the Admin panel
2. Go to Users --> All users
3. Select 'User tags' --> +New tag
4. Give the tag a name
5. Select 'Add tag' to Save
### The even easier way to create user tags
Although the manual option provides a quick way of creating single user tags in the admin panel there is a much quicker and simpler way of creating multiple user tags at once and assigning them directly to users through the use of an Excel import.
When importing your user into the system with an Excel sheet you can fill in the column named 'User tags' the specific tags you would like to create and assign them to the specific user as shown in the example below:
{% hint style="info" %}
Hint: you can even assign multiple tags to a user at once by adding a comma + a space i.e. Exhibitor, VIP, Day One
{% 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/user-tags/creating-user-tags.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 `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.
