Skip to main content

​
What this check does

DSALTA compares the users on the Confluent Cloud Access page against your People directory, matched by email within your organization. It passes when every Confluent Cloud user is an active employee on the People page.
This check also runs on 115 other integrations — see User access to Critical System should be valid for the full list.
The Access page shows every user account in the organization but not their role bindings — Confluent’s users endpoint returns none. Check what each person can actually do under Accounts & access when you review.
Passes when: Every user with Confluent Cloud access is an active employee on the People page.

​
Why this matters

Access to the organization’s event-streaming infrastructure must be limited to current, authorized employees.

​
How to fix

Review Confluent Cloud user accounts
  1. Sign in to confluent.cloud as an OrganizationAdmin.
  2. Expand the sidebar menu and open Administration → Accounts & access. The Accounts tab lists every user account in the organization.
  3. Compare every user against your current employee roster, paying attention to any address on an external domain.
  4. For anyone who should no longer have access, open their account and remove them from the organization.
  5. For anyone over-permissioned, open their account’s access and remove the role bindings they do not need.
  6. In DSALTA, go to People and confirm every remaining Confluent Cloud user maps to an active employee.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

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.
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.
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.
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.
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.