> 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/create-an-event/templates/copy-events.md).

# Copy Events

### Templates and Repeating Events

PodPlay does not have a dedicated template system, but Admins can replicate Events using the Copy feature or build repeating programming using the Schedule feature.

#### Copy an Event

Copying creates an independent duplicate of an Event on a new date. The two Events are not connected — Customer signups, for example, do not carry over.

To copy an Event:

1. Navigate to the Event in the Dashboard
2. Click into the Event
3. Click the three vertical dots
4. Select **Copy**
5. In the pop-up window, click **+ Event**
6. Choose the future date(s) for the copy (you can also adjust time, court, visibility, and publish status)
7. Click **Add Item** — repeat to add more copies
8. Click **Copy**

Best practices:

* Copy Events before editing them. Copies reflect the Event's state at the moment of copying — changes made after copying only apply to the Event you edited.
* Copy Events that are still in Draft or Scheduled status (not yet published to Members or Non-members). Copying a partially published Event carries that published state to all copies.
* For connected Events where Customers sign up for all sessions at once, use a \[Series] instead.

#### Schedule an Event to auto-publish

Admins can set an Event to publish automatically at a future date, with the option to publish to Members before Non-members.

To schedule an Event:

1. Create the Event and fill in all details
2. Click the **Publishing status** dropdown (labeled **Draft**)
3. Select **Schedule**
4. Enter the number of days before the Event date when it should publish — set separately for Members and Non-members
5. Review the calculated publish date shown below the input
6. Check **Publish** and click **Save**

> **Example:** If an Event is two weeks away and you schedule it to publish 7 days in advance, it will become visible one week from today.

#### Move or reschedule an Event

To change the time or date of an existing Event:

1. Find the Event in the Dashboard
2. Click into the Event
3. Click the three vertical dots in the bottom left of the side panel
4. Select **Reschedule**
5. Choose the new time or date
6. Click **Save**, then confirm

> **Note:** PodPlay does not send automatic notifications to signed-up Customers when an Event is rescheduled. To notify Customers, either cancel the Event and create a new one, or export the Attendee list and contact them directly. See \[Exporting Attendee List].

#### Generate a link for an Event

Admins can generate links to share Events directly with specific Customers, without requiring them to search the App.

From inside any Reservation or Event, click the three vertical dots in the bottom left of the side panel. The available options depend on the Event's status:

**Draft Event:**

* **Generate guest link** (not as participant) — Customer joins but does not count toward attendee quota
* **Generate signup link** — Customer joins normally
* **Preview draft** — lets the Admin view the Event from the Customer's perspective before publishing

**Published Event:**

* **Generate guest link** (not as participant)
* **Generate signup link**
* **Open in web app** — view the live public-facing Event page


---

# 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/create-an-event/templates/copy-events.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.