Skip to main content
Connect Airbyte Cloud with an application’s Client ID and Client Secret to sync organization users, workspaces and connections, 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 users of one Airbyte organization — the one with the lowest organization ID among those the application can see — with their name and email. Airbyte’s users endpoint exposes no role, status, join date or MFA state, so every user is shown as Member, Active and MFA Unknown, and each row is stamped with the date of the sync. Treat the page as a membership list, not a permissions report.
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 Airbyte organization user roster — names and emails — which appears on your Access page; and your Airbyte workspaces and connections, which appear on your Inventory page with each workspace’s data residency and each connection’s status.It calls these Airbyte endpoints:
  • /v1/applications/token (exchanges the Client ID and Secret for a short-lived access token)
  • /v1/organizations
  • /v1/users?organizationId={id}
  • /v1/workspaces
  • /v1/connections
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Airbyte environment.

​
Troubleshooting

The Client ID and Client Secret look alike and are easy to swap; DSALTA refuses a pair where both fields hold the same value, and Airbyte refuses a swapped pair at the token exchange. Copy each value into its own labelled field. A deleted application is rejected the same way — create a new one and connect again.
An application’s token carries the permissions of the user who created the application. Create the application as an organization Admin, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Airbyte.
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.