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

# Loom

> How DSALTA integrates with Loom — data collected, setup guide, and automated compliance checks.

## Overview

DSALTA connects to Loom using read-only SCIM access to collect compliance evidence automatically. DSALTA reads your Loom workspace members and matches them, by email, against your People directory to run access reviews. Data syncs every 24 hours and feeds into your Data Library modules.

<Info>
  **Read-only access.** DSALTA never modifies, creates, or deletes resources in your Loom workspace.
</Info>

<Note>
  **What you'll see.** Loom exposes workspace members through SCIM, which requires an **Enterprise plan with SAML SSO** enabled. DSALTA's Access page lists the members returned by SCIM (identified by email), which it matches against your People page. If SCIM is not enabled, or a member's SCIM record has no email, the access checks below may not resolve automatically.
</Note>

## How to Connect

Loom is connected with a **SCIM bearer token** — there's no OAuth app to install.

<Steps>
  <Step title="Enable SAML SSO and Directory Sync in Loom">
    Loom SCIM requires an **Enterprise plan with SAML SSO**. In Loom, go to **Workspace Settings → Security** and enable **SSO**, then enable **Directory Sync (SCIM)**.
  </Step>

  <Step title="Generate a SCIM token">
    In **Workspace Settings → Security → Directory Sync**, copy the **SCIM endpoint URL** and generate a **SCIM bearer token**. The same SCIM token can be reused across identity providers such as Okta or Entra ID.
  </Step>

  <Step title="Connect">
    In the DSALTA sidebar, go to **Integrations**, find **Loom**, and click **Connect**. Paste your SCIM token in the secure window and submit.
  </Step>

  <Step title="Finish">
    DSALTA runs an initial sync — usually a few minutes — after which the compliance checks below activate.
  </Step>
</Steps>

## Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

| Check                                                                                                               | Description                                                                     |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| [User access to Critical System should be valid](/integrations/loom/user-access-to-critical-system-should-be-valid) | Checks that everyone with Loom access is an active employee on the People page. |
| [Offboarded users should not have active access](/integrations/loom/offboarded-users-should-not-have-active-access) | Checks that offboarded employees no longer have active Loom access.             |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Integration shows Disconnected">
    Re-authenticate from **Integrations → Loom → Reconnect**. This can happen if the SCIM token was revoked or regenerated in Loom's Directory Sync settings.
  </Accordion>

  <Accordion title="Data is not syncing">
    Confirm SAML SSO and Directory Sync (SCIM) are still enabled in **Loom → Workspace Settings → Security**, and that the SCIM token is current. Then trigger a manual sync from the integration settings.
  </Accordion>
</AccordionGroup>