A resource is an Office 365 account typically used for non-person related calendars, e.g. meeting/conference rooms, audio-visual equipment, project, or vacation calendars. Resources contain special options for scheduling and permissions that are not available in user/service accounts. Users must be granted permissions to interact with a resource account. This document provides instructions on how to manage invitation permissions for a resource account. If you are wanting to manage read/write/editor permissions to the resource calendar, go to Office 365 (Outlook on the web | Outlook for Windows/Mac) - Manage Permissions to a Resource Calendar.
If immediate board action is required and a director does not waive the two-day notice period to call an emergency meeting, that director would not be living up to their fiduciary responsibility to the Association. An emergency meeting can be held in person, by phone, or even email if all directors agree in writing. Meetings can be confusing.
We wanted to remind you that we can help determine the best solution for setting up a resource calendar based on your departmental needs and workflows. If you are unhappy with the way your resource calendars are currently working, we may be able to help you adjust your settings in a way that will address your concerns. Please contact the DoIT Help Desk for support. Any questions or concerns that can't be addressed by the Help Desk will be escalated to the UW-Madison Office 365 team.
Okay - so all of your rooms should have this limit. It's set typically to 180 days. If you have PowerShell connected to your Exchange Online tenancy you can use the Set-CalendarProcessing cmdlet using the BookingWindowsInDays switch to change it ( https://technet.microsoft.com/en-us/library/dd335046(v=exchg.160).aspx ) or if you want to be un-cool you can use the ECP ( here's a quick guide I googled https://robinpowered.com/blog/how-to-restrict-event-length-in-room-calendars-on-office-365/ ) - you're not really un-cool... just learn PowerShell, you won't regret it. It's way easier to find functionality through cmdlets than it is through GUIs.
It's probably out of the scope of your question, but if you need to you can grant only certain users the ability to book in larger windows using the bookInPolicy switch on the cmdlet, but rather than confuse this post, I'll leave it there.
It's probably out of the scope of your question, but if you need to you can grant only certain users the ability to book in larger windows using the bookInPolicy switch on the cmdlet, but rather than confuse this post, I'll leave it there.