> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/l-p-integrations/1password-setup-for-workbench.md).

# 1Password Setup for Workbench

## Prerequisites <a href="#h_01hyebafxatvqcmgmec63ancmr" id="h_01hyebafxatvqcmgmec63ancmr"></a>

1. You must have admin permissions in 1Password.

## Step 1: Create a 1Password Token <a href="#uuid-94447136-204c-ba02-7a0a-183413f2cd9e_bridgehead-idm4609676291264032974765356813" id="uuid-94447136-204c-ba02-7a0a-183413f2cd9e_bridgehead-idm4609676291264032974765356813"></a>

1. Log into the 1Password web dashboard.
2. Select **Integrations** in the side panel.
3. Locate the **Events Reporting** tab and select **Other**.
4. Configure the integration as follows:
   * **Name** - enter "Expel".&#x20;
   * **Expires After** - set to **Never**.
   * **Events to Report** - select the following:
     * **Audit events**
     * **Items usage events**
     * **Sign-in attempts**
5. Select **Issue Token**.&#x20;
6. **Copy and save the token** in a safe place for later use.

## Step 2: Add 1Password as a Security Device in Workbench <a href="#uuid-94447136-204c-ba02-7a0a-183413f2cd9e_bridgehead-idm46090944303376336506009613" id="uuid-94447136-204c-ba02-7a0a-183413f2cd9e_bridgehead-idm46090944303376336506009613"></a>

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**. If you have multiple organizations, you must select the appropriate organization name from the list.
3. Select **Add Security Device**.
4. Search for and select the **1Password** integration.

<div align="left"><figure><img src="/files/McRKNBisBKf3RhgHBd6m" alt="1Password Add a Security Device screen in Workbench." width="329"><figcaption></figcaption></figure></div>

5. Complete the fields as follows:
   * **Where is your device?** - select one of the following depending on your installation:
     * **SaaS installation**: select **Cloud**.
     * **Self-hosted installation:** select **On-prem** and then select **Assembler** from the list. Select the assembler you set up in [Add a New Assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md).
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName 1Password”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   * **Location** - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   * **API token** - provide the token created in [Step 1](#uuid-94447136-204c-ba02-7a0a-183413f2cd9e_bridgehead-idm4609676291264032974765356813).
   * **Server address** - select your server URL from the list.
6. Select **Save**.

Your device should be created successfully within a few seconds. A few reminders:

* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).


---

# 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.expel.io/connect-your-technology/l-p-integrations/1password-setup-for-workbench.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.