.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
What this check does
DSALTA compares the users on the Axiom Access page against your People directory, matched by email within your organization. It passes when every Axiom organization member is an active employee on the People page. Requires the connected API token to have the “users” read permission — without it, the Access page stays empty.This check also runs on 85 other integrations — see User access to Critical System should be valid for the full list.
Passes when: Every user with Axiom organization access is an active employee on the People page.
Why this matters
Access to the organization’s log-management and observability platform must be limited to current, authorized employees.How to fix
Review Axiom access- Open Axiom.
- Go to Settings.
- Go to Users.
- Remove anyone who is not a current employee.
- Go to DSALTA.
- Go to People.
- Confirm each Axiom user exists and is active.
Frequently asked questions
How often does this check run?
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 Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
What does the status actually tell me?
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.
The check shows Failed. Does that mean I am non-compliant?
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.
What if this check does not apply to us?
What if this check does not apply to us?
Deactivate it: open the test from Data Library → 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.
Does DSALTA change my configuration?
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.