> 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/publisher/getting-started.md).

# Getting Started

## Getting Started with Publisher

Publisher enables organizations to make file and table data available through GA4GH APIs. The system serves two distinct user types:

* **Administrators**: Use [Publisher's](https://publisher.staging.dnastack.com/welcome)[ web-based interface](https://publisher.staging.dnastack.com/welcome) to connect data sources, organize data into Collections, and implement access policies
* **Data Consumers**: Access Collection data through [GA4GH](https://www.ga4gh.org/)-compliant software, such as [Explorer](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/getting-started/broken-reference/README.md) for interactive data discovery and analysis, or the [DNAstack Python library](/products/analysis/python-library.md) for programmatic analysis

This documentation is intended for **Publisher Administrators**.

### Prerequisites

Before beginning with Publisher, identify the data sources you want to make available. Publisher supports the following data storage systems:

## Supported Storage Systems

Publisher can connect to data stored on Google Cloud Platform (GCP), Amazon Web Services (AWS), Microsoft Azure, and some on-premises or vendor-neutral systems:

Files:

* [Amazon S3](/products/publisher/data-sources/connectors/connecting-to-aws-s3-storage.md)
* [Azure Blob Storage](/products/publisher/data-sources/connectors/connecting-to-microsoft-azure-blob-storage.md)
* [Google Cloud Storage (GCS)](/products/publisher/data-sources/connectors/connecting-to-google-cloud-platform.md)
* [Any unauthenticated HTTPS URL](/products/publisher/data-sources/connectors/connecting-to-https.md)

Tables:

* [PostgreSQL](/products/publisher/data-sources/connectors/connecting-to-postgresql.md)

## Implementation Process

Working with Publisher involves these essential steps:

* [Sign in](/products/publisher/getting-started/logging-in-to-publisher.md) to Publisher's web interface
* Connect one or more [data sources](/products/publisher/data-sources.md), populating Publisher's library with tables and files
* Create named [Collections](/products/publisher/collections.md) of tables and files
* Define [access policies](/products/publisher/access-policies.md)
* Create [Questions](/products/publisher/questions.md)
* [Share](/products/publisher/collections/sharing-a-collection.md) Collection metadata, tables, and files according to the desired access policies

{% hint style="info" %}
Detailed instructions for each step are available in the corresponding sections of the Publisher documentation, accessible through the left-hand navigation menu.
{% 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/publisher/getting-started.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.