Even if you use the same email address, switching login providers (e.g. ID.me or Login.gov) may cause the system to treat you as a new user.
This is because:

• Each identity provider shares different information with Lasso.
• Our system treats the email + login method combination as unique.

So even if the email is the same, the login method matters — and if the email is already in use with another login provider, you’ll be sent to the registration page and unable to continue.

NOTE:  You cannot register twice with the same email, even across different login providers.

Your NBDC Datasharing account on Lasso is tied to the email address and identity provider (e.g. ID.me or Login.gov) you used when you first signed up.If you change the email address in your ID.me or Login.gov account and then log into Lasso using that new email, the system will treat you as a new user, and:

• You’ll be redirected to the registration page, and
• You will not see any of your previous data or access, because it is linked to your original email.

If there's a compelling reason to change your login email, please consult your identity provider’s help resources:

• ID.me Help Center
• Login.gov Help Center

If you use a different identity provider (such as switching between ID.me and Login.gov), the system may treat you as a new user because each provider shares different information with Lasso login service. As a result, you might be redirected to the new account registration form. However, since your email address is already associated with an existing account, you will not be able to complete the registration. To avoid this issue, please continue using the same identity provider you originally used to create your account.

All ABCD data associated with an NDA DUC must be deleted no later than the DUC expiration date.

While individuals can obtain their own DUCs, a group-level DUC is recommended. This approach allows all recipients to be listed together. A dashboard allows the lead investigator to manage the addition or removal of recipients.

Trainees must be included on an investigator-led group DUC.

Yes, an institutional signing official must sign off on each DUC in order for all recipients to gain access to the data. If new recipients are added onto a group DUC, the institutional signing official must re-sign the updated DUC.

The group-level DUC facilitates this process as the lead investigator will oversee trainees and others listed under the DUC and is responsible for ensuring their compliance with its terms and conditions.

No, prior ABCD data releases are not available on the NBDC platform. As a reminder, each data release is cumulative and includes data from all previous timepoints.

Yes, you may use the 5.1 data until your NDA DUC expires. At that time, all data associated with that DUC must be deleted.

DUCs are not transferable between institutions. Recipients must notify the NBDC platform at nbdc@mail.nih.gov when moving to a new institution. A new DUC must then be submitted with appropriate sponsorship from the new institution to retain access. For group-level DUCs, the lead investigator may designate another lead investigator at the original institution as a replacement.

Each past data release prior to the 6.0 data release has a unique Digital Object Identifier (DOI) that is indexed on the NIMH Data Archive (NDA). To properly cite data from a past release, please use the DOI associated with that specific release. Citing the correct DOI ensures accurate attribution and supports transparency and reproducibility.

If you have both a general DUC and an A-DUC, they will be linked and the A-DUC will have the same expiration date as the general DUC.

Your institution must comply with federal security standards—specifically NIST SP 800-171 or equivalent ISO/IEC 27001/27002 standards. View the NIST Security Compliance Requirements.

For NIH Users Only: Use the “Short” Email Format for Your Signing Official. When completing your Data Access Request in the NBDC Data Hub, you may use any NIH email for your own contact information. However, when entering the email address of your NIH Institutional Signing Official (business official), you must use their “short” NIH email format. This format ensures proper routing and validation within NIH systems.

‍

For example, if your signing official’s name is Jane Smith,  their email could be either:

• smithj@nih.gov (use this one)
• jane.smith@nih.gov (do not use this one‎)

Please enter: smithj@nih.gov

If your Signing Official did not receive the Data Use Certificate from Docusign, they should search their inbox for the subject line “Complete with DocuSign: Data Use Certificate for research on NBDC Data Group.” The sender will appear as dse_NA4@docusign.net. If the message is not found, it’s important to check the Spam, Promotions, or Junk folders. Their IT department should also confirm that the domain  @docusign.net has been whitelisted. If the email still cannot be located, please contact the NBDC Support email to have the request reissued.

The training email is only sent after you have logged into the NBDC Datasharing Platform for the first time. If you have already logged in, search your inbox for the subject line “Responsible Data Use Training,” and be sure to check all folders, including Spam or Promotions. You can also confirm whether the training has been unlocked by navigating to the Data Access (DUC) module in the platform and looking for the orange "Start Training" Button.

If you began the Data Use Certification (DUC) process using a personal or non-institutional email address, you need to restart with your institutional email.

Most personal email domains are blocked (e.g., Gmail, or a custom domain that's not institutionally recognized), but if yours isn’t, please don’t proceed, your request will still be declined by the Data Access Committee (DAC).

To correct this:

1. Log in to Datashare using the personal email you originally used.
2. In the Data Access module, click Cancel Request to remove the current DUC.
3. Log out, then sign in via RAS using your institutional email address (e.g., ending in .edu, .org, or your organization’s domain).
4. The DUC form will now auto-fill with your institutional email.
5. Re-complete and sign the DUC form to submit your request properly.

Note for Lead Investigators: Be sure to log in using your institutional email. For any sub-applicant you add to the DUC, please use their institutional email address as well. They should then authenticate via RAS and log into the platform using that same institutional email.

If you’ve received approval from the Data Access Committee and completed your Responsible Data Use Training but are still unable to download data, please check the following:Are you listed as a sub-applicant? If so, your ability to download data depends on your lead investigator’s status.

‍

If the lead investigator has not completed their Responsible Data Use training, sub-applicants will not be granted download access—even if their own training is complete.

‍

Next Steps:

• Confirm with your lead investigator that they have completed their training.
• If they have, and you’re still experiencing issues, please contact Lasso Support via the Help Center in the NBDC Data Sharing platform.