> 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/event-series/how-to-edit-the-participant-quantity-in-a-series.md).

# How to edit the participant quantity in a Series

* An Admin is able to edit how many participants are allowed to sign up for a Series.
* The **Total Teams** field sets that quantity, and what it counts depends on the Series:
  * On a solo Series (Team Size of 1), it is the number of Customers who can join.
  * On a **team** Series, it is the number of **teams** that can join — not the number of players.
* To do so:
  * Find and click on the Series you want to edit
  * On the **Overview** tab, expand the **Capacity and Admission** section
  * Change the Total Teams quantity to reflect the new number of Customers — or, on a team Series, the new number of teams — who can join the Series
  * Click on the Save button in the corner of the Series side panel
* The new quantity is applied to every remaining Event in the Series.
* If the new quantity is below the number already signed up — Customers on a solo Series, teams on a team Series — the save is rejected and an error explains why. Raise the quantity instead, or cancel signups first.
* The video below shows this process and a verification that each Event in the Series was changed.
* NOTE: it is a best practice to not edit the participant quantity after a Series has been Published.
* NOTE: for a **team** Series, Total Teams is the number of teams that can join (not the number of players), and both Total Teams and Team Size are set at the Series level — they are read-only when editing a single session. See *Team signup for a Series* in the Create a Series guide.

## Which sessions the new quantity reaches

* A save only writes the new quantity to sessions that **have not happened yet**. Cancelled sessions are left alone as well.
* Sessions that already finished keep the capacity they ran with, so the Series holds its historical record. After saving, the drawer reports how many were held back — for example, *1 completed session kept its original capacity.*
* Because of this, a Series that has already run can legitimately show different Total Teams values across its sessions.

## The lowest quantity you can set

* The quantity cannot go below the largest number already signed up **among the remaining sessions** — Customers on a solo Series, teams on a team Series.
* Completed sessions do not hold the quantity up. A Series that filled to 20 in week 1 can still be lowered to 12 for the sessions that are left.
* If the value entered is below that floor, the save is rejected and an error explains why. Raise the quantity, or cancel signups on the remaining sessions first.


---

# 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/event-series/how-to-edit-the-participant-quantity-in-a-series.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.