Skip to main content
Connect Bugsnag (SmartBear Insight Hub) with a personal auth token to sync organization collaborators and projects, 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 collaborators of one Bugsnag organization — the one with the lowest ID among those the token can see — with their name, email, whether they are an organization Admin or a Collaborator, and the date they were added. People with a pending invitation are left out. Bugsnag reports no account status, so every collaborator is shown as Active. Bugsnag does report two-factor authentication per collaborator, so the MFA column shows Yes, No, or Unknown when Bugsnag returns 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 Bugsnag collaborator roster — names, emails, admin flag, two-factor state and join dates — which appears on your Access page; and the organization’s projects, which appear on your Inventory page with their language, open error count and collaborator count. Error events themselves are not read.It calls these Bugsnag endpoints:
  • /user/organizations
  • /organizations/{id}/collaborators
  • /organizations/{id}/projects
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Bugsnag environment. Bugsnag rate-limits its Data Access API per token; when it asks DSALTA to wait, DSALTA waits and retries once.

​
Troubleshooting

The token is invalid or was revoked under My account settings → Personal auth tokens. Generate a new token and connect again. A project notifier API key (the one you put in the SDK) is not a personal auth token and does not work here.
A personal auth token sees every organization its owner belongs to, and DSALTA syncs the first by ID; there is no field to pin another. Generate the token as a user who belongs only to the organization you want reviewed, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Bugsnag.
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.