Booking policies¶
Booking policy is primarily configured per area. Use it to express operational rules rather than relying on users to remember them.
Time boundaries¶
Areas can define:
- minimum and maximum notice for creating a booking;
- minimum and maximum notice for deleting a booking;
- maximum booking duration;
- earliest and latest allowed booking date;
- permitted weekdays and holidays; and
- when booking opens in period mode.
Usage limits¶
MRBS can limit a user's number of bookings or total booked time over a day, week, month, year, or all future bookings.
Limits exist at area and global scope. Document the resulting policy for users, especially when several limits apply at once.
Simultaneous bookings¶
By default, a room cannot contain overlapping bookings. Additional policy can prevent a user from holding simultaneous bookings across rooms or areas.
Approval¶
When approval is enabled, responsible administrators review bookings before they become approved. Configure notification recipients and verify that pending bookings are visible to the right people.
Administrator behavior¶
Administrators traditionally bypass some policies. MRBS 1.12.2 includes configuration to require administrators to obey booking policy as well.
Use this when policy represents a real operational or safety constraint rather than a convenience rule.
Policy exemptions¶
Specific booking types can be exempted from selected limits. Keep exemptions narrow and document why they exist.
Test the boundary cases¶
For every important rule, test:
- exactly at the allowed boundary;
- just outside the boundary;
- a recurring series;
- a multiday booking;
- a normal user;
- an administrator; and
- a booking moved between areas.