For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuring AI Agents

Configure when agents run, how approvals work, and provisioning behavior for each agent type.

Understanding Agent Configuration

Each agent type has a configuration panel on the right side of the detail page. Options vary by agent but typically include:

  • Schedule - When the agent runs (daily, weekly, etc.)

  • Approval - Who must approve and how (for agents that require approval)

  • Provisioning - Access duration, auto-approval (for app access and similar agents)

  • Agent-specific options - Thresholds, ticket desk, filters, etc.

Configuring Agent Settings

  1. Open the agent detail page.

  2. Use the configuration panel on the right.

  3. Change options (schedule, approval, thresholds, etc.).

  4. Click Save to apply.

Agent detail page with configuration panel

Setting Agent Schedules

In the Run Schedule section:

Recurring schedules

  • Frequency - Daily, Weekly, Monthly, Quarterly (every 3 months), Semi-annually (every 6 months), Annually

  • Day - For weekly: day of week, for monthly/quarterly/semi-annually/annually: day of month (e.g., first, last, specific day)

  • Time - Hour and minute

  • Timezone - When the schedule runs in local time

Cron-based schedules

Agents use cron expressions internally. The UI exposes frequency, day, time, and timezone, these are converted to a 5-field cron expression for the backend.

One-time runs

Agents can be run manually. Use the Run button (or Run dialog) to trigger a one-time execution. This does not affect the schedule.

Run Schedule section (frequency, day, time, timezone)

Configuring Agent Approval Workflows

For agents that require approval (e.g., Application Access Request, Group Membership Management, Employee Account Termination):

Approval strategy

Strategy
Description

Require approval from all

Every listed approver must approve.

Require approval from one of

Any one approver can approve.

Escalate if first approver doesn't respond

First approver is tried, if no response within the timeout, escalation occurs.

Approvers

  • Role-based - Direct manager, app owners, IT approvers, budget approvers, etc. (options vary by agent)

  • Employee-based - Specific people from the employee directory

Add up to 10 approvers. Configure per agent based on available role options.

Timeout

Set how many days (1–7) to wait for approval before timeout or escalation.

Reminders

Enable reminders (first and second) at configurable intervals (e.g., 4 hours, 24 hours) to nudge approvers.

Approval strategy and approvers

Last updated

Was this helpful?