> 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-do-i-edit-a-series.md).

# How do I edit a Series

* Now that you have created a Series, you want to edit it. First, you’ll
  * Click on the specific Event Series you want to edit
  * Choose what to edit:
    * Participants
    * Generate a link to send to a Customer
    * Name of Series
    * Capacity of Series
    * Series Picture
    * Series public description
    * Tables/Courts in Series
    * Days of the Series
    * Members only
    * Pricing for Members and Non-members
    * Days when the Customers can sign up for the Series after the Series has started
      * This means that if a Series has started and you want to give Customers a chance to sign up for the Series after the first day of the Series, you can choose how many days after the start of the Series the Customers can do so
        * *Learn more in the Series Pricing article*
    * Prorated cost of Series
      * This means that you can set a different price for the remaining sessions in a Series if a Customer didn’t sign up for a Series on time. We strongly suggest incentivizing Customers to sign up for Series on time by increasing the Series remaining session cost.
      * For example, a 10-session Series costs $500 ($50 per session). For Customers who sign up after the Series has started, the cost is $60 per remaining session. By signing up for the entire Series in advance, customers not only secure their spot, they also receive a $10 discount relative to those joining after the Series has started.
        * Learn more with this [**Series Pricing**](/events/event-series/how-does-series-pricing-work.md) article.


---

# 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-do-i-edit-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.