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

# Airbyte

> Data integration platform — users & access

<Tabs>
  <Tab title="Overview">
    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.

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

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

      <Accordion title="The Access page shows fewer users than the console">
        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.
      </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">
    An Airbyte application Client ID and Client Secret (User settings → Applications). Read-only.

    **Before you begin**

    * An Airbyte Cloud account. This integration talks to the Airbyte Cloud API at `api.airbyte.com`; a self-hosted Airbyte deployment cannot be connected.
    * An organization **Admin** to create the application, so that its token can see every user.

    You will need:

    | Field             | Where to find it                             | Example                                   |
    | ----------------- | -------------------------------------------- | ----------------------------------------- |
    | **Client ID**     | Your name → **User settings → Applications** | Revealed by clicking the icon beside it   |
    | **Client Secret** | Same page                                    | Revealed the same way — a different value |

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

      <Step title="Create an application">
        In Airbyte Cloud, click your name, choose **User settings → Applications**, and click **Create an application**. Give it a name and submit. Reveal the **Client ID** and the **Client Secret** by clicking the icon beside each and copy both.

        <Warning>
          **Keep the two values apart.** They look alike but are different values, and a swapped pair fails at Airbyte's token exchange. Paste each into its own labelled field in the next step.
        </Warning>

        <Info>
          Airbyte states that an access token "represents an individual Airbyte user, and it has the same permissions as that Airbyte user" — the application inherits your role. DSALTA exchanges the pair for a token that Airbyte expires after 15 minutes, and repeats the exchange as needed; the Client ID and Secret themselves do not expire.
        </Info>
      </Step>

      <Step title="Connect Airbyte">
        Return to the connect panel, paste the Client ID and the Client Secret into their fields, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the pair when you click **Connect**, by exchanging it for an access token and listing the organizations it can see. 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 or swapped Client ID and Client Secret, a deleted application, or an application whose user belongs to no organization.

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

  <Tab title="Useful links">
    | Topic       | Link                                                                                             |
    | ----------- | ------------------------------------------------------------------------------------------------ |
    | Setup       | [Configuring API access](https://docs.airbyte.com/platform/using-airbyte/configuring-api-access) |
    | Remediation | [Role-based access control](https://docs.airbyte.com/platform/access-management/rbac)            |
    | General     | [Airbyte Cloud](https://cloud.airbyte.com)                                                       |
    | DSALTA      | [Connection error messages](/troubleshooting/connection-error-messages)                          |
  </Tab>
</Tabs>