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

# Accessing the Web UI

> How to access the hosted Document Forensics Web UI, including URL formats, deep links, roles, and testing vs production.

The **Web UI** is the hosted web application for reviewing Document Forensics results. It’s best suited for investigator/analyst workflows, PoCs, and operational review.

<Tip>
  If your corporate network restricts outbound access, see [Domains to allowlist](/getting-started/domains-to-allowlist).
</Tip>

## When to use the Web UI

Use the Web UI when you want:

* A fully hosted interface for reviewing results (risk verdicts, indicators, metadata)
* Direct access for analysts (without building your own viewer)
* Deep links from your internal tools directly into a specific analysis
* Optional manual submissions (drag-and-drop) during testing/investigation workflows (if enabled for your tenant)

## Web UI URL format

Your Web UI is hosted under a tenant-specific domain.

### Production

```text theme={null}
https://<tenant>-<org>.documents.resistant.ai
```

### Other production cells

If your tenant is provisioned outside EU (`us-1`, `ca-1`, `ap-2`, `ap-3`), the Web UI hostname includes a cell prefix:

```text theme={null}
https://<tenant>-<org>.{region.}documents.resistant.ai/analysis/<submission_id>
```

### Testing

```text theme={null}
https://<tenant>-<org>.documents.testing.resistant.ai
```

> Your exact `<tenant>-<org>` identifier is provided during provisioning.

## Deep links to a specific analysis

You can deep link directly to a single analysis using the `submission_id`.

### Production deep link

```text theme={null}
https://<tenant>-<org>.documents.resistant.ai/analysis/<submission_id>
```

### Testing deep link

```text theme={null}
https://<tenant>-<org>.documents.testing.resistant.ai/analysis/<submission_id>
```

If the user is not authenticated, they will be redirected to login (SSO/Okta) and then returned to the deep-linked page.

## Roles (high level)

The Web UI supports role-based access:

* **Read-only**: view results
* **Read-write**: submit documents and view results

Keep privileges to least-necessary.

## Testing UI notes (parity and separation)

Testing is separate from production:

* Different hostname (`.documents.testing.resistant.ai`)
* Separate user assignment/provisioning (users must be enabled for the testing tenant/app)
* Same general UI feature set (used for validation before go-live)