Skip to main content
Connect Scalr with your tenant subdomain and an API token to sync account users, environments and workspaces, 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 every user of your Scalr account with their full name, username, email and the date they were created, and respects Scalr’s own status — a user Scalr reports as anything other than active is shown as Inactive. Scalr’s users endpoint returns no role, so every user is shown as Member; service accounts live on a separate endpoint and never appear. Scalr reports no MFA state, so the MFA column shows Unknown.
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 Scalr user roster — names, usernames, emails, status and creation dates — which appears on your Access page; and your Scalr environments and workspaces, which appear on your Inventory page with each environment’s status and each workspace’s Terraform version and auto-apply setting.It calls these Scalr endpoints on https://<subdomain>.scalr.io:
  • /api/iacp/v3/users
  • /api/iacp/v3/environments
  • /api/iacp/v3/workspaces
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Scalr environment.

​
Troubleshooting

The Subdomain must be the first part of your Scalr URL — for acme.scalr.io enter acme — and the token must belong to a user of that account. A token that expired (Scalr admins can cap token lifetimes at up to one year) or was revoked is rejected the same way. Create a new token and connect again.
Scalr assigns permissions through access policies rather than a user-level role, and its users endpoint carries no role field. Check what each person can do under IAM in the Scalr console.
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.