Introduction
Display a prompt to the end user on a device and wait for them to approve before the pipeline continues. Use this action when a task requires the user's awareness or consent before execution — for example, confirming a major OS upgrade before it begins.
This is distinct from Wait for Approval, which pauses for a technician to approve. User Approval pauses for the end user on the device.
User Approval Action
From the automation pipeline in edit mode, click + and select User approval from the Notifications category.
End User Example
Question
The message displayed to the end user in the approval prompt. Required.
Write this as a clear, plain-language question the user can act on.
Click (x) to insert a variable, system variable, or custom field reference — useful for making the message specific to the device or context.
Example: Your device is scheduled for an upgrade from Windows 10 to Windows 11. Do you want to proceed now?
Prompt frequency (in minutes)
How often the prompt re-appears if the user dismisses it without approving. Default is 60 minutes.
Force compliance
Enable Force compliance to require the user to eventually approve, even if they keep dismissing the prompt. When enabled, choose an enforcement method:
Enforcement method | Behavior |
Max attempts | Prompt is automatically accepted after the user dismisses it a set number of times |
Max time | Prompt is automatically accepted after a set number of minutes have passed |
⚠️ WARNING: Force compliance will proceed with the automation even if the user never explicitly approves. Only enable it for tasks where delayed execution is more disruptive than proceeding without consent — and make sure the Question text communicates that the action will happen automatically if they don't respond.
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.
See Actions Overview for the full reference on additional options available on every action.
FAQ
What happens if no user is logged in when the prompt fires? The prompt still appears — it's displayed on the login screen. If no user is present to approve it and you need the pipeline to eventually proceed, enable Force compliance with Max time to ensure the action completes after a set period.
What happens if the user dismisses the prompt without approving and force compliance is off? The prompt re-appears after the configured frequency interval. The pipeline remains paused until the user approves.
When does force compliance kick in? With Max attempts: the pipeline proceeds after the user has dismissed the prompt that many times. With Max time: the pipeline proceeds after the configured number of minutes has elapsed since the first prompt appeared.
Who can add or modify User Approval actions? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.