From c73bdef36f3244d5f500e900023cf1a5b333124f Mon Sep 17 00:00:00 2001 From: Matt Collins Date: Fri, 23 Oct 2026 10:23:23 +1100 Subject: [PATCH] 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. :::