Resources are the bookable things in your space: meeting rooms, equipment, dedicated workspaces, and anything else members or visitors can reserve for a block of time. Every resource belongs to a location inside your workspace, and each one carries its own pricing, availability windows, and booking rules. This article explains how resources are structured so you can set them up correctly. For the step-by-step booking flow, see Booking a resource.
What a resource is
A resource is a single bookable item or space. When you create one, you give it a name, a category, a capacity, a cover photo (and optional additional photos), and a description. The category is one of four fixed options: Meeting Room, Equipment, Workspace, or Other. The description is the public-facing text shown on your marketing website's space detail page.
Each resource is tied to one home location. If your workspace has more than one location, a resource can also be shared with additional locations so members at those sites can book it too. When a resource is shared, you can optionally choose which location its booking invoices are routed to. Resources are never deleted outright. Instead they are disabled, which removes them from booking lists while preserving their history. Members and guests never see disabled resources; only owners and admins can view disabled resources, using the status filter in the resources toolbar.
Bookable status
A resource only becomes bookable when at least one of its two audiences is allowed to book it: members or non-members. If you turn off both member bookings and non-member bookings, the resource is no longer bookable. These two switches independently control who can reserve the resource and which set of rates and booking hours apply.
Member and non-member rates
Deskie keeps two completely separate price lists on every resource: one for members and one for non-members. Members are charged the member rate, and guests (non-members) are charged the non-member rate. This lets you offer your community a lower price while still renting to the public at a higher one. You can enable bookings for members only, non-members only, or both.
Rates are entered as plain numbers with up to two decimal places. The rate that applies depends on who is booking and which interval they choose.
Per-interval pricing
Resources support four booking intervals, each with its own member and non-member rate:
- Hourly, shown as a per-hour rate (/hr).
- Daily, shown as a per-day rate (/day).
- Weekly, shown as a per-week rate (/wk).
- Monthly, shown as a per-month rate (/mo).
Hourly bookings are priced by duration: the hourly rate multiplied by the number of hours booked. The daily, weekly, and monthly intervals are flat rates. A daily booking covers that day's booking hours, a weekly booking runs from Monday's start time through Sunday's end time, and a monthly booking runs from the first day of the month through the last day. You only need to set rates for the intervals you actually offer.
Which intervals are offered
Each resource has an interval mode. In restricted mode the resource offers a single interval. In multi mode you enable several intervals and the person booking picks which one they want. At least one interval must always be enabled, and hourly is the default. When more than one interval is enabled, the booking screen presents the choices and shows each rate alongside its interval.
Capacity
Capacity records how many people a resource is meant to hold, for example the number of seats in a meeting room. It is a required field when you create a resource. Capacity is shown to members and guests on the resource card, the resource detail page, and during booking so they can pick a space that fits their group.
Capacity is informational. It is not a headcount limit that Deskie enforces on the number of simultaneous bookings. Whether two reservations can exist for the same time slot is controlled by the overlapping bookings setting described below, not by capacity.
Overlapping bookings
By default a resource can only hold one confirmed booking at any given moment. When someone tries to book a time that conflicts with an existing confirmed booking, Deskie blocks it and reports that the resource is already booked for that slot. Back-to-back bookings are allowed: one booking ending exactly when the next begins does not count as a conflict.
If you turn on Allow overlapping bookings, Deskie skips the conflict check entirely and lets any number of bookings share the same time. This suits resources where simultaneous reservations make sense, such as a large open area or a shared pass-style space. With overlapping enabled, every time slot is treated as available.
Cooldown between bookings
When overlapping bookings are not allowed, your workspace booking settings can add a cooldown buffer around each reservation. With a cooldown enabled, a new booking that falls within the cooldown window before or after an existing booking is rejected, even if the times themselves do not directly overlap. This gives staff time to reset a room between groups. The cooldown is a workspace-level setting and only applies to resources that do not allow overlapping bookings.
Booking hours and duration limits
Each resource has separate booking hours for members and for non-members, configured per day of the week. For each day you can turn availability on or off and set a start and end time. This means you can let members book evenings and weekends while limiting public bookings to standard business hours, or vice versa. When booking hours are not enabled for a resource, it falls back to a 9:00 AM to 5:00 PM window.
For hourly bookings you can also set duration limits:
- Minimum booking duration: bookings shorter than this are rejected.
- Maximum booking duration: bookings longer than this are rejected. Both limits are capped at 24 hours, and the minimum cannot exceed the maximum.
- Enforce maximum per day: when this is on, Deskie adds up the booking user's confirmed hourly bookings for the resource on the same calendar day. If a new booking would push their daily total past the maximum, it is blocked and the person booking is told how many hours they have left for the day. This is an anti-abuse control so a single person cannot tie up a resource all day in small chunks.
Access during bookings
Resources can be connected to door access so a booking grants entry for its time window. A resource can use push-button access through Kisi, or automatic unlocking through Deskie Access channels during the booking. These options are configured per resource. For the full picture of how door access works, see Resource access rules and the door access documentation.
Public links: booking, kiosk, and the resource list
Owners and admins can share resources publicly using links generated from the Links view on the resources page. There are three kinds of links:
- Public booking link (one per resource): sends someone straight to that resource's public booking page so they can reserve it without signing in to the admin app. Use this when you want to share a specific room or item.
- Kiosk link (one per resource): a public page for that single resource, suited to a tablet mounted outside a room or at a front desk. Each resource has its own kiosk URL.
- Public resource list link (one per workspace): a single link to your workspace's public list of resources, where visitors can browse everything that is publicly available and choose what to book.
Each link can be copied to the clipboard with one click. Members and guests do not see the Links view; it is admin tooling. The resources page itself also offers Cards and List views for everyone, plus a Calendar view available to admins that shows the day's bookings across resources in a multi-column schedule.
Who can see and book a resource
Resources are scoped to the current location, plus any locations a resource has been shared with. Admins viewing all locations see the full set. Beyond location scope, access rules can hide individual resources from specific members or restrict them to an allow-list, so not every member necessarily sees every resource. Admins always see the complete list with those rules surfaced in the permissions interface. See Resource access rules for how to control which members can book which resources.