> ## 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 Descope console access.

## What this check does

DSALTA takes every user with Active status on the Descope Access page and matches it to your People directory by email address. A match whose person is terminated or offboarding is recorded as a serious issue. A Descope console member is Active unless the company marks the account as disabled. Users with no People match are not counted.

<Note>
  This check also runs on 141 other integrations — see [Offboarded users should not have active access](/tests/offboarded-users-should-not-have-active-access) for the full list.
</Note>

<Info>
  Descope's own account state is respected: a console member whose account the company has disabled is synced as **Inactive** and is not counted as retaining access, even if their People record is offboarded.
</Info>

| | |
| - | - |
| **Severity** | High |
| **Category** | `access` |
| **Data used** | Descope Access page users, People page offboarding status |

**Passes when:** No Active user on the Descope Access page matches a person who is terminated or offboarding on the People page. An Access page with no Active Descope users passes.

## Why this matters

Offboarded employees must not retain access to the organization's Descope company, which controls the customer authentication projects its products sign users in with and the management keys that administer them. A former employee who can still sign in to the Descope console can change how customers authenticate or mint a management key, long after anyone expects them to have access.

## How to fix

**Remove access for offboarded users**

1. Sign in to the [Descope console](https://app.descope.com) as a company administrator.
2. Open **Company → Descopers** and find each offboarded employee.
3. Disable or remove each of them.
4. Open **Company → Management Keys** and delete any management key they created.
5. In **DSALTA**, go to **People** and confirm each of those employees is marked terminated with an end date.

Once resolved, DSALTA records a **200** (compliant) result on this test's **Source Data** tab at the next scheduled run.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    Once a day, at 02:00 America/New\_York, while the integration is connected. A run is skipped entirely if the integration is not in a **connected** state, or if the test has been deactivated.

    To see a fix reflected sooner, open the test from **Compliance → Tests** and click **Run** in the **Run Test** row. You need Full Access to run a test on demand.
  </Accordion>

  <Accordion title="What does the status actually tell me?">
    The **Status** column answers "did the check run?", not "did I pass". **Completed** means DSALTA reached your system and finished evaluating — a check that ran and *found a problem* is still Completed.

    To see what it found, open the test and read the result code on the **Source Data** tab. **200** means nothing to fix; **204** means the check did not apply to your environment; **207** means it ran and found a compliance gap you need to act on. See [Understanding test results](/guides/compliance/test-results).
  </Accordion>

  <Accordion title="The check shows Failed. Does that mean I am non-compliant?">
    Usually not. On an integration-powered check, **Failed** means DSALTA was *blocked* and could not evaluate it — result code **403** (a missing permission) or **428** (a setting DSALTA still needs from you). Code **500** means the run failed on DSALTA's side.

    A genuine compliance gap does not turn the list red — it runs to completion and shows **207**.
  </Accordion>

  <Accordion title="What if this check does not apply to us?">
    Deactivate it: open the test from **Compliance → Tests**, then use the **⋮** menu at the top right of the panel and choose **Deactivate Test**. It applies immediately, with no confirmation step.

    Write your justification in the **Comments** tab **before** you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see [Test detail](/guides/compliance/test-detail).
  </Accordion>

  <Accordion title="Does DSALTA change my configuration?">
    No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.
  </Accordion>
</AccordionGroup>