> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/get-started/getting-started/activate-your-account/restrict-access-to-the-merchant-control-panel.md).
# Restrict access to the Merchant Control Panel
## Overview
Restrict access to the Merchant Control Panel only for specific IPs or IP ranges and increase the security of your account. By default, 2Checkout account users can access the Merchant Control Panel from any IP.
## Availability
All 2Checkout accounts.
## How to restrict access to the Merchant Control Panel
1. Log in to your [Merchant Control Panel](https://secure.2checkout.com/cpanel/).
2. Navigate to the **Settings** cogwheel in the upper right corner and click on **User Management**.
3. On the **User Management** page, click on the **Restrict access** tab.
4. On the **Restrict access** page, click on the **Add IP filter** button.
5. Specify a static IP address or a range of IP addresses in the iFrame window.
6. Apply the restriction to **all** or only to **selected** Merchant Control Panel users.
7. Click on the **Add filter** button to save the setting.
8. On the **Restrict access** page, click on the **Activate** button to enable the IP filtering system.
---
# 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.2checkout.com/get-started/getting-started/activate-your-account/restrict-access-to-the-merchant-control-panel.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.
