> 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-types.md).
# Manage Event Types
### Overview
Event Custom Types let you create and manage the list of custom **Class** and **Event** types shown to Customers in the PodPlay web app filters. Use this when you want Customers to be able to find specific kinds of community events (for example: “Beginner Clinic”, “Open Play”, or “Round Robin”).
### Where to find Event Custom Types
* Open **Company Settings**
* Stay on the **Overview** tab
* Scroll to **Community Event Settings**
* Find **Event Custom Types**
### Create a new custom type
* In **Event Custom Types**, expand either **Class** or **Event**
* Click **New type**
* In the drawer:
* Enter the **Type Name**
* Select a **Subtype**
* Toggle **Show on Web App** on or off
* Click **Continue**
When you create a type, it becomes available immediately for use in your Community Events setup.
{% hint style="warning" %}
**PLEASE NOTE:** Type names must be unique and can only include letters, numbers, and spaces.
{% endhint %}
### Show or hide an existing type on the web app
* In **Event Custom Types**, select an existing type
* In the drawer, toggle **Show on Web App**
* Click **Continue**
When **Show on Web App** is enabled, Customers can see this type in the public app’s advanced filters. When it’s disabled, the type is hidden from those filters.
{% hint style="success" %}
Save settings when done editing or creating new types before clicking away from the Company Settings page.
{% 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://docs.podplay.app/owners-playbook/build-your-club/company-settings/manage-event-types.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.
