> 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/~/revisions/XPl7OpcVJrUAYPfsdid4/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.

## Crate prerequisites

Before unpacking this Crate:

* Our [Duo](/~/revisions/XPl7OpcVJrUAYPfsdid4/documentation/configuration/integrations/integration-guides/duo-integration-setup.md) integration must be set up.
* Your [PSA](/~/revisions/XPl7OpcVJrUAYPfsdid4/documentation/configuration/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 **Crates** **>** **Crate Marketplace** 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>

### Test the Crate

1. Navigate to **Automations > Workflows**.
2. Search **Duo:** **Identify Users In Bypass Mode**.
3. Click into the workflow.<br>

   <figure><img src="/files/gM2FO0vPU6pVoOkrmnP3" alt=""><figcaption></figcaption></figure>
4. The trigger has the workflow set to run at 12 am on Fridays. This can be changed by clicking ![](/files/hjANaBtAbjd209MVTVMJ). You also have the option to set an email send to notify you if the workflow fails.<br>

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

{% 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 %}


---

# 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.