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).
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.
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
1
Open API Config
Sign in to Fivetran and go to Account Settings -> API Config.
2
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.
3
Copy both values
Copy the API Key and API Secret now.
Connect Fivetran to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations -> select Fivetran.
2
Complete the connection form
Select Continue and provide the following:
3
Confirm the connection
Select Authenticate to validate the credentials. Find the newly connected Fivetran instance on the Connected tab of your Oleria Integrations page.
Verify the integration
Confirm the Fivetran instance appears on the Connected tab of your Oleria Integrations page. After the first sync completes, you can review the discovered accounts, teams, and roles in your Oleria workspace.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.
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 per-user API access status - Fivetran’s user list doesn’t show which users have API keys, so Oleria shows API access as not granted for every Fivetran user. The API key this integration uses is an account-wide credential and isn’t tied to a user 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.

