> 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/workbench/getting-started/log-into-workbench.md).

# Logging into Workbench

## Overview

Workbench uses [Passport](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/workbench/getting-started/broken-reference/README.md), DNAstack's digital identity management system, to handle user authentication and permissions. Passport is specifically designed for federated research environments where data is distributed across multiple locations and organizations.

## Authentication Requirements

Workbench authentication is currently handled through Google Single-Sign-On (SSO). You'll need a Google account to access the platform, regardless of which cloud platforms or engines you plan to use. This login is separate from any accounts used for cloud resource access.

{% hint style="info" %}
Don't have a Google account? You can [register your existing email ](/products/passport/register-account-with-google.md)address with Google using their [account creation guide](https://support.google.com/accounts/answer/27441?hl=en\&co=GENIE.Platform%3DAndroid).
{% endhint %}

## Login Process

To access Workbench:

1. Go to workbench.omics.ai
2. Click "Log in with Passport"
3. Select "Sign in with Google"
4. Choose your Google account when prompted

After successful authentication, you'll land on the Monitor page, where you can view your workflows and their status.


---

# 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/workbench/getting-started/log-into-workbench.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.