What’s a Quota #
Quotas restrict reservations from being booked based on a configurable limit. The quota system in is very flexible, allowing you to build limits based on reservation length and number reservations.
Quotas applied to a group are enforced for each user in the group individually. It does not apply to the group’s aggregated reservations.
If you choose to not include past reservations in the quota rules, the quota rule will only include current and future reservations in it’s calculation.
Building Rules #
Quota limits “stack”. For example, if a quota exists limiting a resource to 5 hours per day and another quota exists limiting to 4 reservations per day, a user would be able to make 4 one-hour-long reservations but would be restricted from making 3 two-hour-long reservations. This allows powerful quota combinations to be built.
Enforcement #
By default, quotas are enforced all day, every day. You can optionally configure quotas to only be enforced on specific days of the week and/or specific times of the day. This can be helpful if demand for resources peaks and you want to more evenly distribute usage during peak times.
A quota can also be stopped as the reservation time approaches. This can allow last-minute reservations from being exempt from the quota rule. For example, you may want skip a quota rule if someone is trying to book a resource an hour from now, but you’d like to enforce that rule if the reservation is a week ahead of time. This can be helpful if you want to maximize usage of idle resources.
It is important to remember that quota limits are enforced based on the schedule’s timezone. For example, a daily limit would begin and end at midnight of the schedule’s timezone; not the user’s timezone.
Application Administrators are exempt from quota limits.
