> 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/workbench-setup/get-started/connect-your-technologies.md).
# Connect Your Technologies
Each vendor technology has a specific Expel onboarding process that usually includes some setup within the technology before adding it as a security device in Workbench. Certain types of on-prem technology (like AWS, Azure, GCP, Hyper-V, VMware, and Nutanix) may require you to use an [assembler](/connect-your-technology/expel-assembler.md) rather than adding it as a security device. You may also wish to configure an [IP allow list](/workbench-setup/configure-an-ip-allow-list.md).
## **Add an Assembler (if applicable)**
**Do you need an assembler?** Some technologies live on an internal, private network where a direct external connection cannot be established. These technologies will require the deployment of an Expel Assembler to connect.\
\
If you believe you may need an assembler, see the information below:
* To understand how our assemblers are built and how they work, go to the [About the Assembler](/connect-your-technology/expel-assembler/about-the-expel-assembler.md) guide.
* To deploy an assembler, go to the [Add a New Assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md) guide and follow the instructions; links will be provided at the end of that guide to configure your specific technology.
## **Set Up Your Technology**
To find setup instructions for your technology, do one of the following:
* Search for and view your technology's setup guide:
* Browse the [**Integrations page** ](/connect-your-technology/about-integrations/expel-integrations.md)for our portfolio and select the hyperlink (if available) to go directly to the guide.
* If you are an [Organization Admin user](/workbench-setup/get-started/add-and-manage-users/user-role-rights.md), use the **Set up** buttons on your Welcome screen in Workbench to find links to your setup guides. For more information, go to [About the Welcome Screen](#about-the-welcome-screen-organization-admins-only).
If you cannot find the setup guide you need, [contact support](/support/how-to-reach-us.md) for help.
{% hint style="info" %}
Some integrations require you to grant us a certain level of console access during the setup process. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).
{% endhint %}
## About the Welcome Screen (Organization Admins Only)
If you are an [Organization Admin user](/workbench-setup/get-started/add-and-manage-users/user-role-rights.md), you will see a Welcome screen when you log in to Workbench that will contain a list of your technologies to onboard. Select one of the **Set up** buttons to find a link to the appropriate setup guide.
After you have successfully connected, the **Set up** button will disappear and will be replaced by a connection status (as shown below).
If you know you are this user type but do not see the Welcome screen, try going to **Dashboards > Alert Analysis**.
---
# 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/workbench-setup/get-started/connect-your-technologies.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.