That's a recipe for disaster. Note that since a building scheduler can edit anything scheduled at their building, the building scheduler for Ward A can alter Ward B's events to make room for his/her ward. Not a good idea.DMuir wrote:Thank you, currently we have one building scheduler for each ward. As you point out, if they are not aware of other ward reservations, the reservation is meaningless when the other building scheduler books an event.
At most I'd suggest two Building Schedulers: a primary and a backup (for when the primary goes on vacation).
We currently have one building in the stake with NO building scheduler and three wards in it. I've heard no complaints. Each ward schedules their events and that's all they need. So far, they've not asked for any "Scheduling Restrictions" (known in the calendar system as a "Reservation") to be placed on their building.
Building schedulers are only needed for two things: To set scheduling restrictions ("reservations") and to referee any conflicts. That's it. They are not needed for normal functioning. Calendar admins and editors do that. In fact, unless you give a Building Scheduler additional rights, they can't function effectively in any day-to-day role.