Loom

Overview
How to connect
Automated checks
Useful links

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

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads the Loom user roster — names, emails, roles and active status, which appears on your Access page.It calls these Loom endpoints:

SCIM /scim/v2/Users

Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Loom environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the Loom card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Loom. This can happen if the SCIM token was revoked or regenerated in Loom’s Directory Sync settings.

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 click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.

Before you begin

A Loom Enterprise plan and workspace Admin access, and at least one authorized domain. Add the domain first under Workspace settings → Security → Authorize Domains (email verification or a DNS TXT record) — Loom will not let you configure SSO, and therefore not Directory Sync, until a domain is authorized.

Start in DSALTA

Open Integrations in the DSALTA sidebar, find Loom, and click Connect to open the connect panel.

Enable SAML SSO + Directory Sync in Loom

Loom SCIM requires an Enterprise plan with SAML SSO enabled. In Loom: Workspace Settings → Security → enable SSO, then enable Directory Sync (SCIM). SCIM is provisioned through WorkOS.

Copy the SCIM endpoint and bearer token

In Loom Workspace Settings → Security → Directory Sync, click Configure Directory Sync and scroll down to the Endpoint and Bearer Token the setup console displays, then copy both. You’ll enter the token in the next step (the SCIM token can be reused across IdPs like Okta or Entra ID).

Paste the SCIM endpoint URL exactly as Loom shows it, including the /scim/v2 path segment, and do not add a trailing slash. DSALTA appends only /Users to whatever base URL the connection holds — if the /scim/v2 part is trimmed off, every read returns 404 and the integration will look connected while syncing nothing.

Finish in DSALTA

Return to the connect panel you opened in step 1, enter the credential you just created, and confirm to complete the connection.You will be asked for two values, not one: the SCIM endpoint URL (sometimes shown as the SCIM Bridge URL) and the API key — the Bearer Token. Have both on the clipboard before you open the panel.

Once connected, Loom appears on the Connected tab and the checks below begin reporting after the first sync.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that everyone with Loom access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active Loom access.

Topic	Link
Setup	Loom — Configure SSO and Directory Sync (SCIM)
General	Loom website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting