> 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/varonis-datalert-setup-for-workbench.md). # Varonis DatAlert Setup for Workbench {% hint style="warning" %} **Expel supports Varonis DatAlert on-premises.** We do not support DatAlert SaaS or through Varonis Cloud at this time. {% endhint %} Connecting Workbench to a Varonis installation requires a Varonis domain user account with access to DatAlerts. The first step is to configure the account with the proper roles. Then, you can connect Varonis to Workbench and test the connection. ## Prerequisites * You must first [add an Expel Assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md). ## Step 1: Set Up the Varonis Domain User Account Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. [Learn more about console access.](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md) 1. In Varonis, create a domain user account. 2. Make a note of the username and password on the account for later reference. 3. Navigate to the **Varonis management console > Configuration > Security**. 4. Assign the domain user the following roles: * `Alerts View User` * `Directory Services Trends View User` * `File System Trends View User` * `Log View User` * `Reports View User` * `User` * `Web UI User` ## Step 2: Add Varonis DatAlert as a Security Device in Workbench Now that you have the correct access configured and noted the credentials, you can integrate your tech with 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 “Varonis” and then select the Varonis DatAlert integration. 5. Complete the fields as follows: * **Assembler** - select your [assembler](#prerequisites) from the list. * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Varonis”; 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 username** - enter the API admin credentials from Step 1. * **API password** - enter the API admin credentials from Step 1. * **URL** - ener the Varonis instance URL. 6. Select **Save**. 7. On the console access screen, select **Set up now (recommended)**.[ Why do we need console access?](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md) 8. Scroll down to the Console Login area, and complete the fields as follows: * **Console URL** - enter same URL you used on the prior screen, but this time add `/login` to the end of the URL. * **Username** - enter the API username. * **Password** - enter the API password. * **Two-factor secret key (optional)** - if necessary for login at your organization, enter the authentication key here; if not, leave this field blank. If you have questions about this field, [contact Support](/support/how-to-reach-us.md). 9. 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/varonis-datalert-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.