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

# Fivetran

> Data pipelines — users & access

<Tabs>
  <Tab title="Overview">
    Connect Fivetran with an API key and secret to sync account users, connections and destination groups, 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>

    <Info>
      **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**.
    </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 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

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        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.
      </Accordion>

      <Accordion title="The Access page shows fewer users than the dashboard">
        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.
      </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/compliance/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 Fivetran API key and secret. The account is detected automatically. Read-only.

    **Before you begin**

    * A Fivetran account, and a user in it who can see all users — the key inherits that user's permissions, so generate it as an **Account Administrator**.

    You will need:

    | Field          | Where to find it                               | Example    |
    | -------------- | ---------------------------------------------- | ---------- |
    | **API Key**    | Your username → **API Key → Generate API key** | Shown once |
    | **API Secret** | Same page                                      | Shown once |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Fivetran**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Generate an API key">
        In the [Fivetran dashboard](https://fivetran.com/dashboard), click your username at the bottom left, click **API Key**, then **Generate API key** (or **Generate new API key** if one already exists). Copy both the key and the secret.

        <Info>
          Fivetran shows the pair once: "Make a note of the key and secret as they disappear once you close the page or navigate away." Generating a new key later invalidates the previous pair, which breaks the DSALTA connection until you reconnect with the new one.
        </Info>
      </Step>

      <Step title="Connect Fivetran">
        Return to the connect panel, paste the API key and the API secret into their fields, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the pair when you click **Connect**, by reading the account record. 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.** Wrong key or secret, or a pair that was replaced by a newer one.

      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/fivetran/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Fivetran access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/fivetran/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Fivetran access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                      |
    | ------- | ----------------------------------------------------------------------------------------- |
    | Setup   | [Fivetran REST API — getting started](https://fivetran.com/docs/rest-api/getting-started) |
    | General | [Fivetran dashboard](https://fivetran.com/dashboard)                                      |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)                   |
  </Tab>
</Tabs>