Integrations / Vanta

Vanta

Vanta trust management for controls, evidence, tests, personnel, vendors, risks, and audit-readiness workflows.

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A Vanta workspace you can administer.

Vendor setup

Get the credential

Prefer Connect

Settings → Integrations → Vanta. Approve access in Vanta.

Token fallback

If your workspace cannot use the hosted button, create an API token in Vanta and paste it in Telara.

In Telara

Connect in Telara

OAuth 2.0

Vanta OAuth client credentials.

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.

API key

Vanta bearer token.

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
Compliance control	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Compliance control	Up to 1 hour	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: Compliance control.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

The token sees the workspace it was issued for. A sandbox token will not read production monitors.