Skip to main content
Connect LambdaTest with an Admin user’s username and access key to sync organization members with their MFA status, service accounts, and organizations, and run access and MFA reviews. Read-only. Data feeds into your Access accounts and Inventory pages.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the members of the one LambdaTest organization the credential belongs to — the organization is implicit in the credential, and the members of sub-organizations are not listed separately. Each row shows the member’s name (falling back to their username, then their email address), their email, and their LambdaTest role as LambdaTest reports it — Admin, User or Guest — or Member when none is reported. Pending invitations and service accounts are not organization members and never appear; a Guest is a read-only member and does appear. LambdaTest reports no account status on this roster, so every member is shown as Active and stamped with the date of the sync. LambdaTest does report per-user MFA, so the MFA column shows Yes or No, and is blank (a dash) for a member whose record carries no value.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the LambdaTest organization member roster — names, usernames, emails, roles and MFA status — which appears on your Access page; and your organization’s service accounts (username, creation date, teams and tags — never a token or access key) and the organization itself together with any sub-organizations (creation date and the number of available concurrency entries), which appear on your Inventory page. Service accounts appear once you have created one; the organization row appears whenever the organization call succeeds. Members’ last-login times and access-key dates are not synced, and the organization’s audit log is not read.It calls these LambdaTest endpoints on auth.lambdatest.com (or eu-auth.lambdatest.com when the region is eu):
  • /api/organization/users
  • /api/organization/service-accounts
  • /api/organization/sub-org
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your LambdaTest environment.

​
Troubleshooting

A wrong username or access key; a credential that is not an organization Admin’s — the organization endpoints are Admin-gated, and a service account’s credential cannot read the members; or the wrong region: an EU-resident organization’s credential sent to the US host is refused with the same error as a bad key. Enter eu as the region only if your organization signs in at eu-auth.lambdatest.com; any other value, or none, selects the US host.
If your organization has an Access Key Expiry policy, LambdaTest regenerates the access key when it expires and the connection stops working without warning. Set the policy to Never or add the connected user to its Excluded Users, copy the new key from Account Settings → Passwords & Security, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from LambdaTest.
Service accounts and the organization tree are read best-effort after the member roster: a failure on either call leaves that part of the Inventory page empty without failing the sync, and an organization that has not created a service account has nothing to list. Click Sync from integrations on the Integrations page to retry.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.