> 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/lastpass-setup-for-workbench.md).

# LastPass Setup for Workbench

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

1. You must have a LastPass Business account to allow for API provisioning, which this integration requires.

## Step 1: Obtain Your LastPass Account Number and Provisioning Hash <a href="#h_01hye6xqg5v166bjp3hszfekr0" id="h_01hye6xqg5v166bjp3hszfekr0"></a>

1. Log in to the [LastPass Admin Console](http://admin.lastpass.com/).
2. On the dashboard, get the **account number** for your instance as it is needed for authenticating API calls. Save it as you will need it in a later step.

   <div align="left"><figure><img src="/files/2ZlnC8YO5bH5XKP5Quir" alt="Expel Account Number is located on the LastPass dashboard." height="89" width="225"><figcaption></figcaption></figure></div>
3. In the top navigation, select **Advanced.**
4. In the side menu, select **Enterprise API**.
5. Select **Create provisioning hash** if no provisioning hash has already been created.
6. Copy the existing or new hash value and save it to a safe place.

   <figure><img src="/files/WnDPnCaBJzv2xcVRVbkE" alt="Provisioning hash displayed in Lastpass." height="87" width="720"><figcaption></figcaption></figure>

## Step 2: Add LastPass as a Security Device in Workbench <a href="#id-01j9c8sj1ywhqn8242xy68r807" id="id-01j9c8sj1ywhqn8242xy68r807"></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**.
3. Select **Add Security Device**.
4. In the search box, type “LastPass” and then select the **LastPass** integration.
5. Complete the fields as follows:<br>

   <div align="left"><figure><img src="/files/ZWA2a8qNm9cm9ipP5PKU" alt="LastPass add a security device screen in Workbench." width="375"><figcaption></figcaption></figure></div>

   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName LastPass”; 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.
   * **Provision hash** - enter the provisioning hash you acquired in [Step 1](#h_01hye6xqg5v166bjp3hszfekr0).
   * **Account number** - enter the account number you acquired in [Step 1](#h_01hye6xqg5v166bjp3hszfekr0).
   * 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/lastpass-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.