logo
  • What is SeqsLab?
  • Run your first job

Tutorials

  • Deployment
    • Test drive SeqsLab
      • Data registration
      • Tool registration
      • Workflow execution
    • Deploy SeqsLab on Azure
      • Register an Azure resource provider
      • Create a SeqsLab workspace
      • Grant tenant-wide admin consent to the SeqsLab Enterprise Application
      • Request Azure backend quota
      • Manage SeqsLab users
  • CLI
    • Pull and run the SeqsLab CLI
  • Data Hub
    • Upload and register files using the SeqsLab CLI
  • Tools
    • Create an input JSON file
    • Validate workflow scripts
    • Register a TRS tool to the SeqsLab platform
      • Develop a tool
      • Configure the execution file
      • Register a tool
  • Jobs
    • Run a job
  • Run Sheet
    • Create a SeqsLab Run Sheet for sequencing experiments
    • Use the SeqsLab Run Sheet with the CLI

Tasks

  • Manage your jobs
  • Manage your labels

Case studies

  • GATK4 Germline SNPs Indels
  • GATK4 Joint Genotyping
  • Hi-C Data Processing

Explanations

  • SeqsLab Platform
    • SeqsLab on Azure
    • Security
      • Authentication
        • OAuth 2.0 and authentication flow
        • SeqsLab API tokens
      • Authorization
        • Role-based access control (RBAC)
        • Roles
        • Cybersecurity assurance
    • Compliance
  • SeqsLab Data Hub
  • SeqsLab Jobs
    • Workflow engine
    • Workflow description
      • WDL best practice guidelines
      • WDL workflow inputs
  • Operator pipelines
    • Operators
    • Operator types
  • API
    • Data repository service
      • SeqsLab DRS API
    • Tool registry service
      • SeqsLab TRS API
    • Workflow execution service
      • SeqsLab WES API

References

  • CLI commands
    • Authentication subcommands
    • Data Hub subcommands
    • Work Execution Service (WES) subcommands
    • Role subcommands
    • Tool Registry Service (TRS) subcommands
    • User subcommands
    • Workspace subcommands
  • Operator pipelines
  • API references
    • DRS API reference
    • TRS API reference
    • WES API reference
Contact Atgenomix Support
  • .md
Contents
  • Next steps

Grant tenant-wide admin consent to the SeqsLab Enterprise Application

Contents

  • Next steps

Grant tenant-wide admin consent to the SeqsLab Enterprise Application#

The global administrator should grant tenant-wide admin consent to the SeqsLab Enterprise application, so that all existing Azure Active Directory (AD) users can sign in to the SeqsLab platform. It is recommended to use the Azure AD account assigned as the Global Administrator in Step 6 of SeqsLab on Azure.

Use the following command to grant admin consent in your Azure subscription:

seqslab user admin-consent

This command opens a browser page where you can complete the process.

Next steps#

If you are deploying SeqsLab on Azure, below are the next steps in the process:

  1. Request quota

  2. Manage users

previous

Create a SeqsLab workspace

next

Request Azure backend quota

By ATGENOMIX, Inc.
© Copyright 2023.

All Atgenomix products and services are for research or investigational use only, and should not be used for diagnostic purposes.