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

# Rollbar

> Error tracking — users & access

<Tabs>
  <Tab title="Overview">
    Connect Rollbar with an account access token to sync account users and projects, 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>

    <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 Rollbar user roster — usernames and email addresses, which appears on your **Access** page; and your Rollbar resources, which appear on your **Inventory** page. Rollbar's user list carries no role or account status — permission levels live on Teams, which DSALTA does not call — so every member is listed as an active Member.

    It calls these Rollbar endpoints:

    * `/users`
    * `/projects`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Rollbar environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection fails to validate">
        Invalid access token.
      </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/data-library/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">
    A Rollbar Account Access Token with read scope. Read-only.

    **Before you begin**

    * A Rollbar account (free plan works)
    * An Account Access Token with read scope (NOT a Project Access Token — that can't list users/teams)

    You will need:

    | Field                    | Where to find it                                             | Example                                     |
    | ------------------------ | ------------------------------------------------------------ | ------------------------------------------- |
    | **Account Access Token** | [Open](https://docs.rollbar.com/reference/getting-started-1) | `Rollbar account access token (read scope)` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Rollbar**, and click **Connect** to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
      </Step>

      <Step title="Open Account Access Tokens">
        In Rollbar, open **Account Settings** → **Account Access Tokens**. This is an account-level token, not a project-level one.
      </Step>

      <Step title="Create a read-scoped token">
        Create a new Account Access Token with read scope, then copy it.

        On an account access token the `read` scope is enough — Rollbar defines it as "Supports all `GET` operations at the account level". DSALTA never needs the `write` scope, which covers POST, PUT, PATCH and DELETE.
      </Step>

      <Step title="Connect Rollbar">
        Paste your Account Access Token, then click Connect.

        <Tip>DSALTA validates the token by listing your projects (`GET /api/1/projects`), which is an account-level call. A project access token — even one with read scope — will be rejected here, which is the usual cause of "Invalid access token".</Tip>
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you click **Connect**. 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.** Invalid access 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/rollbar/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Rollbar access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/rollbar/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Rollbar access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                                   |
    | ------- | ------------------------------------------------------------------------------------------------------ |
    | Setup   | [Rollbar API — account access tokens and scopes](https://docs.rollbar.com/reference/getting-started-1) |
    | General | [Rollbar website](https://rollbar.com)                                                                 |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)                                |
  </Tab>
</Tabs>