> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/email/resource-management/list-rooms/edit.md). # Edit Room Opened from the per-row actions on the List Rooms page, this page will allow you to edit the details of the selected room. {% hint style="info" %} There is a refresh button in the top right corner that will allow you to update the page with the most up to date settings from Exchange. {% endhint %} ## Basic Information | Field | Description | | ------------------------- | ----------------------------------------------------------------------------------- | | Display Name | Edit the display name of the field as desired | | Hidden from Address Lists | Toggle this setting to set the Boolean value for the room's address list visibility | ## Booking Settings | Field | Description | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Room Capacity | Set the integer for the capacity of the room either by typing over the number or using the up and down arrows | | Maximum Booking Duration (Minutes) | The maximum allowable duration of a meeting | | Booking Window (Days) | The maximum number of days in the future a meeting can be scheduled | | Booking Process | Options for how the owner of the Bookings site will treat the calendar invites they receive are `None - no processing`(Invite will not be accepted or denied by the Room), `AutoAccept - Accept/Decline but not delete` and `AutoAccept - Accept and delete` | | Allow Recurring Meetings | A Boolean that will determine if the room accepts recurring meeting invites | | Allow Double-Booking | A Boolean that will determine if the room accepts meetings that double book the room | | Process External Meetings | A Boolean that will determine if the room processes invites from external users | | Enforce Room Capacity | A Boolean that will determine if the room mailbox caps meeting attendees to the capacity set above | | Forward to Delegates | A Boolean that will set whether meeting invites are automatically forwarded to those with delegated access to the room mailbox | | Add Organizer to Subject | A Boolean that will set if meeting subjects are appended with the name of the user who created the meeting | | Delete Subject | A Boolean that will remove the meeting subject from the room mailbox calendar | | Remove Canceled Meetings | A Boolean that will determine if the room mailbox removes canceled meetings from its calendar | ## Working Hours | Field | Description | | ------------------------------- | -------------------------------------------------------------------------------------------------------- | | Schedule Only During Work Hours | A Boolean that determines if the room will only accept meetings during work hours | | Working Days | A multi-select drop down that will let you determine which days are included in the room's working hours | | Timezone | Select the dropdown for the time zone the room is located in | ## Room Facilities & Equipment | Field | Description | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Wheelchair Accessible | Toggle this setting to set the Boolean value for the room's wheelchair accessibility | | Phone | A text field for the phone number of the room | | Audio Device | A text field to describe the audio device(s) available in the room | | Video Device | A text field to describe the video device(s) available in the room | | Display Device | A text field to describe the display device(s) available in the room | | Tags | A multi-select field to add or remove tags from the room. Tags are used to identify features of the room. To add a tag, type the text of the tag in the box and click "Add option: \" | ## Location Information | Field | Description | | -------------- | -------------------------------------------------------------------------------------- | | Building | The text for desired building name for where the room is located | | Floor | The integer value for the floor the room is located on | | Floor Label | The text label for the floor the room is located on | | Street Address | The text for the street address of the building where the room is located | | City | The text city of the building where the room is located | | State/Province | The text for the state where the building is located | | Postal Code | The postal code of the building where the room is located | | Country/Region | A dropdown box to select the country/region for the building where the room is located | *** ## Feature Requests / Ideas We value your feedback and ideas. Please raise any [feature requests](https://github.com/KelvinTegelaar/CIPP/issues/new?template=feature.yml) on GitHub. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cipp.app/user-documentation/email/resource-management/list-rooms/edit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.