How-To Guides / User

Use Permission Policies

Permission policies define what actions your agents can take. Policies are created and managed by your admins — here is how to find the ones available to you and put them to work on your configurations.

User

Permissions & Policies

Policies are created and managed by admins. As a member, you can attach any policy available for your scope to configurations you control — but creating, editing, or retiring a policy is an admin action. If you need a new or changed policy, ask an admin; admins can also stage a draft for review.

Permission Levels

The three permission levels

Every action in a connected integration can be assigned one of three permission levels.

Auto-approve

The agent takes the action immediately with no interruption. Use this for low-risk, repetitive operations.

Require approval

The agent pauses and notifies you (or a designated reviewer) before proceeding. Use this for actions with meaningful consequences.

Blocked

The action is never taken, even if requested. Use this to create hard guardrails around sensitive or irreversible operations.

Steps

How to use permission policies

See which policies are available to you

Open the Telara dashboard and go to Agents → Capabilities in the left sidebar, then the Policiestab. You'll see the policies available for your scope: org-wide policies plus any scoped to your team, a project you belong to, or you specifically.

Attach a policy to a configuration you control

Which policies you can attach is decided by each policy's scope — an org-wide policy can be attached by anyone, while a team, project, or user policy can only be attached within that exact scope. See the next section for where to attach.

Create keys under that configuration

Any key you create for a configuration is bound to it and governed by the policies attached to it — agents using that key follow those permission levels automatically.

Ask an admin when nothing fits

If no available policy covers what you need, ask an admin for a new or adjusted one — admins can also prepare a draft for review before it takes effect. Tell them which actions you want auto-approved, which should require approval, and which should be blocked.

Attaching to a Configuration

Attach a policy to your configuration

Found a policy that fits? Attach it to any configuration you control: navigate to Capabilities → Configurations → [Your Config] → Policies → Attach Policy.

Policy attachment modal in configuration settings

Common Patterns

Common policy shapes to look for — or ask your admin for

Search only

All write and action operations are blocked. Only search and read actions are allowed. Good for research or read-only workflows.

Create but don't delete

Creates are auto-approved, updates require your approval, and deletions are blocked. Balances speed with safety.

Supervised mode

Everything requires your approval before the agent acts. Best when you're getting started and want full visibility into every action.