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

# How do I create a bookable venue?

> Set up a sheet, room or coach's time that members can reserve from your website, with price, availability and approval.

<Note>
  **Must know**

  * **Bookings** is a CCM-parity feature (CCM had facilitycalendar ice reservations), so a migrating club normally has it. If **Registrations → Venues & Rentals** is missing, ask a superadmin.
  * One flat price per venue, optionally overridden per slot. Different prices for members and non-members are not available; per-member booking limits are (see the rental calendar settings).
  * A venue is public or private depending on the **Resource** you link it to. A private venue's bookings are hidden from everyone outside the club. See [Who can see a venue's bookings?](/club/bookings-and-todays-ice/who-can-see-a-venues-bookings).
  * **Require Approval** means "New bookings must be approved by an admin before they are confirmed. Pending bookings will not block time slots." — so two people can request the same slot until you approve one.
</Note>

<Steps>
  <Step title="Start a venue">
    Go to **Registrations → Venues & Rentals** ("Manage time-based bookings for spaces and staff.") and click **Add Booking**. The stepper has four steps: **General**, **Schedule**, **Requirements**, **Review**.
  </Step>

  <Step title="General">
    Enter **Name** (required), **Description**, an **Image**, the **Price** ("0.00 (free)" for no charge), a **Category** and whether to **Require Approval**.
  </Step>

  <Step title="Schedule">
    Set the **Date Range**, **Availability** (**Days of Week**, **Start Time**, **End Time**), the **Duration (minutes)** of one booking and a **Buffer (minutes)** between bookings.
  </Step>

  <Step title="Requirements">
    Choose the **Registration Mode**: **Member Registration** ("A specific member must be selected. Requirements below are enforced.") or **Open Registration** ("Any signed-in member can book. Requirements below are shown as display text only."). Under it, pick the **Resource** this venue is, or **No resource (follows Show sheets publicly)**. The line under the picker says whether everyone or only club members can see and book the venue. If the venue uses **Open Registration** but its resource is private, a warning says guests will not see it. Then add any of **Level**, **Capacity**, **Age**, **Gender**, **Membership**, **Waiver**, **Medical** or **File Upload**.
  </Step>

  <Step title="Review and create">
    Check the summary and create the venue. It appears in your site's registration catalogue, with its own page at `/bookings/{venue}`. A private venue appears there only for your club's members, their guardians and your staff.
  </Step>
</Steps>

Open the venue afterwards and use its configure sheet to change any of this; its **Requirements** tab has the same **Resource** picker. The sheet also has three extras: **Status** (Active / Inactive / Archived), **Ice sheet position (optional)** ("Ice-sheet venues map to league draw schedules by position — sheet 1 here is sheet 1 on the draw grid.") so its bookings show in the right Today's Ice column, and **Notification emails (optional)** ("Comma-separated — each address gets an email whenever this venue is booked.").

Members see their own reservations on **My ice bookings** (`/account/bookings` on your club site, the **Ice Bookings** button on My Account), upcoming and past.

**Related:** [Who can see a venue's bookings?](/club/bookings-and-todays-ice/who-can-see-a-venues-bookings) · [How do I add bookable slots and closures?](/club/bookings-and-todays-ice/how-do-i-add-bookable-slots-and-closures) · [What are booking types?](/club/bookings-and-todays-ice/what-are-booking-types) · [What are the rental calendar settings?](/club/bookings-and-todays-ice/what-are-the-rental-calendar-settings) · [How do I approve a booking?](/club/bookings-and-todays-ice/how-do-i-approve-a-booking)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.