Run actions without user confirmation

By default, write actions in Glean require explicit user confirmation before execution. Glean proposes the action, the user approves it, and then the action runs.

However, for background agents and scheduled agents, this confirmation step blocks execution because no user is present to approve the action. Enabling the Run without user confirmation setting removes this blocker for automated contexts.

What this setting controls

When you enable this setting for a tool, Glean executes write actions in the background without waiting for user approval if:

• The action is invoked by a scheduled agent running on a timer.
• The action is invoked by a background agent triggered by an event such as a new Slack message or a webhook.
• The agent is running in auto mode without an active user session.

note

When the same action is invoked interactively, meaning a user is present in Glean or in an active agent session, the confirmation prompt still appears as normal, regardless of this setting.

Configuration steps

1. Go to the Glean Admin Console.
2. Navigate to Platform → Actions.
3. Select the action pack you want to configure and open the Configuration tab.
4. Click Edit settings under the Enable actions section.
5. Click Agents and set Run without user confirmation to Yes.
6. Click Save.

note

This setting applies to the entire action pack, not to individual actions within it. If you want to allow background execution for only specific actions, create a separate action pack instance scoped exclusively to those actions.

Security considerations

Enabling this setting allows write operations such as creating tickets, posting comments, or updating records to occur automatically without human review. Before enabling this feature, ensure you:

• Test thoroughly: Verify the instructions of the agent are tightly scoped and tested in an interactive session first.
• Restrict visibility: Limit the visibility scope of the tool to only the specific users or service accounts the agent runs as.
• Disable destructive actions: Use the per-tool enable or disable toggle to turn off any destructive actions, for example, delete, close, archive within the pack.

Run without user confirmation vs. Inline execution

Both settings live in the same Edit settings panel per action pack. They operate independently and you can require user confirmation for interactive use while simultaneously allowing background execution for automated workflows.

Setting	Context	Behavior
User Confirmation (Default)	Interactive sessions	The user must review and approve a confirmation card before each write action.
Run without user confirmation	Automated sessions	Background and scheduled agents execute write actions automatically.

For more details on interactive confirmation behaviors, see Allowing in-line execution of write actions.

If you need help, contact the Glean support team.