> 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/sign-up-for-an-event/how-to-schedule-events-to-auto-publish-and-copy-them.md). # How to Schedule Events to auto publish (and Copy them) * An Admin can Schedule an Event to be published at a future date. This Event can also be published to Members before Non-members (thereby mirroring any preferred [**Booking Horizon**](https://help.podplay.app/en/articles/831745)) * To do so: * Create an Event * Fill in all necessary and desired information about the Event * Click on the drop-down button Publishing status, currently labeled Draft * Select Schedule * Choose the number of days in advance the Event will be published from the day of the Event * You can choose the publish day, when it will become public, for both Members and Non-members. * If the Event is two weeks from today, and you Schedule the Event to publish 7 days before, the Event will be published 1 week from today. * 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 * Check the box labeled publish * Click Save * * NOTE: if an Admin would like to copy a Scheduled Event multiple times as a way to build out programming for the Club, they can do so and the suggested best practice is to: * Copy Events that are Scheduled to publish IF the Event has not yet been published for Members or Non-members. * If an Admin Copies an Event that has published for Members and is still Scheduled for Non-members, the Copy will include the status of the Event. Meaning, it will copy an Event that is currently published for Members and Scheduled for Non-members. * To learn more, read about [**How to Copy an Event**](/events/edit-events/how-do-i-copy-an-event-onto-another-day.md). --- # 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/sign-up-for-an-event/how-to-schedule-events-to-auto-publish-and-copy-them.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.