> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Venues

> The rooms and stages of your event. A venue's perks are its entry gate, and its admit list follows the agenda automatically.

A venue is a place at your event — a main hall, a breakout room, a stage. Sessions on the [Agenda](/en/program/agenda) are held in venues, and a venue can carry an **entry gate**: bind perks to it and only holders may enter.

Find them under **Program & venue → Venue** in the event navigation.

## Create a venue

Click **Create venue** and name it (e.g. "Main hall A"). A venue is created **open to everyone**; its description and access rules are configured on its page.

## Who can enter

A venue's entry gate works exactly like a session's:

* **No perks selected** — the venue is open to everyone.
* **Any perks selected** — entry is restricted to attendees holding **at least one** of them. A ticket that grants the perk opens the door.

The venue's admit list has **two halves**:

1. **The venue's own perks** — what you toggle on the venue page. These apply to everyone entering, for any session.
2. **Perks required by the sessions held here** — honoured automatically. They appear in the list checked and locked, tagged *from the agenda*, and they follow the agenda: schedule a gated session into this venue and its perks join the admit list; move it out and they leave.

<Note>
  The agenda-derived half is **always computed live** from the sessions currently scheduled in the venue — it is never stored separately, so it can't drift out of date and can't be edited away by mistake. To change it, change the sessions.
</Note>

## Sessions held here

The venue page lists every session scheduled in it. You can **unassign** a session from here — the session stays on the agenda, just without a venue, and any admit-list perks it brought along follow it out. A session picks its venue on its own page.

<Note>
  The gate works both ways: a session held in a perk-restricted venue **inherits the venue's gate on top of its own** perks. Placing an open-to-all session in a VIP-only room makes it VIP-only.
</Note>

## Rules to know

* **Venues archive, never delete.** Sessions (and, in exhibition mode, booths) reference venues, so a venue is retired rather than removed.
* **An archived venue takes no new sessions**, but sessions already scheduled there keep it. Restore the venue to schedule into it again.
* **Gating lives in perks, not in ticket types.** The chain is ticket → perk → venue: to make a room VIP-only, bind a perk on the [Perks](/en/ticketing/perks) page to the VIP ticket, then select that perk on the venue.
* **Speakers get through the gate automatically** — assigning a speaker to a session in a gated venue grants their registration the required perks; see [Speakers](/en/program/speakers).
* **Venues double as exhibition halls.** If you enable the [Exhibition](/en/exhibition/overview) module, booths name a venue as their hall — "Hall A" is the same venue the agenda uses, so both sides speak of the same place.

<Tip>
  Model physical access from the venue side, session access from the agenda side. "Only workshop-pass holders may enter Room 3" is a venue gate; "this one session is VIP-only" is a session gate. They compose — you don't have to pick one.
</Tip>