> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/configuration/access/rux-allow-list-for-ui-and-api.md).

# RUX allow-list for UI and API

{% hint style="info" %}
**Please Note:**

This is only for RUX (Respond UX) customers only. QUX (Quadrant UX) customers can restrict access to their Brain appliances, wherever they are installed, though their own network controls if desired.

If you are unsure of your deployment type please see [Analyst UX options (RUX vs QUX)](/deployment/getting-started/analyst-ux-options-rux-vs-qux.md) for details.
{% endhint %}

## Overview

RUX customers now have the ability to request that an allow-list be configured for their Vectra tenant. Once an allow-list is configured, access from the public internet to both the UI and the API or their tenant will be restricted to the IP ranges that were submitted by the customer.

This feature is **supplementary** network filtering for customers who want an additional control; it is **not** the platform’s primary security boundary. Requests still go through the usual chain (API gateway, SaaS authentication, and application authorization) and remain subject to those checks regardless of allow-list configuration—the list does not replace them.

## Request Process

Please open a support ticket at [https://support.vectra.ai](https://support.vectra.aihttps/support.vectra.ai). You must be logged in to the portal to open a ticket. If you do not have access to the portal, please work with a contact at your company who does, or reach out to your Vectra account team.

**Guidelines for allow-list support tickets**

* Ticket must include **complete final CIDR list** every time
  * There are no incremental modifications allowed.
  * Every new request fully replaces the old list.
* Each line must be a valid **IPv4 or IPv6** address or **CIDR** (e.g. 203.0.113.4/32).
* Exact duplicates should be removed.
* Request must contain **at least one** customer CIDR block or IP unless you are requesting the allow list to be disabled (removed).

**Finding your tenant URL**

When logged into your RUX tenant, look at the URL bar in your browser and copy the first part of the URL that ends in portal.vectra.ai.

For example, if your URL is: `https://109796245472.ew1.portal.vectra.ai/accounts/3270`

The TENANT URL is: `https://109796245472.ew1.portal.vectra.ai`

**Title Example**\
`RUX Allow-list Request for <Customer name> at <TENANT URL>`

**Body Example**

Update the example below with:

* Tenant URL
* Request Type - put the `X` where it should go based on your request type.
* Allow List - follow the format exactly.
* Rollback Contact
* Confirmation - put an `X` in the blank to confirm.

```
TENANT URL: e.g. https://109796245472.ew1.portal.vectra.ai

REQUEST TYPE (pick one): [X] ENABLE allow-list (first time) [ ] UPDATE allow-list (replace entire list) [ ] DISABLE allow-list (remove feature for tenant)

FULL DESIRED CLIENT EGRESS ALLOW-LIST (complete replacement; include everything that should remain allowed): One IPv4/IPv6 address or CIDR per line, no commas, a leading dash and space:
- 100.100.100.10/32
- 100.100.110.0/24

ROLLBACK CONTACT: Name + email address

CONFIRMATION (required): [ ] This list is COMPLETE (not incremental). I understand the final production configuration will match the details in this submission..
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vectra.ai/configuration/access/rux-allow-list-for-ui-and-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.