(concepts:seqslab-console)=
# SeqsLab console overview

The SeqsLab console is the primary web application for managing genomic and health-data workflows. After you sign in, the console presents the modules and actions that your account is authorized to use within your organization.

## Sign-in and organization context

- Sign in with your organization's Microsoft Entra ID (Azure AD) workforce account.
- The first time you access SeqsLab, your administrator must have assigned you to the correct organization and role.
- If your account belongs to more than one organization, verify that you are working in the intended organization. Data and jobs are isolated between organizations.

For deployment and sign-in prerequisites, see [Deploy SeqsLab on Azure](../tutorials/deploy-seqslab-on-azure) and [Authentication](authentication).

## Fast path by user type

- **ReporterDataEntryOperator, MedicalTechnologist, BioinformaticsScientist, LaboratorySupervisor,** or **MedicalDirector** who process patient samples should start with {ref}`tutorials:reporter-overview`.
- **BioinformaticsScientist** or **JobExecutor** who run workflows should start with {ref}`tutorials:jobs` and [Tools](../tutorials/tools).
- **GlobalAdministrator** or **OrganizationAdministrator** who manage users, organizations, and workspaces should start with [Deployment](../tutorials/deployment) and {ref}`security:rbac`.

## Console areas

The console is organized into three broad areas. The modules available to you depend on your subscription, backend, and assigned roles.

### Platform administration

Administrators configure the organization, members, and compute environment.

| Module | Typical users | Purpose |
| --- | --- | --- |
| **Organization** | GlobalAdministrator, OrganizationAdministrator | View or update organization settings. |
| **Users and roles** | GlobalAdministrator, UserAdministrator | Invite members, assign roles, deactivate accounts, manage API tokens. |
| **Workspace** | GlobalAdministrator | Create and monitor the cloud backend resources (storage, compute) used for processing. |
| **Container Registry** | GlobalAdministrator, OrganizationAdministrator | Manage tool and workflow images. |

### Research operations

Researchers and bioinformaticians manage data, tools, and workflow executions.

| Module | Typical users | Purpose |
| --- | --- | --- |
| **Data Hub** | DataHubViewer, DataHubWriter | Register, browse, and version datasets and files. |
| **Tools** | ToolRegistryWriter, ToolUser | Register and inspect containerized tools and workflows (TRS). |
| **Jobs** | JobExecutor, JobAdministrator | Submit, monitor, rerun, and inspect workflow executions (WES). |

### Clinical operations

Clinical and laboratory staff manage the Reporter sample-to-report workflow.

| Module | Typical users | Purpose |
| --- | --- | --- |
| **Reporter** | ReporterDataEntryOperator, MedicalTechnologist, BioinformaticsScientist, LaboratorySupervisor, MedicalDirector | Register patients and samples, upload data, run analyses, review results, and issue signed clinical reports. |

See {ref}`tutorials:reporter-overview` for the Reporter entry point.

## Role awareness

The console hides or disables actions that your role is not authorized to perform. However, a visible button does not by itself mean the action is allowed for your role. If an action fails with a permission error, confirm your assigned role with your SeqsLab administrator and review {ref}`security:healthcare-rbac` for Reporter roles or {ref}`security:rbac` for platform roles.

## Where to go next

- New to SeqsLab? Start with [Deploy SeqsLab on Azure](../tutorials/deploy-seqslab-on-azure).
- Need to register a patient sample? See {ref}`tutorials:reporter-register-sample`.
- Need to understand the full clinical workflow? See {ref}`tutorials:reporter-sample-lifecycle`.
- Looking for endpoint details? See the API reference section.