kmertlich wrote:That is what I was looking for. I am trying to make it so that only stake administrators can schedule calendar events with a location/room defined. That is why the reservation was set at the stake level for the entire day.
There is no way to restrict event scheduling to only stake administrators per se
; all stake calendar editors (which includes stake administrators) can create events on top of a Reservation that reserves a location/room for the stake unit.
On the other hand, a Blocked Reservation will allow only a building scheduler for that location to schedule on top of that Reservation; even stake administrators will be unable to schedule events for that location/room at that time.
kmertlich wrote:But it appears that I can't because of the risk of double booking.
The only bug I know of in this area is the one I linked to earlier
, and it applies only to building schedulers. Other than that rather obscure scenario, I know of no risk of double booking when the system is used properly.
For the issue you are discussing in this thread, I'm not sure what the actual reservations and events are. Could you please lay out in simple terms the scenario, describing the reservations and events involved and the people (by role) who are taking the actions? I'm looking for something like (this is all only hypothetical data to illustrate reporting detail):
- Reservation: On 1 Nov 2011 there is a reservation for the Cultural Hall of Building A, all day, assigned to the Stake unit.
- Event: On 1 Nov 2011, there is an event on a stake public calendar that books the Cultural Hall of Building A from 6:00pm to 9:00pm. This was added by a stake admin who is also a building scheduler.
- Event: A stake calendar editor (who is not a stake admin or building scheduler) tries to add an event that books the Cultural Hall of Building A on 1 Nov 2011 from 7:00pm to 9:00pm. This event is added successfully, but I expected that the system would report a conflict and refuse to save.