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

# IP restriction

Restrict Missive access to specific IP addresses for added security.

{% hint style="warning" %}
IP restriction is only available on our [Business plan](https://missiveapp.com/pricing).
{% endhint %}

IP restriction refers to a security measure that allows or denies access to Missive based on the IP address of the user. By configuring IP restrictions, you can control who can access Missive and from where.

For example, you could allow access from specific IP addresses, such as those belonging to your company, to prevent unauthorized access from outside the network. IP restriction can also be used to prevent access from known malicious IP addresses, mitigate hacking attempts, and protect sensitive data.

{% hint style="info" %}
Please note that IP restriction applies to non-admin users only. Therefore, if you’re testing this feature logged in as an admin, it will not work.
{% endhint %}

#### Availability

Once you've upgraded to the Business plan, you will be able to manage IP restrictions in your **Settings > Organization**.

#### How IP restriction works

Each time a non-admin user interacts with Missive – whether it's fetching new emails, chatting, or sending an email, etc. – Missive verifies that the user's IP address matches one defined in the IP restriction settings.

To put it plainly, when IP restriction is activated, any non-admin or non-owner user who is logged in from an IP address that doesn't match the allowed list will be immediately logged out of Missive.


---

# 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://missiveapp.com/docs/administration/security/ip-restriction.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.