> 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/ip-allow-list.md).

# IP Allow List

Define the networks that may connect to Sendman

## Overview

The **Global IP allow list** contains the address ranges that may connect to Sendman. Connections from any other address are refused before the SMTP dialogue starts.

<figure><img src="https://1641814212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EVg4twS3gtObqtkynsm%2Fuploads%2Fgit-blob-4f9d523040eb6dd6735633354fb55238f624ce79%2Fip-allow-list.png?alt=media" alt="IP allow list"><figcaption></figcaption></figure>

{% hint style="warning" %}
The allow list only decides who may **connect**. Whether a client may send, and whether it has to authenticate, is decided by the [authorization policies](/admin-portal/sendman/authorization-policies.md). An address on the allow list can therefore not send anything without a matching policy.
{% endhint %}

{% hint style="info" %}
As long as the allow list is empty, Sendman refuses all connections.
{% endhint %}

## Which addresses to add

Sendman checks the address the connection comes from:

* **Clients on the internet:** the public IP address of the internet connection the client uses, typically the public address of your office's firewall or NAT gateway.
* **Clients behind a** [**network connection**](/admin-portal/settings/network-connections.md)**:** the client's local IP address, e.g. `10.20.30.40`. Its local address is preserved through the tunnel.

## Add

1. Click **Add range**.
2. Enter the **Start address** and the **End address** of the range. For a single address, enter the same address in both fields.
3. Optionally, enter a **Description**, e.g. `Office network`.
4. Save the entry.

<figure><img src="https://1641814212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EVg4twS3gtObqtkynsm%2Fuploads%2Fgit-blob-81712c2814724a4534be48f854cdd0198fc64cf4%2Fip-allow-list-add.png?alt=media" alt="Add address range dialog" width="563"><figcaption></figcaption></figure>

The following rules apply:

* Only **IPv4** addresses are supported.
* An entry may cover at most **16,384 addresses** (a /18). Split larger networks into several entries, but keep the ranges as narrow as possible.
* Entries must not overlap.
* The description may contain up to 255 characters.

## Edit

Click the edit icon of an entry to change its range or description. The dialog also shows who created the entry and when.

## Delete

Click the delete icon of an entry and confirm. Clients in this range can no longer connect to Sendman.


---

# 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/ip-allow-list.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.
