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

# Updated Series features

* Signups are on the Series level
* Coaches are on the Event level
* Admins are not asked if they want to
* If you want to add a Customer to only 1 Event in the Series, add them as a Non-participant
* Attributes like event names, picture, description, advanced features, settle now (Court+), publishing status, admin notes, and several more have been moved to the series level. A new series invite link has been added (there is no need to share a link for a single event anymore, series have their own invitation link). We have removed the overlay asking “Apply to all Events”
  * We’ve also started the second part to this refactor, which includes moving signup orders to the series level, adding a coach to a series, visibility and scheduling, also kids & guests support for series


---

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