Before
An administrator likely had to retrieve the active-user list and work through accounts individually. For each user, they needed to initiate a sign-out of web and device sessions, reset sign-in cookies, and track whether the full organization had been processed.
How it works
- Start from an email-triggered or scheduled execution and retrieve the organization’s active users.
- Process each user individually, signing them out of web and device sessions and resetting their sign-in cookies.
- Stop on a failed user action; otherwise, confirm that the organization-wide sign-out completed successfully.
Workflow details
- Trigger and scope: The flow starts when an email-triggered execution occurs, and it can also be used as a regularly scheduled process according to the playbook notes.
- User discovery: It retrieves the active users in the organization, using a suspended-user filter so that the workflow focuses on currently active accounts.
- Session invalidation: The workflow processes each returned user individually and signs them out of all web and device sessions while resetting their sign-in cookies.
- Completion handling: Each user action is configured to stop the execution if it fails, preventing the flow from silently continuing after an unsuccessful sign-out operation.
- Result confirmation: After the user list has been processed successfully, the workflow returns a confirmation that the general sign-out was completed.
What changed
The sign-out operation now begins from a single trigger, automatically identifies active users, and applies the same session invalidation action to each account. Completion is confirmed only after the user-processing loop finishes successfully, with failures stopping the execution instead of being overlooked.
Work removed
Retrieving the active-user list for each run, opening or selecting users one by one, initiating individual session sign-outs and cookie resets, and manually tracking completion across the user list.
Expected outcome
Each run removes one individual sign-out operation per active user from the administrator’s workload; the exact time saved depends on the organization’s active-user count and prior process.
