Understanding resources and availability
Resources are what Hubhus actually schedules — technicians, vehicles, teams, rooms, or any asset that can be booked. Understanding how resources work, and how availability is calculated, is key to getting your booking setup right.
TL;DR
A resource ≠ a user. Bookings always attach to resources — not campaigns or leads. Availability is blocked by: Busy events, business hours, travel rules, buffers, and external synced calendars. Free events never block availability. Tags group resources so booking forms only show relevant ones.
6 things to know about resources
Resources ≠ users. A user logs in to Hubhus. A resource is what gets booked — a person, vehicle, team, or location. A user can also be a resource (e.g. "Peter Hansen") but doesn't have to be. "Team North" or "Measurement Van 3" are resources with no user login.
Busy events block — Free events don't. Only events marked as Busy prevent new bookings. Free events (reminders, placeholders) are visible in the calendar but do not affect availability at all.
Business hours and special dates. Bookings must fall within the resource's configured business hours. Special dates (holidays, shortened days) override the regular schedule. Booking forms can be configured to bypass business hours if needed.
Travel rules. If enabled, Hubhus calculates travel time before and between bookings. This means a slot must have enough time for the service duration plus travel to and from the customer. Travel rules are often why availability appears more limited than expected.
Tags filter which resources appear. Resources carry tags (region, skill, vehicle type). Booking forms use these tags to only show relevant resources in availability. A "Roofing Inspection" form only considers resources tagged as roofing.
External calendar events count. Busy events imported from Google Calendar, Outlook, or CalDAV also block availability — just like internal events. If a synced calendar event is Free, it still doesn't block.
Read more⌄
Resource tags vs. User tags
Resource tags are applied to resources (technicians, vehicles, rooms). They determine which resources a booking form can use, what regions or skills they represent, and how multi-resource bookings are constrained.
User tags are applied to users (internal staff). They control grouping, access permissions, and internal routing. User tags do NOT directly affect availability.
Linking them: You can link user tags to resource tags. This controls which users are eligible to be assigned when a booking form requires a resource with a specific tag. Example: booking form requires resource tag "Inspection Technician" → only users with a linked user tag can be assigned.
Multi-resource bookings
Some bookings require multiple resources simultaneously — e.g., a technician + a vehicle, or two specialists. Hubhus checks availability across all required resources and only shows times where all of them are free at once.
Multi-resource availability respects each resource's business hours, external calendar conflicts, buffers and duration, and travel rules.
Duration and buffers
The service duration must fit cleanly between other events, including any pre-buffer and post-buffer configured on the booking form or resource. Gaps that are too small — even if technically free — will not show as available.
Common searches
resource vs user • availability not showing • booking blocked • resource tags • travel time • busy free event • multi resource booking
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article