> 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.md). # User tags Personalise communication, access, visibility and event experience by using user tags. Here you can read how to create, assign and mange your user tags to label or categorize visitors of your event. {% hint style="info" %} Looking for ways to [manage your user tags](https://knowledge-base.letsgetdigital.com/the-admin-panel/users/user-tags/managing-user-tags?q=user+tag)? Or information on how to [create](https://knowledge-base.letsgetdigital.com/the-admin-panel/users/user-tags/creating-user-tags) or [assign](https://knowledge-base.letsgetdigital.com/the-admin-panel/users/user-tags/assigning-user-tags) them? {% endhint %} ### What is a user tag? User tags are there to label or categorize the visitors of your event. By adding user tags you get more control over your user's experience with your event as they can be used to group/categorize your users for example; Speaker, Attendee, Exhibitor, VIP. By assigning a tag to a user you can tailor communication, event content, and the access of specific users. Here below are some examples of actions related to assigned user tags: * Send communication (e.g. emails and push notifications) to specific groups of users only (and exclude others). * Filtering of users in the platform * Permission to access specific sessions * Provide users access to specific event days * Access to menu items based on tags If a user is connected as a speaker to a session or a company booth they will automatically receive the tag 'Speaker and/or 'Exhibitor'
--- # 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.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.