> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scalr

> Terraform automation platform — users & access

<Tabs>
  <Tab title="Overview">
    Connect Scalr with your tenant subdomain and an API token to sync account users, environments and workspaces, and run access reviews. Read-only.

    <Info>
      **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.
    </Info>

    <Info>
      **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**.
    </Info>

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

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

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        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.
      </Accordion>

      <Accordion title="The Access page shows every user as Member">
        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.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        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.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        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](/guides/compliance/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        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.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **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](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        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.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    Your Scalr tenant subdomain plus an API token. Read-only.

    **Before you begin**

    * A Scalr account (`<subdomain>.scalr.io`), and a user in it whose access policy lets them list users — the token acts as that user.

    You will need:

    | Field         | Where to find it                 | Example                  |
    | ------------- | -------------------------------- | ------------------------ |
    | **Subdomain** | The first part of your Scalr URL | `acme` for acme.scalr.io |
    | **API Token** | Profile menu → **API tokens**    | Created per user         |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Scalr**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Create an API token">
        In Scalr (`https://<subdomain>.scalr.io`), open your profile menu, choose **API tokens**, create a token, and copy it.

        <Info>
          Scalr account admins can enforce a maximum token lifetime through security rules, up to one year. If your account does, the DSALTA connection breaks when the token expires; create a new token and reconnect.
        </Info>
      </Step>

      <Step title="Find your subdomain">
        Your tenant subdomain is the first part of your Scalr URL — for `acme.scalr.io` enter `acme`. DSALTA also accepts the full hostname and trims it.
      </Step>

      <Step title="Connect Scalr">
        Return to the connect panel, paste the subdomain and the API token, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the pair when you click **Connect**, by listing the account's users. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** Wrong subdomain, or an expired or revoked token.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check                                                                                                                | Severity | What it verifies                                                                 |
    | -------------------------------------------------------------------------------------------------------------------- | -------- | -------------------------------------------------------------------------------- |
    | [User access to Critical System should be valid](/integrations/scalr/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Scalr access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/scalr/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Scalr access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic       | Link                                                                                        |
    | ----------- | ------------------------------------------------------------------------------------------- |
    | Setup       | [Scalr API overview](https://docs.scalr.io/reference/api-overview)                          |
    | Remediation | [Identity and access management](https://docs.scalr.io/docs/identity-and-access-management) |
    | General     | [Scalr](https://scalr.io)                                                                   |
    | DSALTA      | [Connection error messages](/troubleshooting/connection-error-messages)                     |
  </Tab>
</Tabs>