Skip to main content
Connect Spacelift with your tenant URL and an API key granted the Space admin role to sync managed users and stacks, and run access reviews. Read-only.
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 managed users of your Spacelift account whose status is active, with their username and role; users who are still invited or otherwise not active are left out. Spacelift’s managed-user record carries no separate email field, so the username is used as the identity — where your identity provider issues email-shaped usernames, matching to the People page works by email; otherwise DSALTA falls back to matching the username. Spacelift reports no join date or MFA state, so the MFA column shows Unknown and each row is stamped with the date of the sync.
The API key needs the Space admin role. Without it the key exchanges for a token normally, but listing users returns unauthorized and the connection is rejected.
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 Spacelift managed-user roster — usernames and roles of active users — which appears on your Access page; and your Spacelift stacks, which appear on your Inventory page with their state and whether they are administrative.It sends these GraphQL operations to https://<tenant>/graphql:
  • mutation { apiKeyUser(id, secret) { jwt } } — exchanges the key for a short-lived token
  • query { managedUsers { … } }
  • query { stacks { … } }
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Spacelift environment.

​
Troubleshooting

Check three things: the Tenant URL must be your full address including the region (https://<name>.app.spacelift.io or https://<name>.app.us.spacelift.io), the key ID and secret must be the pair from the downloaded config file, and the key must hold the Space admin role. A key without that role logs in and then fails with unauthorized when DSALTA lists users.
Only managed users whose status is active are synced. A user whose invitation is still pending, or who was deactivated, does not appear.
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.