---
title: "Repository workspaces in Relativity aiR"
description: "Set up repository and review workspaces from the same template in Relativity aiR, and move data between them with Integration Points using matching fields."
feature: "Workspaces"
audience: ["end user", "developer", "system analyst", "system administrator", "system engineer"]
version: "Relativity aiR"
type: ["User Guide", "Tutorial"]
url: "https://help.relativity.com/RelativityaiR/Content/Relativity/Workspaces/Repository_workspaces_in_RelativityOne.htm"
lastModified: "2026-11-20"
---

# Repository workspaces in Relativity aiR

When setting up a workspace for documents, it is useful to understand that Relativity aiR provides administrators the flexibility to setup a workspace either as a regular workspace or as a [repository workspace](https://help.relativity.com/RelativityaiR/Content/Relativity/RelativityOne_document_repository.md).

This topic highlights some of the items that admins need to be aware of as they create the repository workspace in Relativity aiR. It also covers how to prepare and handle the flow of data between the review and the repository workspaces.

## Setting up a repository workspace

All organizations start with a [template](https://help.relativity.com/RelativityaiR/Content/Getting_Started/RelativityOne_Workspace_Templates.md) that is shipped with Relativity aiR or a template that is customized for your instance that meets your workflow requirements. The workflows described here will apply towards all such template workspaces in your Relativity aiR environment.

Here are some advantages of executing these workflows in the below scenarios to designating repository / review workspaces:

- You have the same fields / layouts / views available in both workspaces (repository and review) so the learning curve for the teams administering the case is minimal.
- When you promote data between repository and review workspace (using[Integration Points](https://help.relativity.com/RelativityaiR/Content/Relativity/Integration_Points/Exporting_data_through_Integration_Points.md#Exporting_to_a_Relativity_workspace)) you can use the same field names and types to push data between them, reducing the opportunity for errors since both workspaces are born out of Template Review Workspace (Workspace –A) originally.

Below, we'll describe two scenarios for creating a Repository Workspace, followed by a few quick workflows that will come in handy as you use those workspaces.

## Example: creating a repository template from a review template

You currently have a Review Template (Workspace-A). You can create a new workspace (Workspace-Z) from Workspace-A, add the Repository application to Workspace-Z and designate it as a Repository Template.

1. In Repository Template Workspace-Z remember to setup the appropriate security groups that limit access to case admins and disable access to the reviewer groups.
2. You have two designated workspace templates – one for review (Workspace–A) and one for repository (Workspace-Z).
3. You can create Review Workspace-B and Repository Workspace-Y from these templates.  
   ![Creating repository workspace example 1](https://help.relativity.com/RelativityaiR/Content/Resources/Images/Features/Workspaces/DGM_Repository_Workspaces_in_RelOne_Scenario1.png)

## Example: converting an active review workspace into a repository workspace

You currently only have a Review Template Workspace-A. You have created a new Review Workspace-M and loaded data into it and are well into review. With time you receive more data and the size of the workspace is expected to increase dramatically.

At this point, you can still take advantage of the Repository feature and here is how:

1. Create a new review workspace called Workspace-N (from Template Workspace-A).
2. Now, add the Repository application to the original Review Workspace-M and from this point on it becomes your repository workspace.
3. Turn off Review access to Workspace-M.
4. Promote the reviewed data from Workspace-M to your new Review Workspace-N.
5. Proceed with review in Workspace-N.  
   ![Creating repository workspace example 2](https://help.relativity.com/RelativityaiR/Content/Resources/Images/Features/Workspaces/DGM_Repository_Workspaces_in_RelOne_Scenario2.png)

## Special considerations

### Loading and promoting data

- Administrators can load data in using [Import/Export](https://help.relativity.com/RelativityaiR/Content/Relativity/Import_Export/Import_Export_Overview.md).
- Repurpose some of the suggested Data Load / Analytics / Searching Dashboards to facilitate analysis and culling your data sets for promotion.
- Promotion works in both directions. You can promote documents and metadata from the repository workspace to the review workspace, and overlay coding, such as privilege designations, from the review workspace back to the repository workspace.
- Tag promoted documents on an admin field in the repository workspace to make quality control easier.
- If you promote a subset of documents, such as inclusive, non-duplicate emails or documents from certain clusters, and then rerun email threading or clustering in the review workspace, the results differ from the repository workspace. This is by design.

### Billing for promoted documents

How Relativity bills promoted documents depends on whether you promote them as links or as physical copies.

| Promotion method | Where the files are stored | How the files are billed |
| --- | --- | --- |
| Links Only | In the repository workspace only. The review workspace holds links to the files. | Once, at the review rate. The size is reported on the repository workspace in the Billable Linked File Size field. The same documents promoted to several review workspaces are charged once. |
| Physical files | In both workspaces. | The copy in the repository workspace at the repository rate, and the copy in the review workspace at the review rate. Refer to your contract for how this is calculated. |

To avoid being billed for the same data in two workspaces, promote documents to review workspaces with the Links Only option rather than copying files.

> **Note:** Links in the review workspace break if you delete the linked documents in the repository workspace, or if you delete or ARM archive the repository workspace. Before you migrate a repository workspace to Cold Storage, see [Repository workspaces and linked files](https://help.relativity.com/RelativityaiR/Content/Relativity/Workspaces/Cold_Storage.md#Repository).

### Processing in a repository workspace

1. Administrators can load data in using [Import/Export](https://help.relativity.com/RelativityaiR/Content/Relativity/Import_Export/Import_Export_Overview.md) and processed data via Relativity Processing in the repository.
2. If you are loading data via [Import/Export](https://help.relativity.com/RelativityaiR/Content/Relativity/Import_Export/Import_Export_Overview.md):
   1. Watch out for deduplication challenges across the mixed data.
   2. To avoid errors on retry (of processing errors), use unique control numbers that will not conflict with the Relativity Processing Numbering scheme (Ex: HardCopy-xxxxx or LoadFile-xxxxx).
3. Process data with deduplication turned off on the processing profile and use the [Processing Duplication Workflow](https://help.relativity.com/RelativityaiR/Content/Relativity/Processing/Processing_duplication_workflow.md) to cull your data. It provides better flexibility in case of changes in dedupe order / type.

### Analytics across repository and review workspaces

1. For structured analytics sets - Evaluate if you need to repopulate text or update only new documents. For more information, see [Running structured analytics](https://help.relativity.com/RelativityaiR/Content/Relativity/Analytics/Running_structured_data_analytics.md).
2. For conceptual indexes – Evaluate if you need to do a full index update or an incremental one. For more information, see [Best practices for updating an index](https://help.relativity.com/RelativityaiR/Content/Relativity/Analytics/Analytics_indexes.md#Best).
3. When clustering documents, evaluate if you would like to cluster the entire universe or just a subset of documents based on your needs.
