Yes, you can limit who can book a resource or a room. There can be a list and anyone not on that list will not be able to book. But should you actually do this?
Two points here:
- In the sixteen years that Nexus has operated there has never been a reported incident of someone maliciously booking a room that they didn’t intend to use.
- Every time you create a restriction you add a layer of support complexity – and very often a significant delay in being able to use it – to the very people that you want to be able to use that resource.
We have had a support ticket today which has generated three tasks, over more than two weeks (so far), just to try and get one person to be able to book a room. And the only reason it’s this difficult is because there’s a restrictive list. Getting that right can be a challenge.
Seriously, people, save yourself some hassle, and save IT Services from unnecessary support tickets: just leave room bookings open to the University. You’ll be amazed how much easier they are to use. It doesn’t stop you from being able to moderate bookings, or have someone with permissions to edit the calendar directly to deal with any problem events.