> 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/edit-events/how-do-i-copy-an-event-onto-another-day.md). # How do I Copy an Event onto another day * If you have an Event built that you would like to replicate onto another day, where the two Events are not connected, you can Copy the Event! * By Copying an Event, all of the Event details will be replicated on another day. * An Admin will copy an Event if there is a recurring need for it (i.e. Open Plays every Thursday at 5 pm). To Copy an Event, the Admin will: * Navigate to the preferred Event * Click into this Event * Click the three vertical buttons * Select “Copy” * A new window will pop-up * Click + Event * Choose the future dates when the Event will also occur * (an Admin can also change the time, court, Listed/Unlisted, and Draft/Published) * Click Add Item * (an Admin can repeat these last two points as many times as they want) * Click Copy at the bottom of the pop-up window {% embed url="" %} * Other things to keep in mind when Copying an Event: * It is important to note that these Event Copies are not connected in any way other than being replicas of one another. Customer sign-ups, for example, are not across all Copied Events. * To learn more about connected Events, read about [**Series functionality here**](/events/event-series/updated-series-features.md). * When Copying an Event that has already been published, it's going to hold onto the format of the Event in that moment * So in the case of Copying an Event that is already published to Members, the Event will hold that feature and be visible to Members * It's best practice to Copy Events that are pending publish for both Members and Non-members * Make sure to Copy Events after you are done editing them. Copying an event will duplicate the Event in it’s current state. If you edit an Event after Copying it, the changes will only be reflected on the Event you edited, not all Copies of the Event. --- # 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/edit-events/how-do-i-copy-an-event-onto-another-day.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.