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

## What this check does

DSALTA matches each user with active Qase access to your People directory by email. If a matched person is offboarded (terminated or in offboarding) but still has active access, the check flags it as a serious issue.

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

<Info>
  Qase's own user status is respected: a user Qase reports as inactive is synced as **Inactive** and is not counted as retaining access.
</Info>

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

**Passes when:** No offboarded employee retains active Qase access.

## Why this matters

Offboarded employees must not retain access to the organization's test-management platform.

## How to fix

**Remove offboarded users from Qase**

1. Sign in to [app.qase.io](https://app.qase.io) as a workspace owner or admin.
2. Open the workspace settings, go to **Users**, and find each offboarded employee.
3. Remove or deactivate them.
4. Have any API tokens they created revoked from their **API Tokens** page — a token keeps its owner's workspace access until the user is removed or the token is deleted.
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>