> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/crates/existing-crate-documentation/identify-users-in-bypass-mode-crate.md).

# Identify Users in Bypass Mode Crate

{% hint style="info" %}
If you’re new to Crates, read through our introductory Crate documentation [here](https://docs.rewst.help/prebuilt-automations/crates). Find the Crate in our Crate Marketplace.
{% endhint %}

## What does the Identify Users in Bypass Mode Crate do?

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.

## Crate prerequisites

Before unpacking this Crate:

* Our [Duo](/documentation/integrations/integration-guides/duo-integration-setup.md) integration must be set up.
* Your [PSA](/documentation/integrations/top-5-integration-types-get-started-with-integrations-in-rewst.md#psa-integrations) must be successfully integrated with Rewst.

## Unpack the Identify Users in Bypass Mode Crate

1. Navigate to **Marketplace > Crates** in the left side menu of the Rewst platform.
2. Search for `Identify Users in Bypass Mode`\
   \
   ![](/files/mSVVhr9TDDrCZnSr4piU)
3. Click on the Crate tile to begin unpacking.
4. Click **Unpack Crate**.
5. Enter your estimated time saved.
6. Click **Unpack**.

<figure><img src="/files/EkcxEVtdfCUTCcLV6rSH" alt=""><figcaption></figcaption></figure>

### Update the cron trigger

{% hint style="info" %}
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.
{% endhint %}

1. Navigate to **Automations > Workflows**.
2. Search for **`Duo: Identify Users In Bypass Mode`**.
3. Click on the workflow to view it in the Workflow Builder.
4. 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.&#x20;
5. Click **Save Trigger**.<br>

{% hint style="info" %}
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](https://rewst.canny.io/crates).
{% endhint %}

### Set the email for failure notification.

1. Navigate to **Automations > Workflows**.
2. Search for **`Duo: Identify Users In Bypass Mode`**.
3. Click on the workflow to view it in the Workflow Builder.
4. Scroll over the workflow and locate the **send\_error\_to\_email** task.
5. Click into the task. Navigate to the **Parameters** tab.
6. Update the desired email address in the **fallback\_email** field.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rewst.help/documentation/crates/existing-crate-documentation/identify-users-in-bypass-mode-crate.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
