Overview of Account Setup

To use AnVIL, you will need a Google account for authenticating with Terra and Gen3 and to associate your Terra account with a Google Cloud Platform (GCP) account.

If you will be accessing controlled-access data, you will also need an eRA commons id or to be a member of a data sharing consortium.

To enable dbGaP data use authorizations to flow through from dbGaP to Terra, you will need to link your Terra account with your eRA commons ID and your Gen3 account.

The guides below walk you through each step in the account setup process.

Account Setup Checklist

  1. Set up a Terra account - To register for a Terra account, you will need a Gmail account or another email account (an institutional email, for example) associated with a Google identity.
  2. Set up Terra account with non-Google email - If your email is not associated with a Google identity, follow these steps to create a Google account that is associated with your non-Gmail, institutional email address.
  3. Set up a Gen3 account Create a Gen3 account by logging in with your NIH, Google, or RAS login credentials. This allows you to use the Gen3 data explorer to create artificial cohorts over AnVIL datasets that have been indexed by Gen3.
  4. Link your Gen3 and Terra accounts - Follow these step-by-step instructions to link your Gen3 credentials to your Terra account. This allows you to analyze Gen3 data on Terra.
  5. Link your Terra and eRA Commons ID - To use controlled-access data on Terra, you will need to link your Terra user ID to your authorization account (such as a dbGaP account). Linking to external servers will allow Terra to automatically determine if you can access controlled datasets hosted in Terra (ex. TCGA, TOPMed, etc.) based on your approved dbGaP applications.

Next, see Requesting Data Access for more information about obtaining access to controlled access data and configuring Terra and Gen3 to read your data access privileges from dbGaP or your consortia access control list.

Understanding Cloud CostsObtaining a Google ID
Improve this pageContent guide