RussellHltn wrote:One purpose for creating reservations to to allow scheduling for next year in phases. For example, if you block everyone, then only someone with building scheduler rights can place events.
I understand the first idea of blocking everyone to get started on annual calendar planning. That makes sure the stake planning process takes precedence over anyone scheduling events in advance.
RussellHltn wrote:Then you can change it to stake to let the stake calendar editors submit their events.
How do you "change it to stake"? Either the building is blocked or restricted to a certain ward or has no restriction. I assume at this stage that the stake is gathering input from stake organizations, wards, etc. I would think at this stage that you want people adding events to the appropriate ward and stake calendars. In order to allow that, wouldn't you need to remove all reservations? I don't know how you'd stop people from scheduling in the future at this point? I'd like to understand what you do in the process here.
RussellHltn wrote:Then lastly you change it to the final configuration of no reservations or only reservations for ward night.
Yes, I understand this.