How-To Guides / Admin

Deploy a Configuration to Users

A deployment pushes a configuration to a specific audience. Users receive their connection details — and if they're using the Telara CLI, their agent tools connect automatically on next login.

Admin

Deployments

Overview

Two delivery methods

Managed via CLI (recommended)

Users run telara login and the configuration is applied automatically. No manual key copying or config file editing. Best for teams already using the Telara CLI.

Self-serve

Users receive an email with the endpoint URL, API key, and setup instructions. They configure their tools manually. Good for teams not using the CLI or for one-off manual setups.

How To

Creating a deployment

Open Capabilities → select your configuration

Open Agents → Capabilities in the sidebar and, on the Configurations tab, click the configuration you want to deploy.

Click the 'Deployments' tab

Inside the configuration detail page, open the Deployments tab to see existing deployments and create new ones.

Configuration detail page showing the Deployments tab with existing deployments and a 'New Deployment' button

Click 'New Deployment'

Click New Deployment to open the deployment wizard.

Select the target audience

Choose who this deployment is for. You can target:

All users in org— Everyone in the organization receives this configuration

A specific team— All current and future members of the selected team

A specific project— All collaborators on the selected project

Individual users— Named users you select explicitly

Deployment target selector with radio options for Org, Team, Project, and Users — with a search field for teams and users

Choose the delivery method

Select how users receive access:

Managed via CLI

The configuration is applied automatically the next time users run telara login. No email sent, no manual steps required.

Self-serve

Targeted users receive an email with the endpoint URL, their API key, and step-by-step instructions for their agent tool.

Click 'Deploy'

Review the summary — target audience and delivery method — then click Deploy.

Deployment success screen showing the target audience summary (e.g., 'Frontend Team — 12 users') and connection status

User Experience

What users see after a managed deployment

For managed CLI deployments, users don't need to do anything special. The next time they authenticate with the Telara CLI, the configuration is applied automatically:

Terminal output on next login

telara login

Authenticated as you@company.com (Acme Inc.)

Connected to Frontend Team — Read Access:

claude-code ✓ cursor ✓

No manual setup needed. The configuration name, connected tools, and active integrations are all applied from your deployment.

Connection count tracking

The Deployments tab shows how many users have actively connected to each deployment. "Deployed to" is the target count; "Connected" is how many have actually authenticated and connected their tools. Use this to follow up with users who haven't connected yet.

Revocation

Revoking a deployment

To remove access for a deployment's audience, navigate to the Deployments tab, open the deployment, and click Revoke.

What happens on revoke

The deployment is deactivated. Affected users lose access on their next tool restart — active sessions are not forcibly disconnected mid-task, but no new connections are accepted. The configuration itself is not deleted — only this deployment is revoked.