---
title: Create data recipients for OpenSharing (Databricks-to-Databricks sharing) | Databricks on AWS
source: https://docs.databricks.com/aws/en/delta-sharing/create-recipient
ingestedAt: "2026-06-18T08:05:16.961Z"
---

This page explains how to create recipients in OpenSharing, when the recipients are on a Databricks workspace that is enabled for [Unity Catalog](https://docs.databricks.com/aws/en/data-governance/unity-catalog/). To view, update, delete, grant share access, manage properties, or restrict access with IP lists for an existing recipient, see [Manage data recipients for OpenSharing](https://docs.databricks.com/aws/en/delta-sharing/manage-recipients).

A recipient is the named object that represents the identity of a user or group of users who consume shared data. The way you create recipients differs depending on whether or not your recipient has access to a Databricks workspace that is enabled for Unity Catalog:

*   Recipients with access to a Unity Catalog\-enabled Databricks workspace:
    
    You can create a recipient object with a secure connection managed by Databricks. This sharing mode is called _Databricks-to-Databricks sharing_, and it is documented in this page.
    
*   Recipients without access to a Unity Catalog\-enabled Databricks workspace:
    
    You must use _open sharing_, with a secure connection that you manage using token-based authentication (either bearer tokens or OAuth federation). For information about creating Databricks-to-Open sharing recipients, see [Enable Open ID Connect (OIDC) federation for OpenSharing recipients](https://docs.databricks.com/aws/en/delta-sharing/create-recipient-oidc-fed) and [Create a recipient object for non-Databricks users using bearer tokens (Databricks-to-Open sharing)](https://docs.databricks.com/aws/en/delta-sharing/create-recipient-token).
    

For more information about these two sharing modes and when to choose which, see [Databricks-to-Open sharing versus Databricks-to-Databricks sharing](https://docs.databricks.com/aws/en/delta-sharing/#open-vs-d-to-d).

## Requirements[​](#requirements "Direct link to Requirements")

To create a recipient:

*   You must have the `CREATE RECIPIENT` privilege for the Unity Catalog metastore where the data you want to share is registered.
*   You must create the recipient using a Databricks workspace that has that Unity Catalog metastore attached.
*   If you use a Databricks notebook to create the recipient, your compute must use Databricks Runtime 11.3 LTS or above and either standard or dedicated access mode (formerly shared and single user access modes).

For permissions required for other recipient operations (view, update, delete, grant share access, manage properties), see [Manage data recipients for OpenSharing](https://docs.databricks.com/aws/en/delta-sharing/manage-recipients).

## Create a recipient object for users who have access to Databricks (Databricks-to-Databricks sharing)[​](#create-a-recipient-object-for-users-who-have-access-to-databricks-databricks-to-databricks-sharing "Direct link to create-a-recipient-object-for-users-who-have-access-to-databricks-databricks-to-databricks-sharing")

If your data recipient has access to a Databricks workspace that has been [enabled for Unity Catalog](https://docs.databricks.com/aws/en/data-governance/unity-catalog/enable-workspaces), you can create a recipient object with an authentication type of `DATABRICKS`.

A recipient object with the authentication type of `DATABRICKS` represents a data recipient on a particular Unity Catalog metastore, identified in the recipient object definition by a _sharing identifier_ string consisting of the metastore's cloud, region, and UUID. The data shared with this recipient can be accessed only on that metastore.

### Step 1: Request the recipient's sharing identifier[​](#step-1-request-the-recipients-sharing-identifier "Direct link to step-1-request-the-recipients-sharing-identifier")

Ask a recipient user to send you the sharing identifier for the Unity Catalog metastore that is attached to the workspaces where the recipient user or group of users will work with the shared data.

The sharing identifier is a string consisting of the metastore's cloud, region, and UUID (the unique identifier for the metastore), in the format `<cloud>:<region>:<uuid>`.

For example, in the following screenshot, the complete sharing identifier string is `aws:us-west-2:19a84bee-54bc-43a2-87de-023d0ec16016`.

![example of CURRENT\_METASTORE](https://docs.databricks.com/aws/en/assets/images/share-metastore-078409bb1ea0ffdeae1f0a915930abc5.png)

The recipient can find the identifier using Catalog Explorer, the Databricks Unity Catalog CLI, or the default SQL function `CURRENT_METASTORE` in a Databricks notebook or Databricks SQL query that runs on a Unity-Catalog-capable compute in the workspace they intend to use.

*   Catalog Explorer
*   SQL
*   CLI

To get the sharing identifier using Catalog Explorer:

1.  In your Databricks workspace, click ![Data icon.](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIHZpZXdCb3g9IjAgMCAxNiAxNiIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj4KPHBhdGggZmlsbC1ydWxlPSJldmVub2RkIiBjbGlwLXJ1bGU9ImV2ZW5vZGQiIGQ9Ik04LjY0NTc2IDAuMzY4NDUzQzguNTEwODIgMC4xNDAwOTkgOC4yNjUzIDAgOC4wMDAwNiAwQzcuNzM0ODIgMCA3LjQ4OTMgMC4xNDAwOTkgNy4zNTQzNyAwLjM2ODQ1M0w0LjEwNDM3IDUuODY4NDVDMy45NjczNiA2LjEwMDMgMy45NjUxOCA2LjM4NzgxIDQuMDk4NjUgNi42MjE3MUM0LjIzMjEzIDYuODU1NjEgNC40ODA3NiA3IDQuNzUwMDYgN0gxMS4yNTAxQzExLjUxOTQgNyAxMS43NjggNi44NTU2MSAxMS45MDE1IDYuNjIxNzFDMTIuMDM0OSA2LjM4NzgxIDEyLjAzMjggNi4xMDAzIDExLjg5NTggNS44Njg0NUw4LjY0NTc2IDAuMzY4NDUzWk04LjAwMDA2IDIuMjI0MjZMOS45MzU3MiA1LjVINi4wNjQ0TDguMDAwMDYgMi4yMjQyNloiIGZpbGw9IiM2RjZGNkYiLz4KPHBhdGggZmlsbC1ydWxlPSJldmVub2RkIiBjbGlwLXJ1bGU9ImV2ZW5vZGQiIGQ9Ik04LjUgOS4yNUM4LjUgOC44MzU3OSA4LjgzNTc5IDguNSA5LjI1IDguNUgxNC4yNUMxNC42NjQyIDguNSAxNSA4LjgzNTc5IDE1IDkuMjVWMTQuMjVDMTUgMTQuNjY0MiAxNC42NjQyIDE1IDE0LjI1IDE1SDkuMjVDOC44MzU3OSAxNSA4LjUgMTQuNjY0MiA4LjUgMTQuMjVWOS4yNVpNMTAgMTBWMTMuNUgxMy41VjEwSDEwWiIgZmlsbD0iIzZGNkY2RiIvPgo8cGF0aCBmaWxsLXJ1bGU9ImV2ZW5vZGQiIGNsaXAtcnVsZT0iZXZlbm9kZCIgZD0iTTEgMTEuNzVDMSA5Ljk1NTA3IDIuNDU1MDcgOC41IDQuMjUgOC41QzYuMDQ0OTMgOC41IDcuNSA5Ljk1NTA3IDcuNSAxMS43NUM3LjUgMTMuNTQ0OSA2LjA0NDkzIDE1IDQuMjUgMTVDMi40NTUwNyAxNSAxIDEzLjU0NDkgMSAxMS43NVpNNC4yNSAxMEMzLjI4MzUgMTAgMi41IDEwLjc4MzUgMi41IDExLjc1QzIuNSAxMi43MTY1IDMuMjgzNSAxMy41IDQuMjUgMTMuNUM1LjIxNjUgMTMuNSA2IDEyLjcxNjUgNiAxMS43NUM2IDEwLjc4MzUgNS4yMTY1IDEwIDQuMjUgMTBaIiBmaWxsPSIjNkY2RjZGIi8+Cjwvc3ZnPgo=) **Catalog**.
    
2.  At the top of the **Catalog** pane, click the ![Gear icon.](data:image/svg+xml;base64,[encoded data, 5356 characters]) gear icon and select **OpenSharing**.
    
    Alternatively, in the upper-right corner, click **Share > OpenSharing**.
    
3.  On the **Shared with me** tab, click your Databricks sharing organization name in the upper right, and select **Copy sharing identifier**.
    

You can send your recipient the information contained in this step, or you can point them to [Get access in the Databricks-to-Databricks model](https://docs.databricks.com/aws/en/delta-sharing/recipient#get-access-db-to-db).

### Step 2: Create the recipient[​](#step-2-create-the-recipient "Direct link to step-2-create-the-recipient")

To create a recipient for Databricks-to-Databricks sharing, you can use Catalog Explorer, the Databricks Unity Catalog CLI, or the `CREATE RECIPIENT` SQL command in a Databricks notebook or the Databricks SQL query editor.

**Permissions required**: Metastore admin or user with the `CREATE RECIPIENT` privilege for the Unity Catalog metastore where the data you want to share is registered.

*   Catalog Explorer
*   SQL
*   CLI

1.  In your Databricks workspace, click ![Data icon.](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIHZpZXdCb3g9IjAgMCAxNiAxNiIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj4KPHBhdGggZmlsbC1ydWxlPSJldmVub2RkIiBjbGlwLXJ1bGU9ImV2ZW5vZGQiIGQ9Ik04LjY0NTc2IDAuMzY4NDUzQzguNTEwODIgMC4xNDAwOTkgOC4yNjUzIDAgOC4wMDAwNiAwQzcuNzM0ODIgMCA3LjQ4OTMgMC4xNDAwOTkgNy4zNTQzNyAwLjM2ODQ1M0w0LjEwNDM3IDUuODY4NDVDMy45NjczNiA2LjEwMDMgMy45NjUxOCA2LjM4NzgxIDQuMDk4NjUgNi42MjE3MUM0LjIzMjEzIDYuODU1NjEgNC40ODA3NiA3IDQuNzUwMDYgN0gxMS4yNTAxQzExLjUxOTQgNyAxMS43NjggNi44NTU2MSAxMS45MDE1IDYuNjIxNzFDMTIuMDM0OSA2LjM4NzgxIDEyLjAzMjggNi4xMDAzIDExLjg5NTggNS44Njg0NUw4LjY0NTc2IDAuMzY4NDUzWk04LjAwMDA2IDIuMjI0MjZMOS45MzU3MiA1LjVINi4wNjQ0TDguMDAwMDYgMi4yMjQyNloiIGZpbGw9IiM2RjZGNkYiLz4KPHBhdGggZmlsbC1ydWxlPSJldmVub2RkIiBjbGlwLXJ1bGU9ImV2ZW5vZGQiIGQ9Ik04LjUgOS4yNUM4LjUgOC44MzU3OSA4LjgzNTc5IDguNSA5LjI1IDguNUgxNC4yNUMxNC42NjQyIDguNSAxNSA4LjgzNTc5IDE1IDkuMjVWMTQuMjVDMTUgMTQuNjY0MiAxNC42NjQyIDE1IDE0LjI1IDE1SDkuMjVDOC44MzU3OSAxNSA4LjUgMTQuNjY0MiA4LjUgMTQuMjVWOS4yNVpNMTAgMTBWMTMuNUgxMy41VjEwSDEwWiIgZmlsbD0iIzZGNkY2RiIvPgo8cGF0aCBmaWxsLXJ1bGU9ImV2ZW5vZGQiIGNsaXAtcnVsZT0iZXZlbm9kZCIgZD0iTTEgMTEuNzVDMSA5Ljk1NTA3IDIuNDU1MDcgOC41IDQuMjUgOC41QzYuMDQ0OTMgOC41IDcuNSA5Ljk1NTA3IDcuNSAxMS43NUM3LjUgMTMuNTQ0OSA2LjA0NDkzIDE1IDQuMjUgMTVDMi40NTUwNyAxNSAxIDEzLjU0NDkgMSAxMS43NVpNNC4yNSAxMEMzLjI4MzUgMTAgMi41IDEwLjc4MzUgMi41IDExLjc1QzIuNSAxMi43MTY1IDMuMjgzNSAxMy41IDQuMjUgMTMuNUM1LjIxNjUgMTMuNSA2IDEyLjcxNjUgNiAxMS43NUM2IDEwLjc4MzUgNS4yMTY1IDEwIDQuMjUgMTBaIiBmaWxsPSIjNkY2RjZGIi8+Cjwvc3ZnPgo=) **Catalog**.
    
2.  At the top of the **Catalog** pane, click the ![Gear icon.](data:image/svg+xml;base64,[encoded data, 5356 characters]) gear icon and select **OpenSharing**.
    
    Alternatively, in the upper-right corner, click **Share > OpenSharing**.
    
3.  On the **Shared by me** tab, click **New recipient**.
    
4.  Enter the **Recipient name**.
    
5.  For **Recipient type**, select **Databricks**.
    
6.  Enter the recipient's **Sharing identifier**.
    
    Use the entire sharing identifier string in the format `<cloud>:<region>:<uuid>`. For example, `aws:us-west-2:19a84bee-54bc-43a2-87de-023d0ec16016`.
    
7.  (Optional) Enter a comment.
    
8.  Click **Create**.
    
9.  (Optional) Create custom **Recipient properties**.
    
    On the recipient **Overview** tab, click the ![Edit icon](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAABWWlDQ1BJQ0MgUHJvZmlsZQAAKJFtkL1Lw1AUxU9rasUvHHQQOgREsFKlxIJdawcpOIRq/ZpM05iqafqaRtTVVWdnJ/8CpYqLbu6Ciojo5uKkZLEl3teqadX7uJwfl/Me9x3ALyiMGQKAgmlb6ekpcXFpWQy+oJ1OBwYRUNQyS8jyDFnwra3l3MDH9XqMv3X6GFp/Ni6jD68npaqeyvz1t1RnTiurpFXqUZVZNuAbIZa3bMZ5m7jfoqWI9znrDT7knG3wcd0zl04SXxH3qXklR3xHHMk2zfUmLhib6tcOfPtuzczMkvZShyAjAQmTiCOJecrmf2+s7k2iCIYdWFiDjjxsiHSb0TGgEadgQsU4IsQSotQxnvHv7LxZaQOIvwP+IW+2Qpmc7QEDYW82TH/p2QXOn5hiKT+J+hyhvDohNbirAgQOXPdtAQiGgdqt635UXLd2BLTdAxfOJ9PYYx56edxFAAAAOGVYSWZNTQAqAAAACAABh2kABAAAAAEAAAAaAAAAAAACoAIABAAAAAEAAAASoAMABAAAAAEAAAASAAAAALlhkG8AAAD2SURBVDgRpZM9EoIwEEYDw0l0xgKuoR0tXkFrC1vxAvaewdbOc0DBjF5F86LLBIhA4Jsh//vY3WyCt5by1O3+UEX1UslqobJ0Y6wjT4bKL1dVVk9jJj0wL5BA4tXSeINnfGg0yIbkh50xjnVoZ+0hYYZmZaARCMfIi6jUAMTaoEcCIRxyIqEAkDE5CvpuzYYQTqFBhGLrpNcT/ZO/obUhGGMg181cIIydIBeEw/Yt2RAnaAqkA5oKaYDmQGrQXIgBkUDqgzqRimWjL7HstxVS3mgOBPvO9ft6AgTVT2S7P35Xfm27ThqbjklkP0LZz9K1qWKZj+k/LRuwBP9tGQAAAAAASUVORK5CYII=) edit icon next to **Recipient properties**. Then add a property name (**Key**) and **Value**. For details, see [Manage recipient properties](https://docs.databricks.com/aws/en/delta-sharing/manage-recipients#properties).
    

The recipient is created with the `authentication_type` of `DATABRICKS`.

## Next steps[​](#next-steps "Direct link to Next steps")

*   [Manage access to OpenSharing data shares (for providers)](https://docs.databricks.com/aws/en/delta-sharing/grant-access) — Grant the recipient access to one or more shares.
*   [Manage data recipients for OpenSharing](https://docs.databricks.com/aws/en/delta-sharing/manage-recipients) — View, update, delete, manage properties, or restrict access for an existing recipient.
*   [Create shares for OpenSharing](https://docs.databricks.com/aws/en/delta-sharing/create-share) — Create the shares you want to grant the recipient access to.
