Skip to main content
Connect Fivetran with an API key and secret to sync account users, connections and destination groups, 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 your Fivetran account with their name, email, Fivetran role and the date they were created, and respects Fivetran’s own active flag — a deactivated user is shown as Inactive. People who have been invited but have not yet joined are left out. Fivetran reports no MFA state, so the MFA column shows Unknown.
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 Fivetran user roster — names, emails, roles, active state and creation dates — which appears on your Access page; and your Fivetran connections and destination groups, which appear on your Inventory page. Each connection row shows its source service, sync and setup state, whether it is paused, the destination group it belongs to and the email of the user who connected it.It calls these Fivetran endpoints:
  • /v1/account/info
  • /v1/users
  • /v1/groups
  • /v1/connections
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Fivetran environment.

​
Troubleshooting

Wrong key or secret, or a pair that was invalidated by generating a new one — Fivetran keeps one key per user, and Generate new API key replaces the old pair. Generate a key again, then connect again.
The key inherits the permissions of the user who generated it. Generate it as an Account Administrator so that every user is visible, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Fivetran.
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.