---
title: "Allowlisting"
slug: "allowlisting"
tags: ["administration", "security", "guides"]
updated: 2026-09-11T19:12:59Z
published: 2026-09-15T20:08:17Z
canonical: "docs.unqork.io/allowlisting"
---

> ## 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

Allowlisting restricts access to a Unqork environment to a set of trusted public addresses. Allowlists apply to both the UnqorkAI platform and Express. They cannot be configured separately.

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

## How Allowlisting Works

Once an allowlist is active, only traffic originating from the specified IP addresses can access the environment. All other traffic is blocked by the firewall.

Being on the allowlist does not exempt an IP address from standard security blocks. Improperly defined allowlists can impact end-users' experience. Network engineers and IT administrators should review the list before a request is submitted.

## Cloud Provider Differences

Allowlist behavior varies by cloud provider:

| Provider | Scope |
| --- | --- |
| **AWS** | Per environment, regardless of cluster. |
| **GCP** | Per environment, regardless of cluster. |
| **Azure** | Per cluster. Allowlisting one environment in a cluster affects all environments in that cluster. For example, adding an allowlist to the Staging environment in a non-production cluster also affects UAT and any other environments on the same cluster. |

## Requesting an Allowlist

Allowlist requests are managed through Unqork Support. The IT department can help define the specific IP addresses or ranges.

IP address ranges are specified using CIDR notation. For example, the range `203.0.113.0` to `203.0.113.255` is represented as `203.0.113.0/24`.

To submit a request:

1. Gather the environment URL or URLs to restrict.
2. Compile the list of IP addresses or CIDR blocks to allowlist.
3. Submit a support ticket at [support.unqork.com](https://support.unqork.com) with the environment URLs and IP list.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-06-03 | Initial publication. |

The Unqork front-end application framework that delivers Creator-built applications to end-users. Express is the layer end-users interact with—the published forms, screens, and navigation built in the Module Builder. Express is distinct from Express View, which is a Creator-facing preview tool in the IDE.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

Scope is a tool that limits an application's access to a user's account. An application can request one or more scopes, this information is then presented to the user in the consent screen, and the access token issued to the application will be limited to the scopes granted.

The Staging environment is the first level of application building in Unqork. Use it to build, test, and style your applications.

Use the UAT (user acceptance testing) environment to realistically test and navigate your applications as end-users would use them.

A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.