--- title: "How to Manage IP Access Control" slug: "how-to-manage-ip-access-control" updated: 2026-09-21T14:11:32Z published: 2026-09-21T14:11:32Z canonical: "docs.discngine.com/how-to-manage-ip-access-control" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.discngine.com/llms.txt > Use this file to discover all available pages before exploring further. # How to Manage IP Access Control > ⚠️ **Role required:** The features described in this guide require the **Organisation Administrator** role. If you do not have this role, contact your organisation's administrator. IP Access Control allows you to restrict access to your organisation's applications based on the requester's IP address. You define Access Control Lists (ACLs), each containing a set of allowed IP address ranges in CIDR notation, and assign them to specific applications. When an ACL is enabled and assigned to an application, only requests originating from the listed IP ranges are allowed. All other IPs are blocked. > **Note:** Each application can only have one ACL assigned at a time. ## Navigation ![The IP Access Control page lists every configured ACL.](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Setting/acl_list.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=w%2FUl%2BwWz4lnI3zpsTGOlLFRQ%2B75sN5SglQtp47hjB1I%3D) Click on **IP Access Control** in the left sidebar or on the **IP Access Control** card on the home page. The page lists all ACLs defined for your organisation: | Column | Description | | --- | --- | | **ACL Name** | Name of the access control list | | **Description** | Optional description | | **Status** | Whether the ACL is active (Enabled / Disabled) | | **Applications** | Applications the ACL is assigned to | ## Creating an ACL ![The New ACL dialog where you give the rule a name, choose its applications and supply CIDR ranges.](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Setting/new_acl_dialog.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=CoVIN%2BNB2cTiCl%2BWyi9QycF%2F%2BatwtpguJer9udF%2BaAk%3D) 1. Click **New ACL**. 2. Fill in the **Access Control Edition** form: | Field | Description | Required | | --- | --- | --- | | **ACL Name** | A unique name for this ACL | Yes | | **Enabled** | Toggle to activate or deactivate the ACL. A disabled ACL has no effect even if assigned to applications | No (default: Enabled) | | **Description** | Optional description to help identify the purpose of this ACL | No | | **CIDR List** | One or more IP ranges in CIDR notation, one per line (e.g. `192.168.1.0/24`, `10.0.0.0/8`) | Yes | | **Applications** | The applications this ACL restricts — tick them in the searchable list | No | 3. Click **Apply** to save. ### CIDR format examples | CIDR | Allows | | --- | --- | | `203.0.113.42/32` | A single IP address | | `192.168.1.0/24` | All addresses from `192.168.1.0` to `192.168.1.255` | | `10.0.0.0/8` | All addresses from `10.0.0.0` to `10.255.255.255` | If your organisation uses a corporate VPN, obtain the VPN egress IP range from your IT team and enter it here. ## Editing an ACL 1. Click **Edit** next to the desired ACL. 2. Update fields as needed. 3. Click **Apply** to save. ## Enabling / Disabling an ACL You can temporarily suspend an ACL without deleting it by toggling the **Enabled** switch in the edit form. A disabled ACL has no effect: assigned applications are accessible from any IP. This is useful for temporarily opening access (e.g. during an incident or for a remote workshop) without permanently removing the IP restrictions. ## Deleting an ACL 1. Click **Edit** next to the ACL to delete. 2. Click **Delete** (red button). 3. Confirm the deletion. Deleting an ACL removes it from all applications it was assigned to. Those applications immediately become accessible from any IP. ## Assigning / Unassigning Applications Each ACL can protect one or more applications. To update the application assignment: 1. Click **Edit** next to the ACL. 2. In the **Applications** list, tick the applications to protect, or untick them to remove protection. 3. Click **Apply**. > **Reminder:** Each application can only be assigned to one ACL at a time. If you assign an application to a second ACL, it will automatically be removed from the first. ## How It Works 1. A user tries to access an application (e.g. opens the application URL). 2. The Admin Center checks whether the application has an active ACL assigned. 3. If yes, the user's IP address is checked against the CIDR list. 4. If the IP matches, access proceeds. If it does not match, access is denied. 5. If no ACL is assigned, or the ACL is disabled, all IPs are allowed. ## Related - [Organisation Administrator Guide](/public/docs/organisation-administrator)