> 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/deployment/recall-qux-only/sso-access-to-recall.md).

# SSO access to Recall

The method used to access Recall Data is through your Vectra QUX UI, this also allows you to use your same egress whitelisted IP when working remotely, instead of having to add additional whitelist IP's( all requests to Recall will be proxied through your Brain appliance) when needing to access Recall offsite.

When looking at detections in the Vectra UI, select the link **Investigate in Vectra Recall** to access Recall data. This will navigate to the Recall UI and access the detection that is being investigated.

![](/files/GgVapcbAiu5pQs5nfxTO)

This feature also allows the users with Brain login credentials to go straight to their Recall Account.

Due to Vectra's security protocols to keep your information safe, and to allow for auditing of user access, users are only able to access the Recall UI through the Brain login.

If your company does not want all users to have access to the Recall instance, you can manage your users under *Configuration → ACCESS → Roles*. Then add the Users to a role without access to the permission **Recall - Data Access**.

![](/files/aiCWv4CKAiYzM9F778nZ)


---

# 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/deployment/recall-qux-only/sso-access-to-recall.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.