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

# Offboarded users should not have active access

> Checks that offboarded employees no longer have active WorkOS access.

Checks that offboarded employees no longer have active WorkOS access.

## About

Offboarded employees must not retain access to your organization's identity platform. DSALTA matches each user with active WorkOS access to your **People** directory by email. If a matched person is offboarded (terminated or in offboarding) but still has active WorkOS access, the check flags it as a serious issue. DSALTA re-evaluates this control on every sync.

## Why This Matters

When someone leaves and their access is not revoked, their credentials become an unmonitored door into your systems — a common cause of data theft and accidental damage. Timely access removal on termination is explicitly required by SOC 2, ISO 27001, and GDPR.

## How to Fix

**Before you begin**

* Identify all offboarded employees by cross-referencing your HRMS (or the DSALTA People module) with active WorkOS users.
* Ensure you have administrator access to the WorkOS Dashboard.

**Remove access for offboarded users**

1. In the **WorkOS Dashboard**, go to **Users** and remove members who have been offboarded.
2. In DSALTA, go to **People** and confirm offboarded employees are marked terminated.
3. To automate this going forward, connect your HRMS to DSALTA so that an "Offboarded" status automatically flags any lingering WorkOS access.

Once offboarded employees no longer have active WorkOS access, 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 WorkOS 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 access is corrected, 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 WorkOS configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in WorkOS.
  </Accordion>
</AccordionGroup>