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

# User access to Critical System should be valid

> Checks that everyone with Loom access is an active employee on the People page.

Checks that everyone with Loom access is an active employee on the People page.

## About

DSALTA compares the users on the Loom Access page against your People directory, matched by email within your organization. This check passes when every Loom user is an active employee on the People page. It runs on every sync using the workspace members DSALTA reads through read-only SCIM access.

## Why This Matters

Access to the organization's video knowledge tool must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure the Loom integration is connected so DSALTA has the current list of workspace members.

**Review Loom access**

1. In **Loom**, go to **Admin → Members** and remove anyone who is not a current employee.
2. In DSALTA, go to **People** and confirm each Loom user exists and is active.
3. In DSALTA, go to **Data Library → Access** and filter for **Loom** to review each user against their current job function.
4. Mark each reviewed user as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.

Once every Loom user is an active employee on the People page, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the Loom integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Loom configuration?">
    No. DSALTA uses **read-only SCIM access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Loom.
  </Accordion>
</AccordionGroup>