> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/build-your-club/company-settings/manage-event-tags.md).

# Manage Event Tags

Event Tags let you organize and label Community Events so Customers can filter and discover the right events in the PodPlay web app. Use tags for things like skill levels, formats, or special categories (for example: “Beginner”, “Intermediate”, “Round Robin”, or “Clinic”).

## Where to find Event Tags

* Open **Company Settings**
* Stay on the **Overview** tab
* Scroll to **Community Event Settings**
* Find **Event Tags**

\[SCREENSHOT NEEDED: Company Settings > Overview page showing the Community Event Settings section with the “Event Tags” field]

## Create a new tag

* In **Event Tags**, expand the category (for example: **levels**)
* Click **New tag**

\[SCREENSHOT NEEDED: Event Tags dropdown expanded, showing tag categories and the “New tag” action]

* In the drawer:
  * Enter the **Tag Name**
  * Toggle **Show on Web App** on or off
  * If available, choose a **Tag Color**
* Click **Continue**

\[SCREENSHOT NEEDED: New tag drawer showing Tag Name, Show on Web App, and (if applicable) Tag Color]

When you create a tag, it becomes available immediately for use in your Community Events setup.

**PLEASE NOTE:** Tag names must be unique and can only include letters, numbers, and spaces.

## Show or hide an existing tag on the web app

* In **Event Tags**, select an existing tag
* In the drawer, toggle **Show on Web App**
* Click **Continue**

\[SCREENSHOT NEEDED: Editing tag drawer showing the Show on Web App toggle]

When **Show on Web App** is enabled, Customers can see this tag in the public app’s advanced filters. When it’s disabled, the tag is hidden from those filters.

## Save settings when done editing or creating new tags


---

# 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://docs.podplay.app/owners-playbook/build-your-club/company-settings/manage-event-tags.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.