> For the complete documentation index, see [llms.txt](https://documentation.dnanexus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.dnanexus.com/admin/trusted-research-environments/creating-a-tre.md).

# Create and Publish a Trusted Research Environment

Step-by-step guide for TRE Admins to create, configure, and publish a new Trusted Research Environment on the DNAnexus Platform.

{% hint style="info" %}
Apollo and Trusted Research Environments licenses are required to use Trusted Research Environments on the DNAnexus Platform. [Contact DNAnexus Sales](mailto:sales@dnanexus.com) for more information.
{% endhint %}

Learn how to make your data discoverable using a Trusted Research Environment (TRE) on the DNAnexus Platform.

## Before You Begin

Make sure you've done the preparatory work described in [planning a TRE](/admin/trusted-research-environments/planning-a-tre.md). If you are creating a file-only TRE, follow [Prepare a Resource Inventory for a File-Only TRE](/admin/trusted-research-environments/preparing-resource-inventory-for-file-only-tre.md) to organize the inventory projects and prepare the File Inventory TSV and Data Collections JSON.

Confirm the following before you start creating your TRE:

* Your File Inventory TSV and Data Collections JSON are uploaded to DNAnexus.
* If your file-only TRE uses an optional Participant IDs (PID) CSV, the closed file is uploaded to the same project as the File Inventory.
* If your TRE includes a Tabular Data Inventory, your Apollo Dataset is ingested and accessible.
* If your TRE includes a Data Showcase, your Apollo Dataset is in a **separate project** from your other inventory resources.
* All inventory assets are in the same region as the TRE you are creating.
* You know how many review steps your pipeline needs and who to assign as reviewers.

## Step 1: Create the Research Environment

1. In the platform navigation menu, go to **Orgs** > **Your Org**.
2. Click the **TRE** tab.
3. Click **+ New Research Environment** in the top right corner.
4. Complete the following fields in the **New Research Environment** modal:
   * **TRE ID** — A unique, lowercase, alphanumeric handle for the environment.
   * **Name** — The display name shown to researchers browsing **Data Resources** > **Resource Center**.
   * **Description** — A detailed description of the data offering.
   * **Region** — The cloud region where the data is hosted.
   * **Customized Rate Card** — Controls how compute costs are billed to researchers. Select **Yes** to have the platform create a dedicated billing org (wallet) for each approved data access request, with pricing inherited from the organization hosting the TRE. Leave as **No** to have researchers bill to their own org wallet. This setting cannot be changed after creation. For details and prerequisites, see [planning your billing configuration](/admin/trusted-research-environments/planning-a-tre.md#plan-your-billing-configuration).
5. Click **Create Research Environment**.

{% hint style="warning" %}
The **TRE ID** is permanent and cannot be changed after the TRE is created. In the TRE UI, the **Region** and **Customized Rate Card** fields are also locked after creation, even while the TRE is in the `draft` lifecycle state. The **Name** and **Description** can be updated at any time.
{% endhint %}

## Step 2: Configure Membership

Open the newly created TRE and navigate to the **Membership** section. Add TRE Admins and the initial Authorized Users who you want to be able to discover and access the environment. If your TRE includes a Data Showcase, you must be an Admin in the Data Showcase project to add Authorized Users.

For more details, see how to [manage TRE membership](/admin/trusted-research-environments/configuring-tre-membership.md). Membership can be updated at any time regardless of lifecycle state.

## Step 3: Configure the Resource Inventory

The Resource Inventory links your prepared inventory assets to the TRE. Contact [DNAnexus Professional Services](https://www.dnanexus.com/professional-services) for assistance preparing these files before continuing.

1. Navigate to the **Resource Inventory** section and click **Configure Resource Inventory** to open the **Resource Inventory Settings** modal.
2. Provide a semantic **Version** string for this inventory release, for example `1.0.0`.
3. Enter the `project-xxxx:file-yyyy` identifier for each file-based inventory asset:
   * **File Inventory** — Your File Inventory TSV (`project-xxxx:file-yyyy`).
   * **Data Collections** — Your Data Collections JSON file (`project-xxxx:file-yyyy`).
   * **Participant IDs (Optional)** — Appears when both **Enable Data Showcase** and **Tabular Data Inventory** are set to **No**. Enter the `project-xxxx:file-yyyy` identifier of your closed Participant IDs CSV file to override automatic participant ID derivation from the File Inventory TSV. For formatting requirements and examples, see [Prepare the Participant IDs (PID) CSV](/admin/trusted-research-environments/preparing-resource-inventory-for-file-only-tre.md#prepare-the-participant-ids-pid-csv-optional).
4. If your TRE includes tabular phenotypic or clinical data, set **Tabular Data Inventory** to **Yes** and enter the `project-xxxx:record-yyyy` identifier of your tabular Apollo Dataset.
5. If your TRE includes pre-request data browsing or cohort selection, set **Enable Data Showcase** to **Yes** and enter the `project-xxxx:record-yyyy` identifier of your showcase Apollo Dataset. This dataset must be in a separate project from your File Inventory and Tabular Data Inventory.
6. If your TRE includes assay data, add one entry per assay with the **Assay Dataset** (`project-xxxx:record-yyyy`), **Assay Linking Database** (`project-xxxx:database_name`), and **Assay Field ID** (along with the working project for assay processing). Assays can only be configured when **Tabular Data Inventory** is enabled. Contact [DNAnexus Professional Services](https://www.dnanexus.com/professional-services) for guidance on configuring assays.

{% hint style="warning" %}
Resource Inventory settings can only be configured or updated when the TRE is in the **Draft** or **Maintenance** state. You cannot modify the inventory while the TRE is Active.
{% endhint %}

## Step 4: Configure Data Access Policies

1. Under **Data Access Policies**, click **Configure Policies**.
2. For each policy, select one of three options:
   * **Enforce on** — The restriction is enforced on all projects in this TRE, regardless of individual project settings.
   * **Enforce off** — The restriction is explicitly disabled for all projects in this TRE.
   * **Defer to project settings** — Individual project owners control this setting.
3. Click **Save**.

## Step 5: Configure Data Governance

1. Under **Data Governance**, click **Configure Data Governance**.
2. Review the available governance settings.
   * **Pseudonymization** — When enabled, the platform replaces participant identifiers with unique pseudonyms across tabular, assay, and file data on dispensal. This setting is permanent and can be set only when the TRE is in the Draft state. To learn more about how pseudonyms are generated and mapped, see [pseudonymization in TREs](/admin/trusted-research-environments/pseudonymization.md).
3. Click **Save**.

## Step 6: Configure Data Showcase and Selection

Navigate to the **Data Showcase and Selection** section. If your governance policy requires all researchers to access data for all participants without cohort filtering, enable **Enforce Full Set Selection**. When enabled, researchers' data access requests always include all participants in the dataset.

If you do not configure a Data Showcase, the TRE must use **Enforce Full Set Selection**. Researchers cannot select cohorts, but they can still select data collections and submit access requests.

{% hint style="warning" %}
This setting can only be configured in **Draft** state and cannot be changed or disabled after the TRE is published.
{% endhint %}

## Step 7: Configure the Review Workflow

Navigate to the **Review Settings** section and add the review steps you planned. Assign at least one reviewer to each step.

For details, see how to [manage review steps and reviewers](/admin/trusted-research-environments/configuring-review-workflow.md). The TRE must have at least one review step with at least one reviewer assigned before you can publish it.

## Step 8: Publish the Research Environment

Once your membership, inventory, policies, and review pipeline are configured, you can publish the TRE to make it visible to Authorized Users. You can also publish with no Authorized Users configured and add them later.

When published, the TRE enters the **Active** state. Authorized Users can immediately discover the environment in **Data Resources** > **Resource Center**, explore the Data Showcase (if one exists), and submit access requests.

1. Click **Administrative Actions** (gear icon) at the top right.
2. Select **Publish Environment**.
3. Review the confirmation checklist:
   * Your review steps are finalized. After publishing, you cannot add, remove, or reorder steps, but you can update step names and descriptions.
   * Your Resource Inventory is correctly linked with valid file and record IDs, and any optional Participant IDs CSV file is closed and validated.
   * Your data access policies and Data Governance settings reflect the appropriate restrictions for your data. Irreversible choices, including pseudonymization and Enforce Full Set Selection, cannot be changed after publishing.
4. Click **Confirm and Publish**.

To update the resource inventory after publishing, or to deactivate or delete the TRE, see [Manage TRE Lifecycle](/admin/trusted-research-environments/managing-tre-lifecycle.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.dnanexus.com/admin/trusted-research-environments/creating-a-tre.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.