Managing Agents as an admin

Last updated: July 13, 2026

Admins can use Agent Management to monitor, configure, and roll out agents across an organization. This is useful when you want a consistent workflow for a team, not just a personal agent owned by one user.

Open Agent Management

  1. Go to Settings.

  2. Open Agents.

You need permission to view and edit organization settings to access this page.

What admins can see

The Agent Management page shows organization and global agent templates. You can search by name or description, filter by active or inactive status, and filter by live or on-demand type.

Live vs on-demand

  • Live agents have an automatic trigger, such as a schedule, deal stage change, after-call trigger, or web trigger.

  • On-demand agents are saved workflows users run manually.

Global and organization templates

  • Global templates are Airspeed-provided templates.

  • Organization templates are templates created or shared inside your workspace.

Users may need to duplicate a template before customizing its prompt, depending on who created it and how it was shared.

Assign an agent to users

  1. Open Settings → Agents.

  2. Select the agent template row.

  3. Use the assignment panel to choose users.

  4. Set whether each user's agent should be active or inactive.

  5. Confirm the rollout.

Rollout checklist

  1. Start with one team or pilot group. Confirm the prompt and output are useful before rolling out broadly.

  2. Test delivery. Check Slack DMs, Slack channels, and email recipients.

  3. Use clear ownership. Decide who owns prompt quality, trigger settings, and follow-up actions.

  4. Review history. Use agent history to confirm the agent is running at the right time and producing actionable output.

  5. Keep templates clean. Duplicate experimental agents instead of editing a production template in place.

Permissions and data access

Agents run against the data available to the agent owner or configured user. Admin rollout does not override normal Airspeed data permissions.

When to create an organization template

Create an organization template when the workflow should be reused by multiple people, such as a manager coaching brief, weekly pipeline report, closed-won handoff, or risk alert.

Troubleshooting

I cannot see Settings → Agents

Ask an admin to confirm you have permission to view and edit organization settings.

A user is not receiving output

Confirm the user is assigned, the agent is active for that user, and the delivery method is configured correctly.

An agent is active but not useful

Review the prompt, trigger scope, output format, and recent run history. Narrow the workflow before rolling it out to more users.