> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/explorer/accessing-a-private-collection.md).

# Accessing a Private Collection

How to access registered or controlled access Collections

[Explorer](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/explorer/broken-reference/README.md) allows researchers to access both registered and controlled data collections through [Passport](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/explorer/broken-reference/README.md) authentication. This guide explains how to access each type of collection.

## Registered Access Collections

To access a registered collection:

1. Click on a registered collection from Explorer
2. Click "Log in with Passport" on the collection overview page
3. Sign in using your preferred authentication method
4. Once authenticated, you'll have immediate access to the collection's data

## Controlled Access Collections

For collections requiring approval:

1. Navigate to the controlled collection in Explorer
2. Click "Request Access" on the collection overview page
3. Complete the request form with:
   * Your full name
   * Email address
   * Optional note explaining your request purpose
4. Submit your request and await email notification of approval

## After Approval

Once your access request is approved:

1. Return to the collection in Explorer
2. Sign in with your Passport account
3. Access the collection's data, including tables and metadata

{% hint style="info" %}
Collections may have different data access requirements based on their sensitivity and usage policies. Contact collection administrators for specific access questions.
{% endhint %}


---

# 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://docs.omics.ai/products/explorer/accessing-a-private-collection.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.