> For the complete documentation index, see [llms.txt](https://docs.sendman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sendman.com/admin-portal/sendman.md).

# Sendman

Control who may connect to Sendman and who may send which messages

The **Sendman** menu group contains the three building blocks that decide whether a message is accepted:

| Page                                                                      | Decides                                                    |
| ------------------------------------------------------------------------- | ---------------------------------------------------------- |
| [IP Allow List](/admin-portal/sendman/ip-allow-list.md)                   | Which networks may **connect** to Sendman                  |
| [SMTP Credentials](/admin-portal/sendman/smtp-credentials.md)             | Which usernames and passwords clients can **sign in** with |
| [Authorization Policies](/admin-portal/sendman/authorization-policies.md) | Which sender and recipient addresses a client may **use**  |

A message is only accepted if all three steps succeed:

1. The client connects from an address on the [IP Allow List](/admin-portal/sendman/ip-allow-list.md).
2. The client signs in with a [Sendman credential](/admin-portal/sendman/smtp-credentials.md) or an Entra ID account, or sends anonymously.
3. An [authorization policy](/admin-portal/sendman/authorization-policies.md) that applies to this client allows the sender address and every recipient address.

All pages share the same table columns **Description**, **Created by**, **Created** and **Last change**, so you can always see who changed an entry and when.

{% hint style="info" %}
Changes apply to new connections immediately.
{% endhint %}


---

# 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.sendman.com/admin-portal/sendman.md?ask=<question>&goal=<user_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.