> 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/tenant/conditional/list-named-locations/add.md).

# Add Named Location

This page creates a Conditional Access named location. Unlike most pages in CIPP, it is not limited to the tenant selected in the menu bar: you choose the tenants explicitly, and the same named location is created in each of them. That makes it a quick way to roll a standard office IP range or country restriction out across your estate in one pass.

## Fields

| Field               | Description                                                                                                                   |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Select Tenants      | The tenants to create the named location in. At least one is required, and All Tenants is available.                          |
| Named Location Name | The name of the location, as it will be referenced by Conditional Access policies. Required.                                  |
| Type of Location    | Either **Countries Location** or **IP Location**. The remaining fields depend on this choice. Defaults to Countries Location. |

### Countries Location

| Field                                 | Description                                                             |
| ------------------------------------- | ----------------------------------------------------------------------- |
| Countries                             | The countries or regions the location covers. At least one is required. |
| Include unknown countries and regions | Includes addresses that cannot be mapped to a country. Off by default.  |

### IP Location

| Field                    | Description                                                                                   |
| ------------------------ | --------------------------------------------------------------------------------------------- |
| IPs                      | The address ranges, one per line, in CIDR format, for example `111.111.111.111/24`. Required. |
| Mark as trusted location | Marks the location as trusted. Off by default.                                                |

{% hint style="info" %}
A named location is either country-based or IP-based, never both. If you need to combine the two in a policy, create separate named locations and reference them together in the policy's location condition.
{% endhint %}

{% hint style="warning" %}
Creating the same named location across several tenants gives you locations that share a name but are separate objects, each with its own identifier. Later edits are per tenant, so if the underlying ranges change you will need to update each one, either from the named locations list or by creating a replacement here.
{% endhint %}

***

## 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cipp.app/user-documentation/tenant/conditional/list-named-locations/add.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.