---
title: "Allowlisting in Unqork"
slug: "allowlisting-in-unqork"
description: "Allowlisting in Unqork restricts access to trusted IPs, enhancing security while managing network traffic effectively. Learn how to implement it correctly."
updated: 2026-06-03T18:09:45Z
published: 2026-06-03T18:09:45Z
canonical: "docs.unqork.io/allowlisting-in-unqork"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Allowlisting in Unqork

**Allowlisting** lets only trusted **public** IP addresses have access to your Unqork environment. It’s important to note that allowlists are applied to Designer and Express. You cannot request allowlists for Designer and Express separately.

> [!WARNING]
> **Important**: To maintain core platform operations, Unqork's service IPs must remain allowlisted alongside your organization's specified IP addresses.

## What Is a Firewall?

Firewalls act as a barrier between networks, controlling incoming and outgoing network traffic. This security measure uses a set of rules to determine whether network traffic should have access to the network or block it. Doing so prevents threats from malicious software and cyber attacks.

## How Does Allowlisting Work in Unqork?

Once you provide a list of **public** IP addresses, only those specified IP addresses can access your Unqork environment. However, take note that traffic originating from other IP addresses **will be blocked completely** by the firewall.

Below are considerations to keep in mind when whitelisting in Unqork:

- In AWS and GCP, **public** IP addresses can be whitelisted per environment regardless of the cluster where they reside.
- In Azure, **public** IP addresses can only be whitelisted on the cluster level, and will affect any environments in that cluster. For example, whitelisting in the Staging environment of the non-production cluster also affects other environments in that same cluster, like the UAT environment.

Improperly defined allowlists can potentially and severely impact your end-users' experience, with the perception of downtime. So, please work carefully with your Network Engineers and IT Administrators to ensure the list is **extensive and comprehensive**.

> [!WARNING]
> It's important to note that being on the allowlist does **not** preclude you from being blocked for standard industry security reasons.

> [!TIP]
> You can submit a support ticket to specify individual addresses or IP address ranges. These ranges are referred to as CIDR blocks. Your IT department can help you define the specific addresses or ranges for your allowlist. For example, the range might be `203.0.113.0 - 203.0.113.255`. This range is represented by the following CIDR notation: `203.0.113.0/24`. Submit a support ticket that includes the environment URL(s) and list of IP address CIDR blocks you are requesting to allowlist at [support.unqork.com](http://support.unqork.com/).