Skip to main content
Connect GlitchTip with an auth token to sync organization members, projects, teams, uptime monitors, and open error issues, and run access reviews. Read-only. Data feeds into your Access accounts, Inventory and Incidents pages.
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 members of every GlitchTip organization the token’s user belongs to, one row per email address, with their name (or their username or email address when the profile carries no name), their email, their organization role as GlitchTip names it (for example Owner, Manager, Admin or Member, or Member when none is reported) and the date they were added to the organization. When the token sees several organizations, each role is suffixed with the organization it applies to, and a person who belongs to more than one has their roles joined on a single row. Invitations that have not been accepted are left out. A member whose GlitchTip user account is inactive is shown as Inactive; every other member is shown as Active. GlitchTip reports no per-user MFA state, so the MFA column is blank (shown as a dash).
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 GlitchTip organization member roster — names, usernames, emails, roles, account state and membership dates — which appears on your Access page; your GlitchTip projects (platform, first-event date or no events yet, and whether they are public), teams (listed by their slug, with their member count) and uptime monitors (type, target URL, up or down state when GlitchTip reports one, and interval), which appear on your Inventory page; and each organization’s unresolved error issues, which appear on your Incidents page. Each issue arrives with its short ID and title, and its culprit, project, event count, number of users affected and last-seen time in the description. Its severity follows the issue level — fatal is Critical, error is High, warning is Medium and anything else is Low — and every issue is typed Application Error and shows Open, because only unresolved issues are read: an issue that has been resolved or ignored in GlitchTip is never imported. At most 1,000 issues per organization are read. Incidents fills once an unresolved error issue exists in one of your projects. Members’ last-login times, password and SSO sign-in details, releases, deploys and commits are not read.It calls these GlitchTip endpoints under https://<host>/api, where the host is app.glitchtip.com unless you entered another:
  • /0/ (the token’s own record and scopes, used to validate)
  • /0/organizations/
  • /0/organizations/{slug}/members/
  • /0/organizations/{slug}/projects/
  • /0/organizations/{slug}/teams/
  • /0/organizations/{slug}/monitors/
  • /0/organizations/{slug}/issues/ (with the query is:unresolved)
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your GlitchTip environment.

​
Troubleshooting

The token was not accepted by the host — a bad token, or a valid token sent to the wrong host, because a US token is not accepted by eu.glitchtip.com and the other way round. Otherwise the token is missing the member:read or org:read scope, and the message names the missing scope: without member:read the members cannot be listed, and without org:read the organization cannot be discovered. A project DSN key is not an auth token. Create a token with both scopes under Profile → Auth Tokens, check the host, and connect again.
Projects, teams, uptime monitors and issues are read best-effort after the member roster: a failure on one of those calls leaves that part of the page empty without failing the sync. Projects need the project:read scope, teams team:read and issues event:read — a token without one of them leaves that surface empty with no error. A new organization has no projects, teams or monitors until you create them. Click Sync from integrations on the Integrations page to retry.
GlitchTip reports the member’s user account as inactive. The member stays on the Access page, marked Inactive, and is not counted as retaining access by the offboarding check. Remove the member from the organization under its Settings → Members to take them off the roster.
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.