# Reverse ETL Sources


RudderStack's **Reverse ETL** feature lets you use the customer data residing in your data warehouse and route it to your entire data stack, including analytics, sales, and marketing tools.

With this feature, you can set up your data warehouse as a source in the [RudderStack dashboard](https://app.rudderstack.com/), specify the data to import, then sync it to your desired destination.

{{< info >}}
You can set up to: 

- 10 connections in the RudderStack [Free](https://www.rudderstack.com/pricing/) plan
- 25 connections in the [Growth](https://www.rudderstack.com/pricing/) plan
- Unlimited connections in the [Enterprise](https://www.rudderstack.com/enterprise-quote/) plan
{{< /info >}}

## Supported Reverse ETL Sources

{{< sources type="reverse ETL" >}}

## Required permissions

- [Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to create and manage Reverse ETL sources created via warehouse tables, [SQL Models]({{< ref "data-pipelines/reverse-etl/features/models.md" >}}), and [Audiences]({{< ref "data-pipelines/reverse-etl/features/audiences.md" >}}).
- [Members]({{< ref "access-management/member-management.md#member-roles" >}}) can have the following [permissions]({{< ref "access-management/policies-overview.md#resource-permissions" >}}) depending on their workspace policy:

| Permission | <div style="width:350px">Description</div> | 
| :----| :-----| 
| Edit |  Make changes to the configuration of Reverse ETL sources | 
| Connect | Connect a Reverse ETL source to a destination | 
| Create & Delete | Create or delete Reverse ETL sources in the workspace | 

{{< warning >}}
To make a connection, that is, connect a source to a destination, the member must have both **Edit** and **Connect** permissions on both the resources.
{{< /warning >}}

{{< details "**Click here to see how these permissions appear in the workspace policy**." >}}
<br />

{{< figure src="images/access-management/reverse-etl.webp" alt="Permissions to manage Reverse ETL sources in RudderStack dashboard" >}}

{{< /details >}}
<br />

#### Permissions for legacy RBAC system

In the [legacy Permissions Management (RBAC) system]({{< ref "archive/dashboard-guides/user-management.md" >}}):

- [Org Admins]({{< ref "archive/dashboard-guides/user-management.md#organization-roles" >}}) and members with the [**Connections Admin** role]({{< ref "archive/dashboard-guides/user-management.md#connections" >}}) in their workspace policy can create and delete Reverse ETL sources, and connect them to destinations
- Members with the [**Connections Editor** role]({{< ref "archive/dashboard-guides/user-management.md#connections" >}}) in their workspace policy can only edit the Reverse ETL source configuration and connect Reverse ETL sources to destinations

{{< image src="images/access-management/data-catalog-permissions-legacy-framework.webp" alt="Reverse ETL sources permissions in the legacy framework" >}}

## FAQ

For answers to commonly asked questions around the Reverse ETL feature, see [FAQ]({{< ref "data-pipelines/reverse-etl/developer-guides/faq.md" >}}).