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

# How integrations fit together

> Connections hold your data (your directory and storage). Connectors start verifications from the tools people already use, or act after a verification succeeds. What each one does and where to set it up.

This page is for anyone planning a TruU IDV rollout who wants to know what connects to what. When you finish you will know which integrations you need for your use cases and where each is set up.

## Two kinds of integration

**Connections** hold your data. They live under **Settings → Directory** and **Settings → Storage**.

**Connectors** link TruU IDV to other tools. They live under **Settings → Connectors**, and each one does one of two jobs: it **starts** verifications from where people already work, or it **acts after** a verification succeeds.

```mermaid theme={null}
flowchart LR
  subgraph Start["Connectors that start verifications"]
    SN[ServiceNow]
    MT[Microsoft Teams]
    API[Your tools, via the API]
  end
  subgraph IDV["TruU IDV"]
    UC[Use case picks the flow] --> FL[Employee completes the flow]
  end
  subgraph Data["Connections"]
    DIR[Directory: Entra ID or Okta]
    ST[Storage: TruU managed, S3 or Azure Blob]
  end
  subgraph After["Connectors that act after success"]
    TAP[Windows TAP]
    PING[PingOne MFA]
    PWL[TruU Passwordless enrollment]
  end
  Start --> UC
  DIR -.-> UC
  FL -.-> ST
  FL --> After
```

The help desk app and the self-service portal also start verifications. They're built in and need no connector.

## Connections

| Connection | What it's for | Required? |
| - | - | - |
| [Directory](https://docs.truu.ai/idv/connect/directory/overview.md) | Finds employees, their groups and the attributes factors check | Yes, to verify real employees |
| [Storage](https://docs.truu.ai/idv/connect/storage.md) | Where proofing records, face photos and capture media are kept | No. TruU managed storage is the default. |

Proofing vendors (Didit, PingOne Verify, Persona, Entrust) are set up on the [Proofing factor](https://docs.truu.ai/idv/factors/proofing/overview.md), not here.

## Connectors

![Connectors page with cards for ServiceNow, TruU Passwordless, Windows TAP, PingOne MFA and Microsoft Teams](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/settings-connectors-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=68bd31c1f30bcac318d0be16a56987e4)

| Connector | Job | What it does |
| - | - | - |
| [ServiceNow](https://docs.truu.ai/idv/connect/servicenow.md) | Starts | Agents send verifications from records, and catalog items can make employees verify themselves; results flow back to the record |
| [Microsoft Teams](https://docs.truu.ai/idv/connect/microsoft-teams.md) | Starts | Agents send verifications from Teams chat; employees can type `verify me` to verify themselves |
| [TruU Passwordless](https://docs.truu.ai/idv/connect/passwordless.md) | Acts after | Passwordless enrollment on Windows and macOS waits for a passed verification |
| [Windows TAP](https://docs.truu.ai/idv/connect/windows-tap.md) | Acts after | Issues an Entra ID Temporary Access Pass so the employee can sign in and add a new method |
| [PingOne MFA](https://docs.truu.ai/idv/connect/pingone-mfa.md) | Acts after | Resets the employee's PingOne MFA devices so they can register again |

Connectors that act after success are chosen per use case under **When it ends → Passed**. See [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md#outcome-what-happens-after).

## In sales terms

If you've seen TruU IDV presented as sources, channels and outcomes, the same picture maps like this:

| Sales term | In these docs |
| - | - |
| Sources: where identity evidence comes from | Your directory, proofing vendors and stored reference photos |
| Channels: where a verification reaches someone | The help desk app, self-service portal, ServiceNow, Microsoft Teams, Passwordless enrollment and the API |
| Outcomes: what happens after | Report only, Windows TAP or PingOne MFA, set on each use case |

## Related

* [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md)
* [API quickstart](https://docs.truu.ai/idv/api/quickstart.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.