Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Booker25 allows you to define availability of its Resources. This defines when these can be booked. You can also create unavailabilities that define when resources are not available.

Resource availabilities are configured on the Resources tab. For example, the screenshot below shows a resource that is open Monday through Friday, from 8:00 until 16:00.


You can define availabilities for resources by going to the Resources tab. Click on a resource and then click 'New' in the Opening Times table of the Related tab. Fill out the following fields to define when the resource is available:

  • The Start Date defines when the availability starts having an effect on the resource. Before this date the availability has no effect.
  • TheĀ End DateĀ defines until when the availability is in effect. This date is inclusive, meaning that on that date the availability is still in effect.
  • The Start Time and End Time fields define from what time of day until what time of day the resource is available, in 24-hour format. Use 00:00 until 24:00 to indicate that the resource is available all day long.
  • The Unavailability checkbox lets you create unavailabilities. These are the exact opposite of availabilities, meaning that the resource is unavailable during the defined dates and times.
  • The Days multi-picklist lets you define on which days of the week the availability is in effect. If you only select Monday and Thursday for example, the availability is only in effect on every Monday and Thursday in between the Start and End dates.

You can leave End Date empty to create an availability that never ends


If you have a lot of resources, creating availabilities for each of them individually can be tedious. This is why Booker25 supports the inheritance of availabilities for resources.

Availabilities are inherited down the resource hierarchy from parents to children. If you look at the screenshot above, you will see that the currently selected resource inherits its availability from the City Nice, higher up in the resource hierarchy.

If you want to create exceptions to this inheritance, you can use the 'Availability Defined At' picklist on the Resource Type. In the screenshot below, the Room resource type is set to inherit its availability from the City that it's in. This means that only availabilities defined on the City or the Room itself will have an effect on each room. Set this field to 'Full Inheritance' to go back to the normal situation where availabilities are inherited from every resource above it.

Content by Label
cqllabel in ( "group-availability" , "teacher-availability" , "availability" , "resource-availability" ) and type = "page" and space = "BPD"
labelsavailability resource-availability teacher-availability group-availability

Page Properties

Related issues

titleOn this page

Table of Contents