> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/booking/availability/resource-availability.md).

# Resource Availability

In Sesami, **availability belongs to resources** (not just “team members”). A resource can be:

* **Team member** (staff)
* **Room**
* **Chair / station**
* **Equipment / machinery**
* Any other capacity you need to schedule

> Note: In Sesami, **team members are a Resource type** (Resources can also be rooms, equipment, etc.).

## Set availability for a resource (team member, room, equipment, …)

{% stepper %}
{% step %}

#### Open Resources

Open **Sesami → Resources**.
{% endstep %}

{% step %}

#### Select the resource

Select the resource you want to edit\
(Example: a resource with type **Team member**).
{% endstep %}

{% step %}

#### Go to Availability

Go to the **Availability** section.
{% endstep %}

{% step %}

#### Edit availability

Click a date (or day) to open **Edit Availability**.
{% endstep %}

{% step %}

#### Add time intervals

Add time intervals (example: `8:00 am – 11:00 am`).
{% endstep %}

{% step %}

#### Apply to other days (optional)

Use **Apply to…** to copy the same schedule to other days (optional).
{% endstep %}

{% step %}

#### Save changes

Click **Save** (top-right) when you’re done.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Tips

* If you schedule *rooms* or *equipment* as resources, give them realistic availability windows so the calendar doesn’t offer impossible slots.
* If you use Google Calendar sync for team members, you can block time by creating “Busy” events (see the “Block off dates or times” guide).
  {% endhint %}

<figure><img src="/files/2FxVEbqkduCX4MiPTLzl" alt=""><figcaption></figcaption></figure>

## Availability Range

The Availability Range lets you control when a Resource can accept bookings by defining a booking window.

You can choose when bookings start and how far into the future customers can schedule appointments.

### Settings:

**From: Choose when bookings become available.**

* **Now** – Customers can book immediately.
* **Exact Date** – Bookings begin on a specific date.
* **Days into the Future** – Delay bookings by a set number of days.

**Example:** Setting **From → Days into the Future → 7** prevents customers from booking appointments within the next 7 days.<br>

**To:  Choose how far into the future customers can book.**

* **Indefinitely into the Future** – No booking limit.
* **Exact Date** – Stop accepting bookings after a specific date.
* **Days into the Future** – Allow bookings only within a rolling number of days.

**Example:** Setting **To → Days into the Future → 90** allows customers to book up to 90 days in advance.

{% hint style="info" %}
Notes: It controls the booking window, not the Resource's working hours.

To prevent [same-day](/booking/availability/same-day-bookings.md#disable-same-day-bookings) or last-minute bookings, use [Buffer time before the first appointment of the day ](/booking/availability/buffer-times.md#before-the-first-appointment-on-the-same-day)instead.
{% endhint %}

<figure><img src="/files/NHG3Ll4ymj0p5GGomgLe" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sesami.co/booking/availability/resource-availability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.