Skip to main content
8 min read

Configure a Persona Agent

Configure a Persona Agent

After you create a persona agent, open it to give it tools and guardrails. This page covers each tab on the agent's page and both ways to attach an integration.

Available for roles: Admin Workspace Admin

Scope: Workspace

Open an agent​

  1. Open Workspace Settings -> Agents and automation -> Agents.
  2. Click the agent's name.

The top of the page shows the agent's chat handle (for example @jira-assistant), its status, and Talk to Agent. The More actions menu holds Delete agent.

Below that are these tabs:

TabUse it to
Agent ActivitySee recent conversations and runs
PersonaView or edit the system prompt
ModelsAssign LLMs to the agent
PoliciesAssign or revoke governance policies
IntegrationsAttach or detach integrations and see their tools
ToolsChoose which tools run without a human approval step
PII redactionAdd per-agent redaction rules
WorkflowsSee which workflows use this agent
Remote RunnersAttach runners that execute tools inside your network
Danger ZoneStop or restart the agent

Agents installed by an app do not show Persona, because the app manages it.

Some deployments turn off advanced agent features. In those deployments, Models, Policies, Workflows, and Danger Zone are hidden, Delete agent is hidden, and Talk to Agent is shown but disabled.

Attach an integration​

Every agent has a few built-in tools, such as knowledge search, runbooks, notes, and web search. To reach your other systems, it needs integrations attached to it. Attaching does not copy credentials. The agent uses the integration's saved connection.

You can attach from either side. Both give the same result.

From the agent​

  1. Open the agent and select the Integrations tab.
  2. Under Attach an integration, pick an integration from the list.
  3. Click Attach.

The integration appears as a card with a tool count. Click the tool count to see each tool and its description.

The list only shows enabled integrations that are not already attached. If the Attach an integration control is missing, every enabled integration is already attached, or none is connected yet. Connect one under Workspace Settings -> Connections -> Integrations.

From the integration (Attach to)​

When you connect or edit an integration under Workspace Settings -> Connections -> Integrations, the form ends with an Attach to field.

  1. Click Attach to (placeholder Select agents or apps).
  2. Pick one or more entries. The list has two groups:
    • Apps: enabled apps such as Aiden DevOps and Aiden SRE. Attaching to an app makes the integration available to that app.
    • Agents: agents in the workspace, including persona agents you created.
  3. Click Add integration (or Save integration / Save changes when editing). Aiden attaches it to everything you picked.

Attach to is optional. You do not need an agent before you connect an integration:

You want toDo this
Connect the tool now and decide laterLeave Attach to empty and save. Attach it from an agent's Integrations tab later
Let the Aiden DevOps or Aiden SRE app use itPick the app under Apps
Give a persona agent accessPick the agent under Agents. If the agent does not exist yet, create it first, then edit the integration and pick it, or attach from the agent

Attach to only adds attachments. Removing an entry while you edit an integration does not detach it. To detach, use Detach on the agent's Integrations tab.

If Attach to lists no agents, none have been created yet. If the field is disabled, there are no agents and no attachable apps in the workspace.

Detach an integration​

On the agent's Integrations tab, hover over the integration card and click Detach. The agent can no longer use that integration's tools. The integration itself stays connected for other agents and apps.

Tools show as a count but no list​

If a card shows a tool count but no tool names, go to Workspace Settings -> Connections -> Integrations, open the integration's More actions menu, and click Refresh. Aiden discovers the tool details again.

Auto-approve tools​

When someone chats with an agent, every tool call pauses for human approval by default. The conversation shows an approval card with Approve and Reject, and the request also appears in Approvals.

Auto-approve tools that are safe to run on their own, such as read-only lookups:

  1. Open the agent and select the Tools tab.
  2. Click Manage auto-approved tools.
  3. Search or filter by name, description, or pattern.
  4. Select the tools that should skip approval. Use Select all in list or Deselect all in list for bulk changes.
  5. Click Save.

The Auto-Approved list shows what now runs without asking. All other tools still require approval in chat.

Integration tools are listed with the integration's name in front. For example, the jira_get tool of an integration named jira-prod appears as jira-prod_jira_get. If the list says no tools are available, attach an integration first.

Recommended starting point:

  • Auto-approve: read-only tools (get, list, search, describe).
  • Require approval: tools that create, update, transition, delete, deploy, or run commands.

Deny policies still block auto-approved tools. A policy that only requires approval does not, because auto-approve satisfies it.

Runs with no one watching​

Schedule and webhook automations, and API-triggered runs, have no person to approve tool calls. In these runs, every tool runs without approval, including tools you left off the auto-approve list. The approval is recorded as approved by system:unattended-run in the audit trail, and nothing waits in Approvals.

Only two things limit an unattended run:

  • A deny policy. Assign a policy that denies the tools the agent must never call on its own.
  • The integration's credentials. Connect the integration with an account that cannot make the change, for example a read-only account.

Set one of these up before you schedule an agent or point a webhook at it.

Assign policies​

  1. Open the agent and select the Policies tab.
  2. Under Assign a policy, pick a policy.
  3. Click Assign Policy.

To remove a policy from this agent, click Revoke next to it. Create policies first under Policies.

Choose models​

With no model assigned, the agent uses the organization's default models from LLM Providers.

To pin specific models:

  1. Open the agent and select the Models tab.
  2. Under Available Models, click a model to assign it.

Each assigned model shows its temperature and max tokens, if set. Click Remove to unassign a model.

Attach remote runners​

Attach a remote runner when the agent needs to run tools inside your network.

  1. Open the agent and select the Remote Runners tab.
  2. Under Attach a remote runner, pick a runner.
  3. Click Attach.

Click Detach on a runner to remove it. To route a single integration through a runner instead, see Use on-prem integrations with Aiden. Not every integration type can run on a runner.

Set PII redaction​

The PII redaction tab layers per-agent rules on top of the platform's redaction.

Redaction settingEffect
Platform defaultInherit the platform baseline (redaction on)
EnabledAlways redact for this agent
DisabledSend identifiers to the model without [HIDDEN] tokens

Add rules with a name and an RE2 pattern, for example employee_id and EMP-[0-9]{6}:

  • Deny rules: values matching these patterns are always redacted.
  • Allow rules: values matching these patterns are never redacted, for example infrastructure IDs. Allow always wins.

Paste sample text into the preview box to check your rules, then click Save PII policy.

Edit the persona​

  1. Open the agent and select the Persona tab.
  2. Click Edit, change the system prompt, and click Save.

See the system prompt template for what to include.

See workflows that use the agent​

The Workflows tab lists workflows that bind this agent to a stage. Click View to open one. To add the agent to a workflow, edit the workflow's stages under Workflows.

Stop, restart, or delete an agent​

  • Stop immediately: on the Danger Zone tab, turn off Agent running. In the Stop this agent (kill switch) dialog, type the agent's name to confirm. Running tasks are canceled, and new chat, event, schedule, and webhook requests are rejected until you start the agent again.
  • Restart: turn Agent running back on.
  • Delete: open More actions at the top of the page and click Delete agent.