> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/core-concepts/geofencing.md).
# Geofencing
[Organization](/core-concepts/organizations.md) administrators can choose to limit access to their organization to certain IP address ranges and zones through a feature we call *Geofencing*.
## Geofencing your organization
From the *Organization* page, navigate to the Geofencing tab, then enable the toggle that appears. You will see the following:
Add the IP ranges and zones which will be allowed to access your organization, then click on *Apply IP and Zone Restrictions* to enable geofencing.
{% hint style="danger" %}
By applying the wrong geofencing settings, you may permanently lock yourself, and everyone else, out of your organization.
Before applying geofencing settings, please ensure that your IP, or your zone, is included in the IP or zones list.
{% endhint %}
{% hint style="info" %}
When both IP ranges and zones are configured, a caller must meet both restrictions. An empty list leaves that restriction disabled.
{% endhint %}
To disable geofencing, enter the *Geofencing* section of the *Organization* page, and turn off the toggle.
## Geofencing SDK and integration access
Geofencing also applies to API-key calls from the SDK, Copilot tools, hosted and workflow plugins, and webhook integrations. Add the calling hosts’ IP ranges and countries to your allowed lists before applying restrictions. Calls from outside the configured restrictions fail with HTTP **451**; the SDK raises the error returned by Ango Hub.
Restrictions apply to the organization associated with the API key. Outbound webhook delivery from Ango Hub is unaffected; an integration calling back into Ango Hub with an API key must meet the restrictions.
A restricted browser user can still switch organizations or sign out.
## Verifying whether your organization is geofenced
Next to your organization's name in the organization switcher, you will be able to see whether or not your organization is geofenced.
If the "world" icon is grey and without a padlock, your organization is not geofenced:
If the icon is green and showing a padlock, your organization is geofenced. Hovering over the icon will provide details about the geofencing settings:
---
# 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.imerit.net/core-concepts/geofencing.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.
