Booking configuration lets admins create bookable resources and control how members can find, reserve, pay for, and manage those resources. Admins can configure resources and create bookings. Members can book the resources they are allowed to see and use.

A booking resource is anything members can reserve for a specific time or date.

Examples include:

Each resource can define its own visibility, booking interval, availability, price, checkout behavior, notifications, upgrades, access settings, and booking permissions.

Admins manage booking resources under Admin > Booking > Resources.

To create a new resource, open the resource list and choose Create. To update an existing resource, open it from the resource list. The resource editor is divided into sections so you can configure the member-facing booking experience step by step.

Use the general settings to define how the resource appears to members.

The resource name is shown in resource lists, calendars, checkout, booking confirmations, and internal booking views.

Examples:

Choose a name that members can recognize quickly.

Use the description to explain what the resource is for or to add booking instructions.

Examples:

Select a location if the resource belongs to a physical or online location. Members can use locations as filters in the booking calendar.

Examples:

Locations are managed separately in the community settings.

Upload an image that helps members understand what they are booking. This can be a room photo, coach profile image, equipment preview, or visual of the resource.

Images are useful when members compare several similar resources.

Maximum image size: 2 MB.

Enable Hidden when a resource should not be visible to members yet.

This is useful when:

If a hidden resource has no custom Who can see resource rule, coapp treats it as visible to admins only. If a custom visibility rule is set, that rule decides who can discover the resource.

The booking interval controls how members select time in the calendar and checkout.

Available intervals:

Use shorter intervals for flexible resources such as meeting rooms or desks. Use hourly intervals for services or equipment rentals that should be booked in larger blocks. Use day-based booking for resources such as accommodation, day passes, or all-day rentals.

Existing resources without a configured granularity are treated as 30-minute resources.

For time-based resources, you can set a minimum and maximum booking duration.

Examples:

Use minimum durations for resources that need preparation time or should not be booked for very short periods. Use maximum durations to prevent one member from blocking a shared resource for too long.

For day-based resources, configure:

Examples:

Day-based resources are shown in a month calendar. Members select dates, while the configured check-in and checkout times are applied automatically during checkout.

Availability defines when a resource can be booked.

Select the weekdays when the resource is available.

Examples:

For time-based resources, set the From and To time for each rule.

Example:

For predictable availability, configure one continuous availability window per weekday. Date overrides take precedence over weekday availability, so members see the override for that specific date.

For day-based resources, select the weekdays that can be booked. The configured check-in and checkout times are used instead of per-rule times.

Use date overrides for one-off changes.

Examples:

An override can make a date bookable at different times or block the date completely. Members see the resulting availability directly in the booking calendar.

Enable Book whole slot when members must book the complete available slot.

Example:

When this is enabled, members do not adjust the start or end time inside checkout.

Use this for:

Enable Price per slot when the resource should have one fixed price for the full slot, regardless of the slot length.

Example:

Use this when the booking should be priced as a package instead of by time.

If billing is enabled and at least one public plan exists, admins can set a resource price.

The displayed price unit follows the resource setup:

If the price is 0, members can book the resource for free. Paid bookings require a valid payment method unless the member has enough credits or the booking is otherwise free for them.

When billing is enabled, select the tax rate that applies to paid bookings. The selected tax rate is shown in the checkout price preview.

The booking currency follows the community currency. It is not configured per resource.

Configure what members see and receive after a successful booking.

Use the after-booking title and text to show next steps after confirmation.

Examples:

Add an optional button when members should open another page after booking.

Examples:

Customize the email sent to members after booking.

Example:

Available placeholders:

Add email addresses that should receive internal booking notifications.

Use this for:

Notification emails include booking information and user contact details.

Blocking rules automatically block related resources when this resource is booked.

Example:

If Meeting Room A is booked, the Projector can become unavailable for the same time.

Use blocking rules for:

Use calendar synchronization when bookings should appear in a connected Google Calendar or when calendar events should affect resource availability.

Setup:

This helps teams manage bookings together with their existing calendar workflows.

Add a terms and conditions link if members must accept specific terms before completing a booking.

Examples:

When a link is set, members must accept it in checkout before they can confirm the booking.

If access management is enabled, assign a connected lock to the resource.

Configure:

Example:

If a booking runs from 10:00 to 11:00, with 10 minutes before and 15 minutes after, access is valid from 09:50 to 11:15.

Use access management for:

If the booking confirmation email includes {{pin}}, members receive the access PIN in their confirmation email.

Booking upgrades let members add optional extras during checkout.

Examples:

Each upgrade can define:

Members select eligible upgrades in checkout, and the price preview updates accordingly.

Use Who can see resource to control which members can discover the resource. Use Who can book resource to control which members can complete a booking.

Examples:

Members only find resources that match their filters and visibility rules. Members can complete checkout only for resources they are allowed to book.

Members open the booking calendar from the app navigation.

After a successful booking, members can add the booking to Google Calendar, Outlook, or an ICS calendar file. They can also open My bookings to review upcoming bookings.

Time-based resources support week, three-day, and day views. The selectable step follows the configured granularity. Past time slots and unavailable slots cannot be booked.

Day-based resources use a month view. The calendar marks unavailable and past dates. If a day-based resource checks out on the following day, coapp applies the configured overnight logic so members select the booking start date while checkout uses the configured following-day checkout time.

Unavailable or fully booked slots cannot be selected. Resources with whole-slot booking use the complete configured slot in checkout.

Checkout shows a price preview with subtotal, tax, and total. Members can open price details to see line items, taxes, credits, discounts, and selected upgrades.

Free bookings can be confirmed directly. Paid bookings require a valid payment method unless the final price is covered by credits or discounts.

The booking checkout and booking details show the cancellation policy when one applies to the resource. If a cancellation period exists, members can cancel free of charge until the displayed cutoff before the booking starts. After that, the booking is non-refundable.

Members can review upcoming bookings under My bookings.