> 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/operations/general/using-generic-portal-links-rux.md).

# Using generic portal links (RUX)

Generic Portal Links take you to specific pages in your RUX UI after inputting your RUX URL or tenant ID.  You might find these links in Docs, KBs, blogs, or training materials.

## Overview

Vectra AI is a highly segmented platform, which means each customer environment is accessed through a unique URL. To simplify access to specific parts of the Vectra UI from support articles, blogs, and training materials, Vectra may sometimes provides a **generic portal link** that routes you to the correct tenant-specific portal deep link after you supply your tenant ID.

This article explains what a generic portal link is, how it works, and where to find your tenant ID.

## How it works

<https://portal.vectra.ai/configuration/lockdown>

A support article, documentation, blog, or training materials, etc may contain generic portal links such as the above which would direct you to a portal where you can enter your full RUX URL or just the tenant ID:

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FPjmYfmGAJmN2uleZ5Xzm%2Fimage.png?alt=media&amp;token=f533ecfb-a2c5-4135-a387-53cd9d0a1999" alt="" width="563"><figcaption></figcaption></figure>

A generic portal link is a single, shared entry point to the Vectra platform. Instead of taking navigation paths, or manually editing URLs to include your full tenant-specific URL, you can:

1. Click on a the generic portal link.
2. Enter your RUX URL or tenant ID.
3. Be redirected automatically to your tenant’s Vectra portal on the correct destination after logging in (if not already authenticated).

Each Vectra customer has a unique tenant ID, which identifies their environment within the Vectra platform.

## Finding your tenant ID

The tenant ID is a **12-digit numeric code** that forms part of your tenant-specific Vectra URL.

**Example:**

If your Vectra portal URL looks like this:

<https://123456789012.ab1.portal.vectra.ai>

The tenant ID is:

123456789012

You can find your tenant ID in one of the following ways:

* **From your browser address bar**: When you are logged in to the Vectra platform, look at the URL. The 12-digit number at the beginning of the URL is your tenant ID.
* **From a saved bookmark**: If you have previously bookmarked your Vectra portal, the tenant ID will be visible in the bookmarked URL.

## Caching Behavior

After you enter your tenant ID for the first time, it is **cached in your browser**. This means:

* You will not be prompted to re-enter your tenant ID on subsequent visits.
* Future visits to the generic portal link will automatically redirect you to your tenant’s portal.

If you clear your browser cache or use a different browser or device, you may be prompted to enter the tenant ID again.

## Troubleshooting

* **Incorrect tenant ID**: Ensure you enter all 12 digits exactly as they appear in your Vectra URL.
* **Unexpected tenant**: If you are redirected to the wrong environment, clear your browser cache and re-enter the correct tenant ID.

If you continue to experience issues, please contact Vectra Support.


---

# 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.vectra.ai/operations/general/using-generic-portal-links-rux.md?ask=<question>&goal=<user_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.
