> 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/q-z-integrations/sentinelone/sentinelone-singularity-data-lake-setup-for-workbench.md).
# SentinelOne Singularity Data Lake Setup for Workbench
## Scope and Limitations
When choosing to set up this integration, remember the following:
* We only support on-prem Active Directory as a data source; if this is not your data source, you can still set up the integration but we will not leverage data from any other connected sources.
## Prerequisites
* You must have SentinelOne's **Deep Visibility** so that we can fully triage and investigate your SentinelOne alerts.
## Step 1: Enable API Access for Expel
You first need to create a new user account with the appropriate permissions and API access, and also obtain an API key.
1. Log in to your SentinelOne console.
2. Navigate to **Policy & Settings** > **Singularity Data Lake** > **API Keys**.
3. Select **New Key**. *Make sure to copy and save the API key to a safe place, as you will need it in the next section.*
4. Select **Log Read Permissions.**
5. To change the name of the API key, hover on the key and select the **Edit** icon.
6. Enter "Expel API" as the name.
7. Select **Save**.
## Step 2: Add SentinelOne Singularity Data Lake as a Security Device in Workbench
Now that you have enabled API access, you can configure the integration in Workbench. **Before you begin, make sure you know your unique SentinelOne console access URL and the API key you generated in the previous step.**
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, type “SentinelOne” and then select the SentinelOne Singularity Data Lake integration.
5. Complete the fields as follows:
* **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Singularity Data Lake”; 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.
* **Server Address -** enter your SentinelOne console URL. It should look something like: https\://\.sentinelone.net.
* **API Key** - enter the API key generated in Step 1.
* Select **Save**.
6. Do one of the following:
* If you have already set up a different SentinelOne integration and granted us console access at that time, select **No thanks, I will not provide console access**. You can then select **Save** and skip to step 9.
* If this is your first SentinelOne integration, select **Set up now (recommended)** from the console access dropdown and continue to step 7. [Why do we need console access?](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md)
7. Scroll down and complete the fields as follows:
* **Console URL** - enter your SentinelOne console URL.
* **Username** - enter your SentinelOne username.
* **Password** - enter your SentinelOne password.
* **Two-factor secret key** - enter the two-factor secret key used during the login process.
8. 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/q-z-integrations/sentinelone/sentinelone-singularity-data-lake-setup-for-workbench.md?ask=&goal=
```
`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.