> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fivetran

> Connect Fivetran to Oleria to bring user, team, and role standing from your data-integration platform into your identity and access graph.

Connect Fivetran to Oleria to extend visibility into who has access to your automated data-integration (ELT) platform. Oleria reads users, teams, and roles from the Fivetran REST API using an API Key and Secret pair, so accounts and their standing in Fivetran are visible alongside the rest of your identity and access graph. This page provides step-by-step guidance for connecting Fivetran to Oleria.

## What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from Fivetran:

* **Accounts** - every user in your Fivetran account, including their account-wide role.
* **Teams** - Fivetran's group construct, including which users belong to each team.
* **Roles** - Fivetran's role catalog, covering the 5 account-wide roles (Account Administrator, Account Analyst, Account Billing, Account Reviewer, Destination Creator) that a user or a team can hold, and each team member's own standing within that team (Team Manager or Team Member).

<Note>
  Fivetran is a data-integration (ELT) tool, not an identity or HR system of record. Oleria connects to its admin-console identity surface only - its core data-pipeline objects (connectors, destinations, transformations) are out of scope.
</Note>

## Prerequisites

* A Fivetran Account Administrator, to generate an API Key and Secret pair (or an org-wide System Key)
* Admin access to the Oleria workspace

## Generate an API Key and Secret in Fivetran

<Steps>
  <Step title="Open API Config">
    Sign in to Fivetran and go to **Account Settings** -> **API Config**.
  </Step>

  <Step title="Generate a key pair">
    Generate an API Key and API Secret pair. Alternatively, ask an account admin to mint an organization-wide System Key - it authenticates the same way and works identically for the Oleria connection.
  </Step>

  <Step title="Copy both values">
    Copy the API Key and API Secret now.

    <Warning>
      Fivetran shows the Secret only once, at creation time. If you lose it, you must generate a new key pair and update the connection in Oleria.
    </Warning>
  </Step>
</Steps>

## Connect Fivetran to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations** -> select **Fivetran**.
  </Step>

  <Step title="Complete the connection form">
    Select **Continue** and provide the following:

    | Field      | Notes                                                                     |
    | :--------- | :------------------------------------------------------------------------ |
    | API Key    | Required. The API Key half of the pair generated in the previous section. |
    | API Secret | Required. The API Secret half of the pair.                                |
  </Step>

  <Step title="Confirm the connection">
    Select **Authenticate** to validate the credentials. Find the newly connected Fivetran instance in your Oleria workspace connected integrations.
  </Step>
</Steps>

## Verify the integration

Confirm the Fivetran instance appears in your Oleria workspace connected integrations. After the first sync completes, you can review the discovered accounts, teams, and roles in your Oleria workspace.

<Note>
  If the API Key or Secret is later revoked or rotated in Fivetran, generate a new pair and update the connection in Oleria - a revoked credential will cause the sync to fail.
</Note>

## Known limitations

* **Read-only** - this integration reads accounts, teams, and roles. It does not make any changes in Fivetran.
* **No MFA or SSO enrollment data** - Fivetran's API exposes no per-user or company-level MFA or SSO field. Oleria reports these as unavailable, not as a false negative.
* **No API-access flag** - this integration reads the bulk user list, which doesn't include per-user API-key status, so this field is always reported as not granted. The API Key/System Key that authenticates this very connection is itself an account-wide credential with no owning-user record in Fivetran.
* **No activity** - Fivetran's Audit Trail is a separate, plan-gated feature delivered outside the REST API this connector uses, so no activity is discovered.
* **Data-pipeline objects out of scope** - connectors, destinations, transformations, and other pipeline-management objects are not discovered; this integration covers identity and access only.

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).