---
schema_version: "1"
id: d4d467ab91808758439c20c1595e08148d83c2dccea303c4e177ee6ad6b69868
title: Plan Your Snowflake Environment for Identity Boost
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_crc_plan_snowflake_for_identity_boost.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_crc_plan_snowflake_for_identity_boost.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7fa562c629226937752244e5d52c0ea6c87684153d2073061fb92e5f7f42a7f3
description: Before accepting identity boost collaboration invitations, decide how to isolate customer data in your Snowflake account and which region to use. These decisions affect the architecture of every collaboration that you accept, so make them before you receive your first invitation.
products:
  - Data 360
release: "264"
---
# Plan Your Snowflake Environment for Identity Boost

Before accepting identity boost collaboration invitations, decide how to isolate customer data in your Snowflake account and which region to use. These decisions affect the architecture of every collaboration that you accept, so make them before you receive your first invitation.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong> Edition (home org)</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">You can’t receive or accept collaboration invitations in Developer Edition.</td></tr></tbody></table>

## Choose a Multitenant Isolation Model

If you're collaborating with multiple consumers, choose how to isolate each consumer's data in your Snowflake environment. Choose one of these two isolation models.

  
| Feature | Object per Tenant (OPT) | Account per Tenant (APT) |
| --- | --- | --- |
| Isolation boundary | Separate database and schema within one Snowflake account for each customer | Separate Snowflake account per customer |
| Security guarantee | Depends on role-based access control (RBAC) configuration | Hard platform boundary — not dependent on RBAC |
| Operations overhead | Lower — one account, one job deployment | Higher — separate account, job deployment, and security integration per customer |
| Recommended for | Partners with a mature Snowflake RBAC practice | Partners with regulated-industry customers or strict data isolation requirements |

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note In the Object Per Tenant model, your enrichment job runs at the account level. A misconfigured role can expose another customer's data to the enrichment job. If you use this model, scope each customer's enrichment job execution role strictly to that customer's database and schema, and never use ACCOUNTADMIN or SYSADMIN roles for enrichment job execution.

## Choose a Snowflake Account Region

When your Snowflake account is in the same AWS region as a consumer's Data 360 instance, Data 360 uses Snowflake's zero-copy sharing for the data share, which doesn't consume Data 360 credits. If the regions differ, Data 360 physically replicates the data and consumes Data 360 credits.

When you receive an invitation, the **Consumer Salesforce Region** field on the Accept Clean Room Collaboration Invitation wizard shows the consumer's region. Use that value to confirm that your account is in a compatible region before you accept.

If you serve customers across multiple regions, provision one Snowflake account per region to avoid cross-region data transfer fees. If you maintain a single account, AWS US-east-2 (Ohio) is compatible with all US-based Data 360 regions.