> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/event-details-and-location.md).

# Event Details and Location

Set an Event Page's name, description, schedule, location, location disclosure, and ticket delivery in the Event panel of the Page Builder.

The **Event** panel holds the basic details of your event: its name, schedule, location, when attendees learn the location, and how tickets are delivered. You'll find it in the Page Builder under **Event > Event** on Event Pages. This article covers each section of the panel.

## Before You Begin

New Event Pages start with an event named "New event," scheduled for today from 6 PM to 8 PM Eastern, and a free General Admission ticket. Update these before you share the page.

## Open the Event Panel

To open the Event panel:

1. Go to **Action Pages > Pages**.
2. Hover over the Event Page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Event > Event**.

## Name and Description

* **Event name:** Required.
* **Description:** Required. Shown on the public Event Page.

## Schedule

Enter the **Start date**, **Start time**, **End time** and **End date**, and choose the **Time zone**. For an all-day event, check **All day**.

## Event Location

Choose a **Location type**:

* **In person:** Enter the address. Start typing in **Address line 1** to search verified addresses.
* **Online:** Enter the **Conference URL**, including http\:// or https\://.
* **Hybrid:** Enter both the address and the Conference URL.

An address is required unless the event is online.

## Location Disclosure

**Disclosure** controls when attendees see the location:

* **In receipt (not on page):** The location is shared in the receipt after a purchase.
* **Email (on specific date and time):** Enter a **Release date** and **Release time**. Attendees get the location by email at that time.
* **Show on page:** The location shows on the public Event Page. This option isn't available for online events.

{% hint style="info" %}
After the location email has gone out, the Disclosure settings are locked. Attendees who buy tickets after that receive the location email when they purchase.
{% endhint %}

## Ticket Delivery and Ticketing Rules

* **Send ticket with receipt email?:** Choose **Yes** to attach tickets to the receipt, or **No** to send the receipt without them.
* **Require a donation for free tickets:** When checked, supporters must add a donation to claim a free ticket. This works with **Accept donations for all ticket purchase types** in [Giving](/action-pages/page-builder/giving-amounts-and-frequencies.md).

When you're done, click **Save**.

## Related Articles

* [Event Tickets and Promo Codes](/action-pages/page-builder/event-tickets-and-promo-codes.md)
* [Manage Events](/action-pages/action-page-basics/manage-events.md)
* [Page Builder Overview](/action-pages/page-builder.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/action-pages/page-builder/event-details-and-location.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.