Introduction
Pause an automation pipeline until a matching user is signed in to the device. Use this action before steps that need an active user session, so the automation does not run too early or depend on a technician timing it around a user’s login.
Wait for Logged-In User Action
From the automation pipeline in edit mode, click + and select Wait for logged-in user from the Flow category.
Configure who Level should wait for and how long the action should wait.
Wait for
Choose which active user session satisfies the action:
Any user: Continue when any user is signed in to the device.
Any administrator: Continue when an administrator account is signed in.
Specific users: Enter one or more local usernames. The action continues when any one of those users is signed in. Usernames are matched without regard to capitalization.
The default selection is Any user.
Wait timing
Choose how long the action should wait:
Wait up to: Enter a whole number and select Days, Hours, or Minutes. If no matching user signs in before the limit, the action times out and fails.
Wait indefinitely: Keep the device on this step until a matching user signs in. No timeout is applied.
New actions default to Wait indefinitely. Select Wait up to when the workflow should fail instead of waiting without a time limit.
How it works
Level checks for an active user session on the device. A value in the device’s Last logged-in user field does not satisfy this action by itself. The matching user must be signed in when the action detects the session.
When a matching session is detected, the action succeeds and the next step runs. The wait applies independently to each device in the automation, so one device can wait while other devices continue through their own pipelines.
If the wait reaches its time limit, the action fails. Use Additional options to choose whether the automation should stop or continue after the failure, and to configure retries. See Actions Overview for details.
💡 TIP: Place this action immediately before a step that needs a user session, such as a process or script that must run in the signed-in user’s context.
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 the action name, failure behavior, output variable assignment, retries, and the enabled toggle.
See Actions Overview for the full reference on options available on every action.
FAQ
What counts as a logged-in user? The action looks for a current user session reported by the device. The device must have an active matching session; a last-known username is not enough.
Can I enter more than one specific username? Yes. Add multiple usernames under Specific users. The action continues as soon as any one of them signs in.
What happens if nobody signs in before the wait limit? The action times out and fails. The On action failure setting determines whether the pipeline stops or continues.
Does Wait indefinitely ever expire? No. The action continues waiting until a matching user session is detected or the run is canceled.
Who can add or modify this action? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.