> ## 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 users with access to critical systems are authorized in Grafana.

## What this check does

DSALTA lists Grafana organization members (`GET /api/org/users`) with their org role and checks them against the allowed members for the org.

<Note>
  This check also runs on 144 other integrations — see [User access to Critical System should be valid](/tests/user-access-to-critical-system-should-be-valid) for the full list.
</Note>

| | |
| - | - |
| **Severity** | Info |
| **Category** | `access` |
| **Data used** | Org member list, Per-user role |
| **Permissions required** | `org.users:read` |

**Passes when:** Only authorized people retain active access to the Grafana organization.

<Note>
  **Check parameters.** This check evaluates against the following defaults:

  * `allowedEmails`: `[]`
  * `allowedRoles`: `[]`
</Note>

## Why this matters

Access to a critical monitoring system must be restricted to authorized people.

## How to fix

**Review Grafana org access**

1. Open **Grafana**.
2. Go to **Administration**.
3. Go to **Users and access**.
4. Go to **Users**.
5. Review roles and remove unauthorized members.

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>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.