> 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-schedule-a-series-to-publish-to-members-before-non-members.md). # How do I Schedule a Series to publish to Members before Non-members * To Schedule a Series to be visible to Members before Non-members, you follow a similar process to [**auto-publishing an Event**](/events/sign-up-for-an-event/how-to-schedule-events-to-auto-publish-and-copy-them.md). * To do so: * Create an Event * Click on the Create a Series button at the top right of the side panel * Fill in all necessary and desired information about the Event * Click on the Visibility options drawer * Select Scheduled * Choose the number of days in advance the Event will be published for Members and for Non-members * Notice the date it will publish below the number of days you have chosen * Verify this is when you want to have the Event published * Click the Publish button at the bottom left of the side panel * Click the Book and Publish blue button on the bottom right of the side panel * Add any additional Events in the Series {% embed url="" %} --- # 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-schedule-a-series-to-publish-to-members-before-non-members.md?ask=&goal= ``` `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.