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

# Booking settings

> What your organisation books at all, what each kind of booking may hold and be charged to, and the rate cards that price a booking.

Configuration for [Bookings](/property/bookings): what's bookable, what a kind of booking means, and
what it costs.

## What this organisation books at all

The product can reserve five kinds of thing — assets, tools, parts, places and people. Tick the ones
your organisation actually books.

<Note>
  Nothing ticked means all five, which is what every organisation books until this is opened. A yard
  that only hires out plant ticks just **Assets**, and the other four stop being offered anywhere in
  the product — the new-booking form, every tab of the availability calendar, and the panel below.
  Anything already booked stays booked; this only refuses the next one.
</Note>

## Booking types

A booking type is a kind of booking — a room booking, an equipment hire, a secondment — and each one
has its own **name**, **code**, and whether it **requires issue**: whether the thing is physically
handed over and taken back (a hired excavator) or not (a room).

### What a type holds, and who it's charged to

Open a type to set two things at once, in one save:

* **What it holds** — which of assets, tools, parts, places and people this kind of booking may hold,
  and an optional cap on how many of each.
* **Charged to** — which of the six payer dimensions this kind of booking may be charged to, and which
  one the form opens on by default.

<Note>
  Nothing ticked in either list is the widest setting, not the narrowest: a type that has declared
  nothing holds anything and may be charged to anybody, exactly as it worked before either table
  existed. Tick to narrow; **Let it hold anything** clears the list back to unrestricted.
</Note>

Whether a booking of this type needs approving before it's confirmed isn't set here — it's a
published [workflow](/config/workflows) for bookings, which is the only mechanism that can say *who*
approves.

## Rate cards

A rate card prices one thing a booking can hold — an asset, an asset type, a tool, a tool type, a
worker, a worker type, a location or a location type — at a basis (per hour, per day, per week, per
month, per use, or per unit on the meter) and a billing rhythm (daily, weekly, monthly, or once on
return).

| | |
| - | - |
| **In force** | Whether the card's effective dates cover today. A card outside its window still lists and still looks configured, but matches nothing — this is computed rather than left for you to compare two dates against today, card by card |
| **Audience** | Internal only, external only, or blank for either |

<Warning>
  A resource kind with no rate card in force today prices nothing. A charge against it is still
  banked — with no amount, rather than an amount of nought that would reconcile silently — and shows
  up on [Bookings](/property/bookings) as **charges nobody could price** until a card is fixed. Parts
  are the exception: a part already has a price from stock, so a missing card for parts is a
  commercial choice rather than a gap.
</Warning>