Skip to main content
Telara

Integrations / Glean

Glean logo

Glean

Glean — Insights API exposing per-user activity (searches, AI assistant usage) across the enterprise knowledge workspace. Spend connector for the AI Platform Spend Governance feature.

OAuth 2.0
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

A Glean Enterprise workspace.
An admin who can issue an API token.

Vendor setup

Get the credential

1
Create an admin token
In Glean, open the admin console and issue an API token that can read insights.
2
Paste in Telara
Settings → Integrations → Glean.

In Telara

Connect in Telara

OAuth 2.0

Tenant-specific Glean Client API authorization-code metadata. Fetch the tenant authorization-server metadata and verify the Insights scope/API path before enabling browser authorization; retain the admin API-token route for unattended pulls.

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

Glean admin-issued API token (Glean Enterprise). Authorizes the /insights endpoint. FlexCredits $ consumption is dashboard/CSV only — not exposed by Insights — so cost here is seat/credit-derived.

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

Fields Telara asks for
  • API key

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • searches
    count
  • chats
    count
  • ai_answers
    count
  • agent_runs
    count
  • mcp_calls
    count
  • days_active
    count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

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.

This catalog entry does not declare extra semantic-search exclusions.

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

Dashboard CSV export is not this connector. Telara reads the insights API only.
A non-admin token cannot read org insights.