I have 30+ resource reservation databases (RRD) on Notes 8.0.2 servers located around the world. How do you control access by ACL if people make reservations from the calendar. Even if you make the default access, “No Access” anyone with a Notes id for that domain can make a reservation from the calendar because calendar reservations are accessing the address book and not the RRD. I would like to somehow control calendar access by straightforward ACL, but I don’t think this is possible.
One option is to use “specific people” for each of our rooms/resources. This is a standard feature of the RRD database, however, specific people does not allow the use of wildcards such as */GV/WidgetCompany which we use to control access by location. Constantly adding specific people by individual name or adding names to a group which is in the specific people field would be very time consuming.
Another option is to add readers fields to each room/resource but this is not a standard feature of the RRD database and could also be cumbersome.
How have others addressed this problem,i.e. feature.
Subject: groups and readers are good ideas…more info
I’ll admit we haven’t had to solve this problem yet, but I have some thoughts:
RE: One option is to use “specific people” …adding names to a group which is in the specific people field would be very time consuming.
Consider using the new “Auto Populate Method”=“Home Server” to keep the group updated. It sounds like maybe your users and their resources are organized that way?
RE: Another option is to add readers fields to each room/resource…
While that might not be listed as a standard feature of RR, it is a standard notes feature, and many copmanies use this to hide groups for mailing, so it should work. I would recommend trying this by creating a new “fake” resource. Give it a couple of days to get around and have a variety of people to try to reserve that resource. THEN add readers fields to that resource, again wait for the change to replicate, and have a variety of people attempt to reserve both thru RR and thru calendar.
Remember that you might need to apply readers not only in RR but also in names.nsf in the ($Resources) view.