> 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/more-features/expel-vulnerability-prioritization/rapid7-insightvm-setup-for-workbench.md).

# Rapid7 InsightVM Setup for Workbench

This guide describes how to connect Rapid7​ InsightVM to Workbench and add Rapid7​ console access.

## Step 1: Get the API Credentials from Rapid7​ VM

An organization API key allows access to InsightVM product APIs, and can only be generated by administrators.

1. Log in to the Rapid7​ console as an administrator.
2. In Insight Platform, select **Home**.
3. Select **API Key Management**.

<div align="left"><figure><img src="/files/ORFlOUhcPeoTViEHqSav" alt="" width="203"><figcaption></figcaption></figure></div>

4. Select **Organization Keys**.
5. On the Organization Keys screen, select **Generate New Organization Key**.
6. Enter your organization name.
7. In the ExpelAPI field, enter the Expel API key. We suggest ExpelAPI.
8. Generate the key by selecting **Submit**.
9. A window opens to display the generated key. Copy and save the key for later use in Workbench.

## Step 2: Add a Rapid7​ InsightVM Console User

Expel's device health team uses console access to investigate potential health issues with your tech. Having access to the interface of your technology allows Expel to dig deeper during incident investigation and supports programmatic vulnerability scanning (i.e. scan details, tagging, asset types, exceptions, and other features). [Learn more about why we need console access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).

1. In Insight Platform, select **Settings > User Management**.
2. Select **Add User**.
3. In the Email field, enter "soc+\<Your\_Organization\_Name>@expel.i&#x6F;**"**.
   * For example, if your organization were Acme Corp, the format would be "<soc+acme_corp@expel.io>".
4. In the First Name field, enter **SOC**.
5. In the Last Name field, enter **Expel**.
6. In the Time Zone field, select **UTC**.
7. In Product Roles, select **Admin**.
8. Select **Submit**.&#x20;

The user is now added to InsightOps, which generates an email to the SOC team to activate the account.

## Step 3: Add Rapid7​ API Credentials to Workbench

You can now add Rapid7​ InsightVM to Workbench.

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. In the search box, enter “Rapid7” and then select the Rapid7 InsightVM integration.
5. Complete the fields as follows:
   * **Name** - enter the name of the device.
   * **Location** - enter the location of the device.
   * **API Key** - provide the key that was generated in [Step 1](#step-1-get-the-api-credentials-from-rapid7-vm).
   * **Region** - enter the location of Rapid7​.
6. Select **Save**.
7. In the How will you access the console field, select **Set up now (recommended)**.
8. Complete the fields:
   * In the Console URL field, enter "<https://insight.rapid7.com>".
   * In the Username field, enter "soc+\<Your\_Organization\_Name>@expel.io".
9. Select **Save**.


---

# 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/more-features/expel-vulnerability-prioritization/rapid7-insightvm-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.