> 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/events/sign-up-for-an-event/how-to-limit-player-quantity-in-events.md).

# How to Limit Player Quantity in Events

An Admin can limit the number of Customers who participate in an Event within the Event settings. By writing the preferred number into the “Capacity and Admission” section during the Event creation flow, the total participants will be capped.

For example, when an Admin chooses a Total Teams quantity of 10 and a Team Size of 1, this means 10 Customers can join the Event.

If there is a value >0 in the “Max Guests per Person” text box, then a Customer could signup for an Event and pay for a Guest [***during the Event signup flow***](https://help.podplay.app/en/articles/3232449). If a Customer signs up and pays for a Guest, this counts as 2 toward to the total of 10 possible Customers who can sign up for the Event.

**PLEASE NOTE:** the “Total Size” should remain at one (1) until the Team Signup feature is available. The Team Signup feature is not yet live, and therefore the Total Size section should not be changed.

***

**Below to be included when the functionality exists to have team sign-ups.**

***

* Team size >1 is used for Events involving teams of 2 or more (e.g. doubles).
  * This functionality will be ready by the end of Q1, 2024.
* Continuing with the example, this means a Total Teams of 8 and a Team Size of 2 will mean 16 Customers can join an Event.


---

# 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/events/sign-up-for-an-event/how-to-limit-player-quantity-in-events.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.