How-To Guides / Admin

Connect an Identity Source

Bring in identity evidence first, review the access Telara proposes, then connect the work apps those identity systems already know about. This is the first-run setup a new admin sees.

Admin

First-run setup

Why identity first

What this step is for

Telara accounts are admin-provisioned, not self-serve — an admin invites people rather than everyone signing up on their own. Connecting an identity provider first (Microsoft Entra ID or Google Workspace / Cloud Identity) gives Telara real evidence of who's in your organization and what teams they belong to, so the access it proposes for each integration you connect afterward is grounded in that evidence rather than guessed.

Walkthrough

Set up first-run identity

Open first-run setup

A newly provisioned admin lands here automatically. You can also reach it from Settings at any time to add another identity source.

Connect an identity provider

Choose Microsoft Entra ID or Google Workspace / Cloud Identity and complete the provider's consent flow. Telara reads who exists and which teams they're in — it doesn't need or ask for your provider's admin credentials directly.

Review what connected

Once a source connects, its name appears with a confirmation, and the page shows a running list of identity providers you've connected so far.

Map access

With at least one identity source connected, the “Map access” action becomes available. This is where you move from “who exists” to “what can they reach” — connecting the work apps (GitHub, Jira, Slack, and the rest of the catalog) those identity systems already know about, with Telara proposing access based on the team memberships it just read.

Note

You can skip this step and come back to it — connecting an identity source isn't required before connecting individual integrations, but doing it first means every integration you add afterward starts from real evidence about your organization instead of a blank slate.