Skip to main content

​
What this check does

DSALTA takes every user with Active status on the LambdaTest Access page and matches it to your People directory by email address. A match whose person is terminated or offboarding is recorded as a serious issue. Every synced LambdaTest member is treated as Active because the organization roster has no status field. Users with no People match are not counted.
This check also runs on 141 other integrations — see Offboarded users should not have active access for the full list.
LambdaTest reports no account status on the organization roster, so every synced member counts as Active for this check. Removing the member from the organization is the only way to clear a finding.
Passes when: No Active user on the LambdaTest Access page matches a person who is terminated or offboarding on the People page. An Access page with no Active LambdaTest users passes.

​
Why this matters

Offboarded employees must not retain access to the organization’s LambdaTest organization, which runs its browser and app test sessions and holds the access keys its pipelines use. A former employee who can still sign in to LambdaTest can watch test sessions against unreleased builds or use an access key that still runs the organization’s pipelines, long after anyone expects them to have access.

​
How to fix

Remove access for offboarded users
  1. Sign in to LambdaTest (TestMu AI) as an organization Admin.
  2. Open Organization Settings → Members and find each offboarded employee.
  3. Remove each of them from the organization; their personal access key stops working with the account.
  4. In DSALTA, go to People and confirm each of those employees is marked terminated with an end date.
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 Compliance → 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 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.
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.