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

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

## About

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

## Why This Matters

Access to the organization's knowledge base must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access to a knowledge base — which often holds sensitive processes, credentials, and internal documentation — widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach it is a core control in SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

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

**Review Guru access**

1. In **Guru**, go to **Team Settings → Members** and remove anyone who is not a current employee.
2. In DSALTA, go to **People** and confirm each Guru user exists and is active.
3. Mark each reviewed user as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.
4. Set a recurring access review schedule (quarterly is recommended).

Once every Guru user 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 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>