> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-capture/events/details-and-settings.md).
# Details and Settings
Event settings control the key details of your event including dates, capacity, registration behaviour, access controls, and pricing.
To access event settings, go to the Event Dashboard and click **Edit Details and Settings**.
### Event Date and Close Date
Set the date of the event so you can schedule triggered emails relative to it. For example, send a reminder the day before and a follow-up survey link the day after.
Set the date registrations close. Anyone visiting the event link after this date will see the Registrations Closed page. You can edit the content of this page under Confirmation Pages.
***
### Capacity
Set a total number of places for your event. Once the limit is reached, new visitors will see the Maximum Capacity Reached page. Cancelling a registration frees up a place.
***
### Additional Registrations
You can allow multiple registrations per form submission in two ways.
**Named places** require individual details for each registrant. Add Person and Remove Person buttons appear on the form, and you can control which fields appear for additional registrants when editing your form fields.
**Anonymous tickets** allow one person to order multiple tickets without entering details for each. A Number of Tickets field is added to the form automatically.
The additional registration settings that are available in event details and settings.
***
### Single Registration Per Respondent
When enabled, each person can only register once. For anonymous registrations via a website link, cookies are used to track this. For contacts arriving via a UbiQuity mailout, personalised links are used instead.
Anyone who has already registered and tries to register again will see the Already Registered page, which can be edited under Confirmation Pages.
***
### Confirmation Status
Each registration has a status of Unconfirmed, Confirmed, or Cancelled. By default new registrations are marked as Unconfirmed. You can change this default to automatically confirm all new registrations.
A confirmed registration counts against the total capacity. An unconfirmed registration does not.
For paid events, registrations also have a Paid or Unpaid status. Payments are made via invoices, and will be marked as Unpaid until you update them manually.
***
### Event Access
**Accessible to anyone with the link** is the default open access setting.
**Restrict access to allowed IP addresses** limits access to the IP addresses configured for your UbiQuity account. Contact UbiQuity to manage this list.
**Restrict access to a custom IP address whitelist** lets you specify your own list of permitted IP addresses.
**Restrict to database contacts only** means anonymous links will show the Inactive page. Only personalised links from UbiQuity mailouts will work.
***
### Registrant Name Template
As registrations come in, you can view them in a list. To control what information appears in that list, add form fields to the **Registrant Name Template** in Edit Event Settings using the merge field selector.
***
### Pricing
You can set a price for your event or leave it free.
If any pricing or paid items are present, a payment page will appear as part of the registration process. This page can be customised under Layouts.
Payments can be taken via invoice, and a text box will appear for the registrant to enter their billing details. You will need to download these and send invoices manually, then update the registration status to Paid once payment is received.
The pricing options that are available in event details and settings.
---
# 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.ubiquity.co.nz/documentation/data-capture/events/details-and-settings.md?ask=&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.
