> 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/series-capacity.md).

# Series Capacity

### Overview

The **Total Teams** field controls how many signups a Series accepts. What it counts depends on the Series. On a solo Series (Team Size of 1), Total Teams 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.

An Admin can change this quantity after a Series exists. The new value writes to every remaining session at once.

{% hint style="warning" %}
**Editing capacity after a Series is published is not a best practice.** Set the quantity before Customers sign up where you can.
{% endhint %}

### Change the quantity

1. Find and click the Series you want to edit.
2. On the **Overview** tab, expand the **Capacity and Admission** section.
3. Change the **Total Teams** quantity to the new number of Customers, or on a team Series, the new number of teams.
4. Click **Save** in the corner of the Series side panel.

{% hint style="info" %}
On a team Series, both **Total Teams** and **Team Size** are set at the Series level. Both fields are read-only when you edit a single session. See Team signup for a Series in the Create a Series article.
{% endhint %}

### Which sessions the new quantity reaches

A save writes the new quantity only to sessions that have not happened yet. Cancelled sessions are left alone.

Sessions that already finished keep the capacity they ran with, so the Series holds its historical record. After you save, the drawer reports how many sessions 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 you enter is below that floor, the save is rejected and an error explains why. Raise the quantity, or cancel signups on the remaining sessions first.

### Common issues

* **The save is rejected with a capacity error:** The new quantity is below the number already signed up on one of the remaining sessions. Raise the quantity, or cancel signups on those sessions first.
* **Sessions show different Total Teams values:** Completed and cancelled sessions keep their original capacity. Only future sessions receive the new value.
* **A Customer you added is not in every session yet:** Propagation runs as a background job and takes a few seconds to finish.


---

# 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/series-capacity.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.