Integrations / Saviynt Enterprise Identity Cloud

Saviynt Enterprise Identity Cloud

Saviynt Enterprise Identity Cloud identity governance data for users, endpoints, connections, SAV roles, and role membership.

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Saviynt EIC tenant you can administer.

Admin who can create an API user / OAuth client in Saviynt.

Vendor setup

Get the credential

Open API configuration

In Saviynt, go to Admin → Settings → API (or the OAuth client page your tenant uses).

Create a client or token

Create an API user. Copy the bearer token or client credentials. Also copy the tenant URL (the *.saviyntcloud.com host).

Paste in Telara

Settings → Integrations → Saviynt Enterprise Identity Cloud. Paste the token and the tenant root Telara asks for.

In Telara

Connect in Telara

OAuth 2.0

Saviynt password-grant OAuth metadata. The credential must be a customer-provisioned integration account and needs a refresh-token persistence path before it can be used live. No browser authorization URL is declared; client_credentials support on EIC 25.x remains unverified.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for

Base Url
Username
Password

API key

Saviynt API bearer token. Store base_url as the tenant root, for example https://example.saviyntcloud.com.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API token

Knowledge

What gets indexed

Resource	Coverage
Identity	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Identity	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Identity.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

On-prem Saviynt URLs must be reachable from Telara.

A client missing identity-read produces an empty directory.