> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/resource-booking/resource-booking-overview.md).

# What is resource booking?

Resource booking is the part of the Kenai dashboard where you reserve a shared workplace resource before you arrive. Different resources are configured to match the setup at each location, so you book against what your site actually offers and facilities teams get clear visibility of how the space is used.

## Resource types

The resource types available depend on how your location is configured. The dashboard groups them on the **RESOURCES** card:

* **Desk**: on-demand desk reservations for hot-desking environments. Workstations are booked by floor or neighbourhood before arrival, with half-day, full-day, or recurring slots for hybrid work.
* **IT Service Locker**: self-service lockers for collecting, returning, or swapping IT equipment such as laptops and peripherals. Locker slots are booked in advance for collection on arrival, removing help desk queues.
* **Parking**: parking allocation across a location for staff and visitors. Resources are classified by type, including disabled bays, EV spots, and motorcycle parking. Cancelled bookings reopen the space, and usage reporting measures demand.
* **Meeting & Event Spaces**: boardrooms, huddle spaces, and video-conferencing suites reserved by capacity, location, or equipment. Add-ons such as catering and AV setup can be included, no-show bookings are released automatically, and recurring reservations are supported.

{% hint style="info" %}
**Note**: these resource types are examples. A site can set up any resources it needs, each with its own booking fields and rules.
{% endhint %}

## How it fits together

Each location is different, so **Resource Groups** tailor the booking setup per location, giving each one exactly what it requires. Every resource page exposes use-case-specific data fields so the booking matches each scenario: desk pages capture floor and pod, locker pages capture a fault description, meeting pages capture venue and catering needs, and parking pages capture vehicle and document details.

Once resources are configured, a **RESOURCES** summary tile appears on the dashboard. **Bookings today** shows the total number of upcoming reservations, and the per-resource tiles (such as **DESK TODAY** and **PARKING THIS WEEK**) summarise activity. All reports include your own bookings.

Open a resource from the **Resources** menu in the sidebar to reach its detail views, organised into tabs:

* **Logs**: usage logs for the resource.
* **Bookings**: upcoming bookings reports.
* **Analytics**: utilisation and pattern analytics, such as bay utilisation over time.

{% hint style="info" %}
**Note**: the tabs and views you can see depend on your assigned access role.
{% endhint %}

{% embed url="<https://app.arcade.software/share/2e2uDBUuSX1ja5evjEil?embed=true>" %}
Walkthrough: a tour of the Resource Booking feature and the per-resource Logs, Bookings, and Analytics views.
{% endembed %}

Ready to reserve something? See [Book a resource](/command-centre/visitor-management-powered-by-kenai/resource-booking/book-a-resource.md).

## Related

* [Book a resource](/command-centre/visitor-management-powered-by-kenai/resource-booking/book-a-resource.md)


---

# 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.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/resource-booking/resource-booking-overview.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.