> 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/sumo-logic/sumo-logic-cloud-siem-enterprise-setup-for-workbench.md).

# Sumo Logic Cloud SIEM Enterprise Setup for Workbench

## Step 1: Create a New Role in Sumo Logic <a href="#h_01hj1cd7n8ddz5gn7b9p9mjj61" id="h_01hj1cd7n8ddz5gn7b9p9mjj61"></a>

This step creates a role that provides permissions to SOC analysts in order to fully triage and research events that result in an Expel Alert. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md). This step also adds a permission allowing Expel to obtain API credentials and complete the integration.

1. Log in to the Sumo Logic Cloud Intelligence Platform console.
2. Navigate to **Administration > Users and Roles > Roles** and and select the **Add Role** button at the top right of the page.

   <div align="left"><figure><img src="/files/NcfVoaT7uptwcLsebWgi" alt="The Administration menu in Sumo Logic." height="269" width="211"><figcaption></figcaption></figure></div>
3. On the Create New Role screen, configure the settings as follows:
   1. **Name** - enter "View CSE Role".
   2. **Description** (optional) - enter a description for the role.
   3. Under **Capabilities**, scroll to the Security section and select **Create Access Keys**.
   4. Scroll down to the Cloud SIEM Enterprise section and check **View Cloud SIEM Enterprise**.
   5. Expand the dropdown for **Content** permissions and select the following:
      * View Rules
      * View Threat Intelligence (recommended, not required)
      * View Match Lists
      * View File Analysis
      * View Custom Insights
      * View Network Blocks
      * View Suppressed Entities
   6. Expand the dropdown for **Configuration** permissions and select those listed below. *The permissions in this section are **recommended**, but not required.*
      * View Mappings
      * View Workflow
      * View Context Actions
      * View Actions
      * View Enrichments
      * View Custom Entity Types
      * View Entity
      * View Entity Normalization
      * View Entity Criticality
      * View Tag Schemas
      * View Entity Groups
      * View Automations
4. Select **Save**.

## Step 2: Create a New User in Sumo Logic <a href="#id-01k5w0mbkeqbm6j2j5vqpwjh7m" id="id-01k5w0mbkeqbm6j2j5vqpwjh7m"></a>

In this step you will create a new Sumo Logic user and assign it the role you created in Step 1.

1. Navigate to **Administration > Users and Roles > Users** and select the **Add User** button at the top right of the page.

   <div align="left"><figure><img src="/files/ZU0vnnPIdepm1DE1DJeu" alt="Administration menu shows Users option." width="206"><figcaption><p>add_user.png</p></figcaption></figure></div>
2. On the Create New User screen, configure the settings as follows:
   * **First Name** - enter "Expel".
   * **Last Name** - enter "SOC Analysts"
   * **Email** - enter "soc+\<your\_company\_name>@expel.io".
     * For example, if your organization were Acme Corp, the format would be "<soc+acme_corp@expel.io>".
   * **Assigned Roles** - select **Analyst** and **View CSE Role**.

     <div align="left"><figure><img src="/files/93wiKuSAg3gJhmrABiDK" alt="Example of the user configuration specified above." width="221"><figcaption></figcaption></figure></div>
3. Select **Save**.
4. Verify that "Expel SOC Analysts" now appears on the Users page with the appropriate roles applied. Sumo Logic automatically sends an invitation to the Expel SOC email address, allowing them activate the account and set a new password. <br>

Using the account and permissions you granted, Expel will generate the required Access Key and complete onboarding your device in Workbench. You will receive a notification that the device is added in Workbench within one business day.

Once your device is created, you can monitor it in Workbench. 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](/support/how-to-reach-us.md) for help.
* 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/sumo-logic/sumo-logic-cloud-siem-enterprise-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.
