---
title: "Booking Creation Settings"
description: "Choose the status new bookings and booking requests start in, how the date picker behaves when staff create a rental, whether pickup and return times can be typed in, whether the booking form starts from items or from dates, and whether units can be scanned in at creation."
canonical_url: "https://requiply.com/docs/en/guides/settings/bookings/booking-creation"
---
# Booking Creation Settings

> Choose the status new bookings and booking requests start in, how the date picker behaves when staff create a rental, whether pickup and return times can be typed in, whether the booking form starts from items or from dates, and whether units can be scanned in at creation.

The **Booking Creation Settings** page is where you choose how date and time pickers behave whenever a booking is created inside Requiply. It controls the default date picker style used across the app — both in internal booking flows and in customer-facing booking experiences — so bookings are always created with a consistent, predictable interface. It also sets the status a new booking starts in, the status a booking request arrives in, whether the staff booking form starts from items or from dates, and whether staff can scan specific units into a booking while creating it.

You can find this page under **Settings → Bookings settings → Booking Creation Settings** ([`/settings/reservations/booking-creation`](https://app.requiply.com/settings/reservations/booking-creation)).

<note>

These are organization-wide settings. The date picker style and the two starting statuses apply everywhere bookings are created in your Requiply workspace. **Allow assigning units on creation** only affects the staff [Add booking](https://requiply.com/docs/en/guides/bookings/add-booking/scanning-and-pinning#assigning-units-on-creation) form and booking creation in the mobile app.

</note>

## Why this page matters

Booking creation is the heart of Requiply. The date picker that appears on the booking form determines how staff and customers select booking dates and times — whether they pick a single date with separate time fields, or a date range with separate times.

Choosing the right picker style helps your team and your customers move through booking creation faster and with fewer mistakes. The selection here is reused across:

- Internal booking creation in the web app and the mobile app
- The [client portal](https://requiply.com/docs/en/guides/online-booking/booking-flow) your customers book on
- Any other place in Requiply where a booking date picker appears

The two status fields decide where a booking enters your [status flow](https://requiply.com/docs/en/guides/settings/bookings/statuses): **Default status for new bookings** for bookings your team makes, and **Status for booking requests** for requests that wait for approval.

The **Allow assigning units on creation** toggle serves teams that hand over exactly the unit a customer asked for. Staff scan the unit while creating the booking, and it is pinned to the booking from the start instead of being chosen later.

## Who can use this page

This page lives inside the Settings area, so it is intended for users who manage organization configuration (typically administrators).

The page itself does not show plan limits, paid add-ons, or upgrade prompts — it is a standard settings screen. Access is governed by the surrounding settings layout and authentication middleware rather than by per-feature billing rules.

## What you'll see

The page is split into two halves:

**Left side: settings form**

- A page heading: **Booking creation**, with two sections: **Defaults** and **Permissions**.
- Under **Defaults**, a **Booking dates picker** dropdown, with a small question-mark icon next to it. Hovering the icon shows a tooltip explaining: *"This date picker will be the default for all places in the app for booking creation."*
- Under **Defaults**, a **Start from** dropdown with the options **Start from items** and **Start from dates**. See [Choosing where the booking form starts](#choosing-where-the-booking-form-starts).
- Under **Defaults**, a **Default status for new bookings** dropdown and a **Status for booking requests** dropdown, each listing your statuses with their colors and each with a question-mark tooltip. See [Choosing the starting statuses](#choosing-the-starting-statuses).
- Under **Permissions**, an **Allow assigning units on creation** toggle, off by default. Its question-mark icon shows the tooltip: *"Adds a field to the booking form where staff can scan or type a unit code. The scanned unit is pinned to the booking and its product line is added automatically. Members also need the "Allow assigning units on booking creation" permission in their group."*
- **Cancel** and **Save** buttons at the bottom of the form. **Save** stays disabled until you change a dropdown or the toggle.

**Right side: live preview**

- A heading: **Settings preview**, with the subtitle *"Date picker preview"*.
- A working preview of the date picker using the currently selected option, populated with a sample equipment item ("Preview equipment") so you can see exactly how the picker will look and behave before saving.

The preview follows your own permissions. If your [permission group](https://requiply.com/docs/en/guides/settings/organization/accounts/permission-groups) has **Allow booking outside of working hours**, the preview also lets you pick closed days and shows times outside the working schedule as orange pills, exactly as your own Add booking form does. Members without that permission see working hours only.

While the page is loading or saving, the entire view is blocked with a full-screen overlay so changes cannot be made mid-request.

## Empty state

This page does not have an empty state. Every organization gets its booking creation settings the moment it is created: **Inline dates with separate times**, **Start from items**, **New** as the default status, **Request** as the request status, and **Allow assigning units on creation** switched off. The preview reflects those values until you change them.

## Main actions

### Choosing the date picker style

The **Booking dates picker** dropdown offers three options:

<table>
<thead>
  <tr>
    <th>
      Option
    </th>
    
    <th>
      How dates and times are picked
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Inline dates with separate times
      </strong>
    </td>
    
    <td>
      An inline calendar for the start and end date, with pickup and return times chosen from half-hour pills. This is the default.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Inline one date with separate times
      </strong>
    </td>
    
    <td>
      The same, for a single day: one date on the calendar, pickup and return times from pills.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Inline dates with typed times
      </strong>
    </td>
    
    <td>
      The same calendar, but pickup and return are typed into a date field and a time field instead of picked from pills.
    </td>
  </tr>
</tbody>
</table>

Selecting an option immediately updates the preview on the right so you can try it out before committing.

#### Typed pickup and return

**Inline dates with typed times** suits teams that already know the exact handover time and find pills slow, and anyone who needs a time the pills do not offer: typed times accept any minute, while pills step in half hours.

The calendar above the fields behaves as it always does, fully booked days struck through in red and partly booked days in orange, and the fields are **Pickup date and time** and **Return date and time**, each a date box next to a time box. Under each pair sits the window it will accept, for example *Available from 09:00 to 18:00*, and the return fields stay disabled until a pickup date exists. The date format follows your [localization settings](https://requiply.com/docs/en/guides/settings/organization/localization).

<figure>

![The typed date picker in dark mode. Two months, September and October 2026, sit side by side with the 22nd to the 24th filled in green as the selected range and today outlined. Below them, Pickup date and time holds the date 09/22/2026 next to the time 10:00, and Return date and time holds 09/24/2026 next to 17:30. Each pair is followed by the line Available from 00:00 to 23:59](https://requiply.com/docs/assets/settings/bookings/booking-creation/typed-times.png)<figcaption>

Dates are still picked on the calendar; the fields underneath take the exact times. This member may book outside working hours, so both windows open to the whole day.

</figcaption>
</figure>

Entries are checked as they are completed, and a rejected one leaves the previous value in place:

<table>
<thead>
  <tr>
    <th>
      Message
    </th>
    
    <th>
      What it means
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <em>
        Enter a valid date
      </em>
      
       / <em>
        Enter a valid time
      </em>
    </td>
    
    <td>
      The text is complete but not a real date or time.
    </td>
  </tr>
  
  <tr>
    <td>
      <em>
        This date is not available for booking
      </em>
    </td>
    
    <td>
      The date is closed, in the past, or fully booked for the selected items.
    </td>
  </tr>
  
  <tr>
    <td>
      <em>
        Return must be on or after the pickup date
      </em>
    </td>
    
    <td>
      The return date is earlier than the pickup date.
    </td>
  </tr>
  
  <tr>
    <td>
      <em>
        Choose a time between {min} and {max}
      </em>
    </td>
    
    <td>
      The time falls outside the window the fields offer.
    </td>
  </tr>
</tbody>
</table>

Members whose group has **Allow booking outside of working hours** may type times outside the schedule, exactly as they may pick orange pills in the other two modes.

<note>

Typed entry is for your own team. On the [client portal](https://requiply.com/docs/en/guides/online-booking/booking-flow) this option behaves like **Inline dates with separate times**, so customers keep the calendar and the time pills.

</note>

### Choosing where the booking form starts

Staff can create a booking in two ways: pick the items first and then see which dates they are free, or pick the dates first and then see which items are free. **Start from** decides which of the two the booking form opens with:

<table>
<thead>
  <tr>
    <th>
      Option
    </th>
    
    <th>
      The booking form opens with
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Start from items
      </strong>
    </td>
    
    <td>
      The item selector first, then the dates. This is the default.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Start from dates
      </strong>
    </td>
    
    <td>
      The dates first, then the items that are free on them.
    </td>
  </tr>
</tbody>
</table>

The question-mark icon explains: *"The booking form in the web and mobile apps opens with this option selected. Staff can still switch to the other one while creating a booking."*

<figure>

![The Booking creation settings page. Under Defaults, Booking dates picker is set to Inline dates with separate times, and the Start from dropdown is open with the options Start from items and Start from dates. A date picker preview is on the right.](https://requiply.com/docs/assets/settings/bookings/booking-creation/start-from.png)<figcaption>

**Start from** sits under **Defaults**, next to the date picker style.

</figcaption>
</figure>

- On [Add booking](https://requiply.com/docs/en/guides/bookings/add-booking) in the web app, the **Start from items** / **Start from dates** switch at the top is preselected with this option. Staff can still switch.
- In the **mobile app**, a new booking skips the *How do you want to start?* question and opens directly in this mode. The question still appears when staff go back from the first step or clear the draft, so they can pick the other mode. See [Items first or dates first](https://requiply.com/docs/en/guides/mobile-app/bookings#items-first-or-dates-first).

A team that mostly books by date, such as a studio or a venue, picks **Start from dates**. A team that builds orders around the equipment the client asks for keeps **Start from items**.

### Choosing the starting statuses

Two dropdowns under **Defaults** decide which status a booking starts in. Both list every status of your organization, shown with its color, and both are required.

<figure>

![The Booking creation settings page. Under Defaults, below Booking dates picker and Start from, the Default status for new bookings dropdown shows a cyan dot and New, and the Status for booking requests dropdown shows a yellow dot and Request, each with a question-mark icon on the right. The Permissions section with the Allow assigning units on creation toggle follows below](https://requiply.com/docs/assets/settings/bookings/booking-creation/status-defaults.png)<figcaption>

The two starting statuses sit under **Defaults**. Every organization starts with *New* and *Request* here.

</figcaption>
</figure>

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      Tooltip
    </th>
    
    <th>
      Applies to
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Default status for new bookings
      </strong>
    </td>
    
    <td>
      <em>
        Bookings that staff create in the web app, the mobile app, imports, the API or the AI assistant start in this status.
      </em>
    </td>
    
    <td>
      <a href="https://requiply.com/docs/en/guides/bookings/add-booking">
        Add booking
      </a>
      
       in the web app, booking creation in the mobile app, bookings created through the API or the <a href="https://requiply.com/docs/en/developers/typescript-sdk/bookings">
        TypeScript SDK
      </a>
      
       with a secret key, and checkouts on the <a href="https://requiply.com/docs/en/guides/online-booking/booking-flow#what-happens-in-requiply">
        client portal
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Status for booking requests
      </strong>
    </td>
    
    <td>
      <em>
        Bookings that clients send as requests from the booking page, the client portal or the chat start in this status. Staff approve a request by moving it to another status.
      </em>
    </td>
    
    <td>
      Bookings from the portal's <a href="https://requiply.com/docs/en/guides/online-booking/booking-assistant#booking-through-the-assistant">
        booking assistant
      </a>
      
      , the <a href="https://requiply.com/docs/en/guides/online-booking/web-widget">
        AI web widget
      </a>
      
      , outside AI assistants connected over <a href="https://requiply.com/docs/en/ai/mcp">
        MCP
      </a>
      
      , and API calls made with <code>
        asRequest: true
      </code>
      
      .
    </td>
  </tr>
</tbody>
</table>

What else follows these two settings:

- **Sidebar counters.** The **Manage bookings** entry in the sidebar shows how many bookings are in your default status and, next to it, how many are in your request status, each counter in its status's color.
- **Dashboard money.** Bookings in the request status owe nothing yet, so they are left out of **Outstanding** on the [Dashboard](https://requiply.com/docs/en/guides/reports/dashboard).
- **Approving a request.** Moving a booking out of the request status is what approves it.
- **The client portal progress bar.** A booking that is still in the request status starts its [progress bar](https://requiply.com/docs/en/guides/online-booking/customer-accounts#a-single-booking) there; every other booking starts it at the default status.
- **New workflows.** A new *Status reached* [workflow](https://requiply.com/docs/en/guides/automations/workflows) preselects the default status.

<note>

**Requests and stock.** A request holds no stock only while its status has **Release availability** switched on, as the default *Request* status does. If you point **Status for booking requests** at a status that holds stock, every request reserves its items the moment it arrives. See [Booking statuses](https://requiply.com/docs/en/guides/settings/bookings/statuses#adding-a-status).

</note>

A status chosen here cannot be deleted. The delete dialog on [Booking statuses](https://requiply.com/docs/en/guides/settings/bookings/statuses#deleting-a-status) says so and points back to this page.

### Allowing units to be assigned on creation

Switch on **Allow assigning units on creation** to let staff pin specific units on [Add booking](https://requiply.com/docs/en/guides/bookings/add-booking/scanning-and-pinning#assigning-units-on-creation). There is no separate field for it: staff type a unit code or SKU into the **Booking items** search (*Name, SKU or unit code*), or scan a label with a handheld scanner anywhere on the page, and the unit is pinned to the booking. If the unit's product is not on the booking yet, the product line is added automatically. With the toggle off, the same code only adds the unit's product, without pinning a unit.

The same toggle makes **Scan** and **Enter code** on the **Inventory** step of booking creation in the mobile app pin the scanned unit. See [In the mobile app](https://requiply.com/docs/en/guides/bookings/add-booking/scanning-and-pinning#in-the-mobile-app) and [Adding items to a booking](https://requiply.com/docs/en/guides/mobile-app/scanning#adding-items-to-a-booking).

Pinned units are assigned to the booking the moment it is created, in both **Unit assignment** modes under [Features](https://requiply.com/docs/en/guides/settings/organization/features#enable-pickup-return-checklists). Any remaining quantity follows that option as usual: assigned right away with **Assign units at booking**, or during the [pickup checklist](https://requiply.com/docs/en/guides/bookings/checklists/pickup#assigning-units-at-pickup) with **Assign units at pickup**.

The toggle alone does not show the field to anyone. Each member also needs **Allow assigning units on booking creation** in their [permission group](https://requiply.com/docs/en/guides/settings/organization/accounts/permission-groups). That permission sits in the **Booking creation** section, is on for **Administrators** by default, and is off for new groups. The server checks both the toggle and the permission whenever a booking with pinned units is created.

### Saving changes

Click **Save** to store the dropdowns and the toggle together. On success, a toast appears: *"Booking creation settings have been saved successfully."* If the save fails, an error toast appears and the form remains editable.

### Cancelling changes

Click **Cancel** to discard unsaved changes and revert the dropdowns and the toggle to their last saved values. This does not navigate away from the page.

## Forms and fields

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      Meaning
    </th>
    
    <th>
      Required
    </th>
    
    <th>
      Notes
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Booking dates picker
      </strong>
    </td>
    
    <td>
      The default date picker style used everywhere bookings are created.
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Must be one of the three allowed options. Validation rejects anything else.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Start from
      </strong>
    </td>
    
    <td>
      Whether the web and mobile booking forms open with the items or with the dates.
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      <strong>
        Start from items
      </strong>
      
       (default) or <strong>
        Start from dates
      </strong>
      
      . Staff can switch while creating a booking.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Default status for new bookings
      </strong>
    </td>
    
    <td>
      The status a booking your team creates starts in.
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Any of your statuses. <strong>
        New
      </strong>
      
       by default. Left empty, the form shows <em>
        Choose a status
      </em>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Status for booking requests
      </strong>
    </td>
    
    <td>
      The status a booking request arrives in, waiting for approval.
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Any of your statuses. <strong>
        Request
      </strong>
      
       by default. Left empty, the form shows <em>
        Choose a status
      </em>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Allow assigning units on creation
      </strong>
    </td>
    
    <td>
      Lets members with the matching permission pin units on Add booking by entering or scanning a unit code.
    </td>
    
    <td>
      No
    </td>
    
    <td>
      Off by default. Members also need <strong>
        Allow assigning units on booking creation
      </strong>
      
      .
    </td>
  </tr>
</tbody>
</table>

The **Save** button is disabled until a dropdown or the toggle differs from its saved value, so you cannot save a no-op.

## Billing, plans, and limits

This page has no plan limits, paid add-ons, or upgrade prompts. It is a standard configuration screen available to organizations using Requiply's booking features.

## How this page connects to the rest of Requiply

<table>
<thead>
  <tr>
    <th>
      Feature
    </th>
    
    <th>
      How this page affects it
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Internal booking creation
      </strong>
    </td>
    
    <td>
      The chosen picker becomes the default date/time selector when staff create a booking from the admin app.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://requiply.com/docs/en/guides/online-booking/booking-flow">
        <strong>
          Client portal
        </strong>
      </a>
    </td>
    
    <td>
      Customers get the same picker, single date or date range. <strong>
        Inline dates with typed times
      </strong>
      
       is a staff option: the portal falls back to the range picker with time pills.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Booking duration settings
      </strong>
    </td>
    
    <td>
      Booking creation works alongside duration rules (minimum duration, start-date buffers). The picker selected here is the surface where those rules are applied during date selection.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Date and time settings
      </strong>
    </td>
    
    <td>
      Localization and time-zone settings from the organization's date/time configuration are loaded together with this page so the preview renders with the correct localized format.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        <a href="https://requiply.com/docs/en/guides/bookings/add-booking/scanning-and-pinning#assigning-units-on-creation">
          Add booking
        </a>
      </strong>
    </td>
    
    <td>
      New bookings start in the <strong>
        Default status for new bookings
      </strong>
      
      . With <strong>
        Allow assigning units on creation
      </strong>
      
       on, members with the permission pin units by entering or scanning their codes.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        <a href="https://requiply.com/docs/en/guides/settings/bookings/statuses">
          Booking statuses
        </a>
      </strong>
    </td>
    
    <td>
      The two starting statuses are picked from there, and a status chosen here cannot be deleted.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        <a href="https://requiply.com/docs/en/guides/online-booking/booking-assistant">
          Booking assistant
        </a>
      </strong>
      
       and <strong>
        <a href="https://requiply.com/docs/en/ai/mcp">
          AI integrations
        </a>
      </strong>
    </td>
    
    <td>
      Requests they create arrive in the <strong>
        Status for booking requests
      </strong>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        <a href="https://requiply.com/docs/en/guides/settings/organization/accounts/permission-groups">
          Permission groups
        </a>
      </strong>
    </td>
    
    <td>
      <strong>
        Allow assigning units on booking creation
      </strong>
      
       decides which members can pin units. <strong>
        Allow booking outside of working hours
      </strong>
      
       changes what the preview picker offers you.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        <a href="https://requiply.com/docs/en/guides/bookings/checklists/pickup#assigning-units-at-pickup">
          Pickup checklists
        </a>
      </strong>
    </td>
    
    <td>
      Units pinned at creation are already assigned, so a pickup checklist in <em>
        Assign units at pickup
      </em>
      
       mode only asks for the remaining quantity.
    </td>
  </tr>
</tbody>
</table>

## Common scenarios

### Setting up booking creation for a new organization

When first configuring Requiply, open this page, try both options in the live preview, and pick the one that best matches how your team books work — single-day bookings versus multi-day rentals.

### Switching from multi-day to single-day bookings (or vice versa)

If your business model changes — for example, moving from equipment rentals (date ranges) to appointments (single date) — update the picker here so all booking surfaces in the app match the new flow.

### Verifying the experience before saving

Use the preview panel on the right to see exactly what staff and customers will see. Because the preview is interactive and uses a sample item, you can confirm the picker behaves as expected before clicking **Save**. With **Inline dates with typed times** this is also where you check that the typed format matches the one your team is used to: the date format follows your [localization settings](https://requiply.com/docs/en/guides/settings/organization/localization).

### Renaming "New" and "Request" to your own words

You do not need this page for that. Rename the statuses themselves under [Booking statuses](https://app.requiply.com/settings/reservations/statuses): the settings here point at the status, not at its name, so they follow the rename.

### Making staff bookings start confirmed

A team that confirms everything on the phone before creating the booking can skip *New*. Open this page, set **Default status for new bookings** to **Confirmed**, and click **Save**. Bookings created from then on start in *Confirmed*; bookings already in *New* stay there until someone moves them.

### Sending requests to a status of your own

Create a status such as *Awaiting approval* under [Booking statuses](https://app.requiply.com/settings/reservations/statuses), with lifecycle **Active** and **Release availability** on so requests hold no stock, and give it transitions to the statuses your team approves into. Then set **Status for booking requests** to it here and click **Save**.

### A studio that books by date

Clients call asking "are you free on Saturday?", not for a specific item. Set **Start from** to **Start from dates** and click **Save**. The booking form on the web and in the mobile app now opens on the calendar, and staff see which items are free once the dates are picked.

### Letting counter staff scan units while booking

Switch on **Allow assigning units on creation** and click **Save**. Then open [Permission groups](https://requiply.com/docs/en/guides/settings/organization/accounts/permission-groups), turn on **Allow assigning units on booking creation** for the counter staff's group, and save the group. The next time those members open [Add booking](https://app.requiply.com/reservations/add), a unit code typed into the **Booking items** search or scanned with a handheld scanner pins that unit, and it is listed under **Pinned units**.

### An administrator cannot pin units

Open this page and check **Allow assigning units on creation**. The matching permission is on for **Administrators** by default, so when a scanned unit code only adds the product, the toggle is almost always off. Switch it on and click **Save**. Then reload [Add booking](https://app.requiply.com/reservations/add) on the web, or close and reopen the mobile app. If units are still not pinned, work through [the checklist](https://requiply.com/docs/en/guides/bookings/add-booking/scanning-and-pinning#when-unit-pinning-or-the-scan-buttons-are-missing).

## Tips and cautions

<tip>

**Tip:** Use the live preview before saving. The picker on the right reacts immediately to your selection, so you can compare both styles side-by-side without committing.

</tip>

<warning>

**Heads up:** This setting is organization-wide and applies to every place bookings are created, the client portal included. Changing it after your team is used to one style may briefly affect their workflow until they adjust.

</warning>

<warning>

**Heads up:** Changing a starting status only affects bookings created afterwards. Existing bookings keep their status, and a booking that was a request under the old request status is no longer counted as one.

</warning>

<warning>

**Heads up:** Turning on **Allow assigning units on creation** is not enough by itself. Members can only pin units when their group also has **Allow assigning units on booking creation**. Administrators have it by default; other groups need it switched on.

It also works the other way round: the permission alone does nothing. Administrators have it from the start, but their scanned or typed unit codes only pin units, on the web and in the mobile app, once this toggle is on and saved.

</warning>

<note>

**Tip:** If the preview shows orange time pills, that is your own **Allow booking outside of working hours** permission at work, not a setting on this page. Customers on the [client portal](https://requiply.com/docs/en/guides/online-booking) always see working hours only.

</note>


## Sitemap

See the full [sitemap](https://requiply.com/docs/sitemap.md) for all pages.