> This page is for Product Documentation.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Locations and events

> Admission objects define what tickets are valid for. Admission objects can be either of either the location or an event type, and are defined in Ticket Admission.

* **Locations** are typically physical, such as a museum, while events are something within the location, such as a guided tour.
  With a few exceptions they work the same.
* **Events** admissions, for example, are valid for specific time, while location admissions are valid for any time within a timeframe.

You also have to set **Schedule type** in **Ticket Schedule** where you define when a location is accessible or when an event occurs:

* **Location** does not have any capacity control and do not require reservation.
* **Event** creates a reservation entry which is relevant for capacity control.

#### See also

* [<ins>NP Designer</ins>](/product/Attraction-ticket-ticket-designer)
* [<ins>Set up DIY printed tickets</ins>](/product/Attraction-ticket-diy-printed-ticket)
* [<ins>Set up tickets using the Ticket Setup Wizard</ins>](/product/Attraction-ticket-ticket-setup-wizard)
* [<ins>Admit an issued ticket</ins>](/product/Attraction-ticket-admit-issued-ticket)
* [<ins>Create prepaid tickets</ins>](/product/Attraction-ticket-create-prepaid)
* [<ins>Create postpaid tickets</ins>](/product/Attraction-ticket-create-postpaid)