> ## 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 Workable access is an active employee on the People page.

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

## About

When you connect Workable to DSALTA, the platform syncs the members of your Workable recruiting account using read-only API access. On every sync DSALTA compares the members on the Workable **Access** page against your **People** directory, matched by email within your organization, and activates this check when a Workable member does not map to an active employee.

The check passes when every member with Workable access is an active employee on the **People** page.

## Why This Matters

Access to a recruiting platform tends to accumulate over time as roles change, leaving people with more than they need. Workable holds candidate and applicant data, so unauthorized or stale access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach it is a core control in SOC 2, ISO 27001, and GDPR.

## How to Fix

**Before you begin**

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

**Review Workable access**

1. In Workable, go to **Settings → Members** and review the members — remove anyone who is not a current employee.
2. In DSALTA, open **People** and confirm each Workable member exists and is active.
3. In DSALTA, go to **Data Library → Access**, filter for **Workable**, and confirm each member maps to an active employee on the **People** page.
4. Set a recurring access review schedule (quarterly is recommended).

Once every Workable member 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 Workable 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 every Workable member maps to an active employee, 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 Workable configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Workable.
  </Accordion>
</AccordionGroup>