Identify Users in Bypass Mode Crate
Last updated
Was this helpful?
If you’re new to Crates, read through our introductory Crate documentation here. Find the Crate in our Crate Marketplace.
Our Identify Users in Bypass Mode Crate identifies all users that are in bypass mode and creates a PSA ticket to ensure that the granting of bypass mode is intentional and tracked. The Crate’s workflow has a weekly cron trigger. Guarantee that any user in bypass mode is regularly identified, and not missed or forgotten. You also have the option to set an email send to notify you if the workflow fails.
Before unpacking this Crate:
Navigate to Marketplace > Crates in the left side menu of the Rewst platform.
Search for Identify Users in Bypass Mode

Click on the Crate tile to begin unpacking.
Click Unpack Crate.
Enter your estimated time saved.
Click Unpack.

To test this Crate, you'll need to adjust the cron trigger's schedule to a few minutes in the future, then adjust it back to your regular schedule after the test. Alternatively, you could wait until the regularly scheduled run occurs and check your result, which would not require you to update the cron trigger schedule.
Navigate to Automations > Workflows.
Search for Duo: Identify Users In Bypass Mode.
Click on the workflow to view it in the Workflow Builder.
Update the timing of the cron trigger as desired. Note that when entering the time into the Cron Schedule field, the correct format is minutes followed by hour. For example, 18 3, not 3 18. The trigger has a default setting to run at 12 AM EDT on Fridays.
Click Save Trigger.
Got an idea for a new Crate? Rewst is constantly adding new Crates to our Crate Marketplace. Submit your idea or upvote existing ideas here in our Canny feedback collector.
Navigate to Automations > Workflows.
Search for Duo: Identify Users In Bypass Mode.
Click on the workflow to view it in the Workflow Builder.
Scroll over the workflow and locate the send_error_to_email task.
Click into the task. Navigate to the Parameters tab.
Update the desired email address in the fallback_email field.
Last updated
Was this helpful?
Was this helpful?
