> 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/management/room-lists/edit.md).

# Edit Room List

Opened from **Edit Room List** on the [Room Lists](/user-documentation/email/management/room-lists.md) page, this page renames a room list, changes which rooms and owners it holds, and controls whether it accepts external mail. The heading reads **Room List:** followed by the list's display name, and **Submit** applies every change on the page at once.

A **View members** button sits beside the heading. It swaps the form for a read-only table of the list's current contents, with a **Type** column marking each row as `Owner` or `Room` alongside the user principal name and display name. The button changes to **Edit Membership** to switch back.

{% hint style="warning" %}
Emptying **Display Name**, **Description**, or **Mail Nickname** leaves the previous value in place. These cannot be cleared from this page.
{% endhint %}

**Room List Properties**

| Field         | Description                                                                                                  |
| ------------- | ------------------------------------------------------------------------------------------------------------ |
| Display Name  | The name shown in the address list and in the room finder.                                                   |
| Description   | A free-text description of the room list.                                                                    |
| Mail Nickname | The alias of the room list. Changing this also renames the room list object, so it is not a cosmetic change. |

**Add Members**

| Field              | Description                                                                                                   |
| ------------------ | ------------------------------------------------------------------------------------------------------------- |
| Add Room Mailboxes | The rooms to add to the list, chosen from the rooms in the tenant. Rooms already in the list are not offered. |
| Add Owners         | The users to add as owners of the list. Users who are already owners are not offered.                         |

**Remove Members**

| Field                 | Description                                                                |
| --------------------- | -------------------------------------------------------------------------- |
| Remove Room Mailboxes | The rooms to take out of the list, chosen from its current members.        |
| Remove Owners         | The users to remove as owners of the list, chosen from its current owners. |

**Room List Settings**

| Field                                                   | Description                                                                                             |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Let people outside the organization email the room list | When on, senders outside the organisation can email the room list. When off, only internal senders can. |

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/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/management/room-lists/edit.md?ask=<question>&goal=<endgoal>
```

`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.