> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/notifications/distribution-lists.md).
# Distribution Lists
Distribution Lists are collections of email or SMS addresses that can be used for notifying people not registered in IT-Conductor as users. Distribution Lists can be used as targets for notification subscriptions.
### Create a Distribution List
1\. In the IT-Conductor main menu, navigate to **Management → Notification → Distribution Lists.**
2\. Click on the **Create New Distribution List** icon.
3\. Supply the necessary information and click the 
to complete the process.
4\. A pop-up message will confirm that the Distribution List has been created. Click **OK** to dismiss.
5\. Once the new distribution list appears, click on the name of the Distribution List to edit.
6\. Click the **"@"** icon to edit the notification addresses.
7\. Click the to add a new target.
8\. Fill in the values and select the appropriate Provider (SMTP/SMS or custom if configured). Click the to save.
9\. A pop-up message will confirm that the Notification Target has been created. Click **OK** to dismiss.
10\. The new target will show up in the list. Repeat the last step to add more targets.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.itconductor.com/user-guide/notifications/distribution-lists.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.