> 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/content/virtual-platform/companies/company-tags.md).
# Company tags (Virtual event)
Tags can be created to group companies into categories and/or streamline the virtual event.
## The home page
To find the company tags home page, select 'Company tags' from the Actions button on [the company home page](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/companies#the-home-page).
## Managing tags
### Creating a tag
1. Open [the home page](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/companies#the-home-page).
2. Click on 'New tag'.
3\. Type a name for the tag.\
4\. Click on the 'Add tag' button.
### Editing and deleting tags
Like companies themselves, each tag has two icons to their right (Under actions):
- Edit icon: Click here to make adjustments similar to when first creating a tag.\
- Delete icon: Click here to remove the tag altogether.
{% hint style="info" %}
Company tags will only be displayed in the platform when fifteen or more companies have been added to the admin panel.
{% endhint %}
## The result
### Self-select company tags
Companies can select which business tags they find relevant to them and add these to their profile. This can be done by editing the company profile in the app, virtual event or exhibitor portal.
---
# 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/content/virtual-platform/companies/company-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.
