# Early Access Data Model Changes

This page is for early access customers who want to understand the differences between data models. Until this access summary feature moves to GA, all data model changes will be **immediate**. See the [versioning](/saas/govern/detect-your-data/access-summary-export.md#versioning) section for more details.

See the [Latest access summary export schema reference guide](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md) for the most current access summary data model.

## PrPr1 <i class="fa-arrow-right">:arrow-right:</i> PrPr2

This section describes the data model changes between [`prpr1`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide/access-summary-export-schema-reference-guide.md) and `prpr2`.

You can move to the new model by simply changing your create table S3 paths to `prpr2`; `prpr1` will no longer get files.

### New tables

* [`datasource-metadata`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#datasource-metadata): This table now serves as your primary asset registry, removing technical redundancy from the `tag-metadata` table.
* [`column-metadata`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#columns): This table prepares your model for the upcoming column-level access policy outcomes.&#x20;
* [`access-requests`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#access-requests): This table provides the primary sources for Request app access requests (who requested, what asset, what they submitted, and the request’s current/terminal status) to support access reporting and downstream audit analytics.
* [`request-determinations`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#request-determinations): This table provides additional insights into the determinations from access requests. Use this table with the `access-requests` and `policy-outcomes` tables to track a request from approval through access.
* [`request-duas`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#request-duas): This table allows you to directly map access requests to the data use agreements the requestors are signing.
* [`data-products`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#data-products): This table provides the primary source for Request app data products to support product-level access insights.
* [`data-product-assets`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#data-product-assets): This table maps with the `data-products` table to detail the exact data sources and columns within a particular data product.

### Updated tables

* [`policy-outcomes`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#policy-outcomes): The `column_id` field has been added to `policy-outcomes`. It will be `NULL` for your current table-level data but will populate automatically as Immuta begins exporting column-level masking outcomes ([Reveal policies](/saas/govern/secure-your-data/authoring-policies-in-secure/data-policies/reference-guides/data-policies.md#reveal-policies)). The `scope` field has also been added and represents if the merged policy is a `WRITE` or `READ` policy.
* [`tag-metadata`](/saas/govern/detect-your-data/access-summary-export/latest-access-summary-export-schema-reference-guide.md#tag-metadata): The redundancy was moved into the `datasource-metadata` table. `data_source_id` changed to `target_id` and `target_type`, which allows the `tag-metadata` table to directly reference both table tags and column tags. Since column IDs are strings, when joining on `target_id` to any other `data_source_id`, you will need to cast to text. Use this option as an example (dependent on your database's sql syntax):&#x20;

```
JOIN datasource-metadata on datasource.id::TEXT = tag.target_id AND tag.target_type = 'DATA_SOURCE' 
JOIN column-metadata on column.id = tag.target_id AND tag.target_type = 'COLUMN'
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.immuta.com/saas/govern/detect-your-data/access-summary-export/early-access-data-model-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.