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

# UI overview

> Choose the right UI option for viewing Resistant Documents results.

This section explains the available UI options for viewing Resistant Documents results and how to integrate them into your workflow.

<Note>
  Resistant AI supports two UI options: **Web UI** (hosted) and **Offline iFrame viewer**.
</Note>

## Choose the right UI option

<CardGroup>
  <Card title="Web UI (hosted)" href="./web-ui/access">
    Best for analyst workflows, deep links, and optional manual submissions.
  </Card>

  <Card title="Offline iFrame viewer " href="./iframe/overview">
    Best for embedded experiences and restricted environments.
  </Card>
</CardGroup>

***

## Web UI (hosted web app)

Use the Web UI if you want a fully hosted analyst experience for reviewing results in a browser.

**Best for**

* Fraud / underwriting / claims analysts reviewing cases in a dedicated UI
* Manual (drag-and-drop) document submissions during testing or investigations
* Deep linking to specific analyses from your internal systems

**Key characteristics**

* Hosted by Resistant AI
* Accessed via a tenant-specific URL
* Role-based access (read-only / read-write)
* Authentication via Resistant AI-managed accounts or federated SSO

**Deep links** You can link directly to an analysis using:

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

➡️ Next: [Accessing the Web UI](./web-ui/access)

***

## Offline iFrame viewer

Use the Offline iFrame viewer if you need to embed the results viewer into your own tool or run in restricted environments.

**Best for**

* Embedding the viewer into an internal portal
* Restricted / air-gapped environments
* Workflows where your system fetches results via API and renders them locally

**Key characteristics**

* Rendered in an `<iframe>` using a self-contained HTML/JS bundle
* Your application provides:
  * the original file bytes (`ArrayBuffer`)
  * result payload(s) from the Documents API:
    * `/fraud` (required)
    * `/decision` (optional)
    * `/classification` (optional)
* Data is passed into the iframe via `postMessage()`

<Warning>
  The Offline iFrame viewer requires provisioning and is enabled by agreement.\
  This documentation uses placeholders for the iframe bundle URL to prevent uncoordinated deployments.
</Warning>

➡️ Next: [Offline iFrame overview](./iframe/overview)

***

## Shared prerequisites

Depending on your environment and security posture, you may also need:

* Network egress allowlisting: see [Domains to allowlist](/getting-started/domains-to-allowlist)
* Web UI authentication setup (SSO / IdP): see [Web UI authentication](/view-results/web-ui/authentication-options)

<Tip>
  If you’re unsure where to start: use the **Web UI** first. It is the fastest path to analyst validation, and you can add the Offline iFrame later if needed.
</Tip>