Summary

Every person who needs to access classroombookings should have their own user account. Each user account is uniquely identified by their username which will be used to log in. When not using LDAP authentication, local passwords are stored in the database using a secure one-way hash format.

The users list can be filtered by a partial match on name, username or email address, or a chosen role or department.

User details

Each user account must have a username, and is used to log in with. It will also be used as the user's identifier displayed to other users if a name or display name is not set.

A user can be associated with one Role which can grant certain permissions and set booking constraints. A user's role isn't visible to other users, but their Department (if set) will be visible on any bookings they create.

Constraints

Booking constraints can be applied to users to control the number of bookings they can create within a given time range, or the number of events in a recurring series. Each user can have a different value:

  • Inherit - the value set on the user's role is applied
  • Not set - the constraint does not apply
  • Other - a custom constraint value can be set for the user that overrides the role's value
Maximum number of active bookings Total active one-time bookings a user can have at a time. Once this count has been reached, the user will be prevented from creating new bookings until their earliest booking has occurred, or they cancel one or more future bookings.
Minimum days notice for one-time bookings Minimum number of days between the current date and the date of a new booking.
Maximum days ahead for one-time bookings Maximum number of days between the current date and the date of a new booking.
Maximum number of events for recurring bookings Maximum number of individual events that can be created as part of a recurring series.

Check access

You can view the permissions the user has in any room by selecting one from the dropdown list.