> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/architecture/warehouse-data-access.md).

# Warehouse Data Access

Rox supports two approaches to accessing structured enterprise data: native warehouse sharing and replication into a Rox-managed environment.

An organization may use a combination of both approaches above, depending on where its data lives and how its sources are connected. The distinction is where source data is made available for processing. Both approaches require configuration of the data Rox can access and how it maps to Rox entities.

### Native data sharing

With native sharing, an organization makes selected warehouse data available to Rox through the warehouse’s sharing capabilities. Rox can read the shared data without requiring a separate replicated copy of those source tables in a Rox-managed warehouse.

This approach is useful when the relevant enterprise data already lives in a supported warehouse and the organization wants to manage which datasets it shares at the source.

The sharing mechanism, permissions, and setup differ by platform. See the [**Snowflake**](https://www.rox.com/docs?page=architecture/docs/rox-enterprise-integrations/data-warehouse-integration/snowflake), [**Databricks**](https://www.rox.com/docs?page=architecture/docs/rox-enterprise-integrations/data-warehouse-integration/databricks), and [**BigQuery**](https://www.rox.com/docs?page=architecture/docs/rox-enterprise-integrations/data-warehouse-integration/bigquery) integration guides for platform-specific requirements.

Native sharing describes access to source data. It should not be read as a blanket statement that no derived data, indexes, or application-serving data is stored by Rox. Confirm those boundaries as part of your deployment review.

### Data replication

With replication, data from connected systems is copied into a Rox-managed environment for processing.

This approach can support sources that are not available through a native warehouse share. Connectors ingest the configured data, and subsequent synchronization brings in supported source changes.

Freshness depends on the connector, synchronization schedule, and downstream processing. Replication also introduces a separate copy of the data, so the deployment should account for access, retention, and disconnection requirements.

### Combining approaches

An organization may share some datasets from its warehouse while using connectors to replicate data from other systems.

For example, an organization could share structured business data from its warehouse and connect communication systems separately. The access and storage arrangements should be understood for each source.

### Comparing the approaches

| **Consideration**        | **Native sharing**                                                      | **Replication**                                                          |
| ------------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Source access            | Rox reads datasets made available through a warehouse share             | A connector copies configured source data into a Rox-managed environment |
| Source-table duplication | Does not require a separate replicated copy of the shared source tables | Creates a copy of the configured data                                    |
| Freshness                | Depends on source updates, access, and Rox processing                   | Depends on synchronization and Rox processing                            |
| Configuration            | Shared datasets, warehouse permissions, and mappings                    | Connector permissions, synchronization settings, and mappings            |
| Operational dependency   | Availability of the shared source and access permissions                | Connector operation and the replicated destination                       |

Neither approach alone guarantees that every source change appears immediately in Rox. Both may involve additional processing before data is available in an account view or agent response.

### Preparing for setup

Before configuring access, identify:

* The systems and datasets Rox needs to use.
* The accounts, people, opportunities, and business attributes represented in those datasets.
* The identifiers and relationships needed to map source records into Rox.
* Who can authorize source access and manage the connection.
* The required freshness, storage, and retention arrangements.

Source permissions determine what the connection can access. Rox Governance determines access within Rox. Review both rather than assuming that establishing a connection completes the permission setup.

For setup instructions, see **Admin Guide → Integrations → Data Warehouses**. For how connected data is organized and used, see [**System of Context**](https://www.rox.com/docs?page=architecture/system-of-context).