From 7f02a9c29fe6b90200bdbf823f43da980847da9e Mon Sep 17 00:00:00 2001 From: Matt Collins Date: Fri, 23 Oct 2026 10:23:23 +1100 Subject: [PATCH 1/2] UID2-8160: Document CSP limitation for Databricks clean rooms Ticket: UID2-8160 Branch: mkc-UID2-8160-document-csp-limitation --- docs/guides/integration-databricks.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index f8cc615d0..0d3cb286d 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -64,6 +64,8 @@ As a starting point, create a Databricks Clean Rooms environment—a secure Follow the steps in [Create clean rooms](https://docs.databricks.com/aws/en/clean-rooms/create-clean-room) in the Databricks documentation. Use the correct sharing identifier based on the [UID2 environment](../getting-started/gs-environments) you want to connect to: see [UID2 sharing identifiers](#uid2-sharing-identifiers). :::important +Create the clean room from a Databricks workspace that has no compliance security profile (CSP). A clean room that is created from a workspace with a CSP might not work with this integration. + After you've created a clean room, you cannot change its collaborators. If you have the option to set clean room collaborator aliases—for example, if you’re using the Databricks Python SDK to create the clean room—your collaborator alias must be `creator` and the UID2 collaborator alias must be `collaborator`. If you’re creating the clean room using the Databricks web UI, the correct collaborator aliases are set for you. ::: From 63a8ca0550e5fa6ad2a474fbeeca951e50a6f9ea Mon Sep 17 00:00:00 2001 From: Matt Collins Date: Mon, 26 Oct 2026 11:51:15 +1100 Subject: [PATCH 2/2] Address review feedback Ticket: UID2-8160 Branch: mkc-UID2-8160-document-csp-limitation --- docs/guides/integration-databricks.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index 0d3cb286d..c293e0559 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -50,25 +50,25 @@ Here are some key benefits of integrating with Databricks for your UID2 processi ## Integration steps -At a high level, the following are the steps to set up your Databricks integration and process your data: +To set up the Databricks integration and process your data, follow these steps: 1. [Create a clean room for UID2 collaboration](#create-clean-room-for-uid2-collaboration). 1. [Send your Databricks sharing identifier to your UID2 contact](#send-sharing-identifier-to-uid2-contact). 1. [Add data to the clean room](#add-data-to-the-clean-room). 1. [Map DII](#map-dii) by running the clean room notebook. -### Create clean room for UID2 collaboration +### Create a clean room for UID2 collaboration -As a starting point, create a Databricks Clean Rooms environment—a secure environment for you to collaborate with UID2 to process your data. +Create a clean room in Databricks Clean Rooms. A clean room is a secure environment where you collaborate with UID2 to process your data. Follow the steps in [Create clean rooms](https://docs.databricks.com/aws/en/clean-rooms/create-clean-room) in the Databricks documentation. Use the correct sharing identifier based on the [UID2 environment](../getting-started/gs-environments) you want to connect to: see [UID2 sharing identifiers](#uid2-sharing-identifiers). :::important -Create the clean room from a Databricks workspace that has no compliance security profile (CSP). A clean room that is created from a workspace with a CSP might not work with this integration. - -After you've created a clean room, you cannot change its collaborators. If you have the option to set clean room collaborator aliases—for example, if you’re using the Databricks Python SDK to create the clean room—your collaborator alias must be `creator` and the UID2 collaborator alias must be `collaborator`. If you’re creating the clean room using the Databricks web UI, the correct collaborator aliases are set for you. +Create the clean room from a Databricks workspace that has no compliance security profile (CSP). A clean room created from a workspace with a CSP might not work with this integration. ::: +You can't change a clean room's collaborators after you create it. The clean room must use the alias `creator` for your collaborator and the alias `collaborator` for the UID2 collaborator. These are the default values. If the method you use to create the clean room lets you set aliases, make sure you set them to these values. + ### Send sharing identifier to UID2 contact Before you can use the clean room notebook, you'll need to send your Databricks sharing identifier to your UID2 contact.