Video
Having trouble viewing? Watch the video here!
Where do I find it?
Operations > Resource Management > Create resource or edit an existing one
What does it mean?
Resources in the system can carry capacity templates and shared availability capabilities. When a resource with an assigned capacity template is added to a departure, it overrides the departure's default capacity with the template's values. Additionally, resources with the share availability capability allow multiple departures to draw from a single shared capacity pool — meaning bookings on one departure automatically reduce availability across all linked departures.
What should I do?
Configure capacity and shared availability so departures draw from the right capacity and, when needed, a single shared pool.
Activate capacity for a resource (assign a capacity template).
Enable shared availability on the same resource, then assign it to overlapping departures to share the pool.
A resource with the shared availability capability must also have a capacity template assigned. Creating a resource with shared availability but no capacity template is not supported — the system requires a capacity template to manage the shared pool across departures.
Once shared availability is enabled, assign the resource to multiple departures that start at the same time. The system will prompt you to confirm sharing; after confirmation, all linked departures draw from the same capacity pool.
To do this, go to Operations > Next departures and assign the shared availability resource to the departures.
A confirmation pop-up will appear when assigning such a resource to overlapping departures.
After confirmation, all linked departures show the same vacant seats. If the numbers don’t update immediately, refresh the page.
Bookings made on any departure sharing a capacity pool will reduce vacant seats across all linked departures simultaneously. Each departure maintains its own manifest, but the available capacity is shared.
Good to know
A resource with shared availability can be assigned to a maximum of five departures. Shared capacity is only possible when the departures are scheduled at the same time, and the resource must have a capacity template assigned for the shared availability capability to function.
Each departure that shares a capacity pool maintains its own separate manifest — passengers are tracked individually per departure. However, the vacant seat count is driven by the shared capacity template: when tickets are booked on one departure, the available seats decrease across all departures linked to that resource.
When a reservation is canceled on one of the shared departures, the vacant seat count increases back across all linked departures — the shared capacity rollback is automatic.
FAQs
➕ Can I manually change the capacity template on a departure if it was assigned through a resource?
No. When a capacity template is applied via a resource, it cannot be changed directly on the departure. You need to update the template on the resource itself.
➕ What happens to availability when I book tickets on one of the shared departures?
The vacant seat count decreases simultaneously across all departures sharing that capacity pool. For example, if 10 tickets are booked on one departure, all linked departures will reflect 10 fewer vacant seats.
➕ Do shared departures have the same passenger manifest?
No. Each departure maintains its own separate manifest. Only the capacity (vacant seats) is shared across departures linked by the same resource.