# RudderStack Destinations Overview


A RudderStack destination is the target for your source event data. It is generally categorized into the following types:

* [Event Stream destinations]({{< ref "destinations/streaming-destinations/" >}}) consume your event data to complement their offering related to marketing, analytics, CRM, etc.
* [Warehouse destinations]({{< ref "destinations/warehouse-destinations/" >}}) are data storage and processing platforms like Amazon Redshift, Snowflake, or Google BigQuery.
* [Webhook destination]({{< ref "destinations/webhooks/" >}}) forwards the SDK events to your configured webhook endpoint.

## Event Stream destinations

The below table lists the Event Stream destinations and different source types that you can use with them:

{{< source-destination type="streaming">}}

## Warehouse destinations

The below table lists the warehouse destinations and different source types that you can use with them:

{{< source-destination type="warehouse">}}

## Reverse ETL-only destinations

The below table lists the destinations which support only [Reverse ETL]({{< ref "sources/reverse-etl/_index.md" >}}) sources:

{{< source-destination type="retl">}}

## Webhook destination

RudderStack supports the webhook destination which lets you send the events generated via RudderStack’s [SDKs]({{< ref "sources/event-streams/sdks/_index.md" >}}), [Cloud Apps]({{< ref "sources/event-streams/cloud-apps/_index.md" >}}), and [Reverse ETL]({{< ref "sources/reverse-etl/_index.md" >}}) sources:

{{< source-destination type="webhook">}}

{{< info >}}
To send events to a destination that RudderStack does not support currently, you can build a new integration for that destination by referring to the [Contributor's guides]({{< ref "get-started/introduction/community.md#contribute" >}}).
{{< /info >}}

## Required permissions

- [Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to create and manage destinations.
- [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 destinations.  | 
| Connect | Connect a destination to a source or transformation. | 
| Create & Delete | Create or delete destinations. | 

{{< 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 >}}

#### 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 destinations, manage their configuration, and connect them to sources
- Members with the [**Connections Editor** role]({{< ref "archive/dashboard-guides/user-management.md#connections" >}}) in their workspace policy can only edit the destination configuration and connect destinations to sources

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