Skip to main content

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.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Loom workspace.
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.

How to Connect

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

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).
2

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

Connect

In the DSALTA sidebar, go to Integrations, find Loom, and click Connect. Paste your SCIM token in the secure window and submit.
4

Finish

DSALTA runs an initial sync — usually a few minutes — after which the compliance checks below activate.

Automated Compliance Checks

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

Troubleshooting

Re-authenticate from Integrations → Loom → Reconnect. This can happen if the SCIM token was revoked or regenerated in Loom’s Directory Sync settings.
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.