Require authentication before accessing a Bookings page
It would be nice to have an option to require authentication (and limited to a group of people) in order to access a particular Bookings page.
This allows for some services to be restricted and could prevent anonymous bookings from people attacking a site.
Slaughter, Marti commented
YES!! I'm using this service at a small college and I only want my students to be able to book appointments with me. There is an option on the Booking Page tab that states "Requrie an Office365 account from my organization to book," but the system does not capture the information from where the student signed in. Once someone has access to the form, they could spam my calendar with all kinds of false data and I would have no easy way to track them down.
I agree. During testing, we noticed the same loophole. We intended to use Bookings to manage a large collection of public facilities (we are a Council) and were excited about the potential use of Bookings. However, the ability of anonymous individuals to enter bogus information when we then need to remove from the Customer database is time consuming and frustrating. Customer's should be forced to submit a registration form for vetting before the details are added to the Customer database. Once registered, customers can sign-in, place a booking, manage existing bookings and reset their password, if required.
Absolutely, this should be pretty easy to implement and would make life so much easier!!
Adam Dickinson commented
Using Azure AD/O365 group membership for limiting to a subset of internal users please
Elliot Surrey commented
the ability to make a page public or not is essential
Samih Ajrouch commented
we have similar requirement here