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

Checks that offboarded employees no longer have active Guru access.

## About

When you connect Guru to DSALTA, the platform syncs your Guru team members using read-only API access. On every sync DSALTA matches each user with active Guru access to your **People** directory by email. If a matched person is offboarded (terminated or in offboarding) but still has active access, this check flags it as a serious issue.

## Why This Matters

Offboarded employees must not retain access to the organization's knowledge base. 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 Guru members.
* Ensure you have administrator access to your Guru team.

**Remove access for offboarded users**

1. In **Guru**, go to **Team Settings → Members** 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 access.

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