eRA Commons ID

What the eRA Commons ID is for

NIH’s Electronic Research Administration (eRA) system is the backbone through which institutions and individuals submit, track, and report on NIH grant applications and awards. Every individual who needs a defined role in that process — applying, reviewing progress, managing a training appointment, or administering an institution’s NIH portfolio — is issued an eRA Commons ID tied to their own account. The ID functions as a persistent login credential and role marker: it determines what a person can see and do inside eRA Commons and its connected modules, and it is how NIH associates a specific individual with a specific application, award, or trainee appointment over time.

Who needs one

NIH requires an active eRA Commons ID for:

• The Program Director/Principal Investigator (PD/PI) on any NIH application or award.
• All other Senior/Key Personnel and Other Significant Contributors named on an application.
• Trainees on training and career-development mechanisms (e.g., T32, F31, F32, K awards), who are registered and tracked through xTrain.
• Signing Officials (an institution’s Authorized Organizational Representative) and Account Administrators, who manage account creation and institutional eRA Commons profiles.
• Anyone entering or editing data directly in ASSIST on behalf of an application.

How registration works

Registration is institution-mediated, not self-service. A person cannot create their own eRA Commons ID; a Signing Official or Account Administrator at an eRA Commons-registered institution must create the account and assign the appropriate role (e.g., PI, trainee, Account Administrator). For trainees specifically, the supervising PI can initiate registration by inviting the trainee through an xTrain appointment, or the institution’s Signing Official/Account Administrator can create the account directly. Because the Commons ID is meant to persist across a person’s NIH-facing career, moving institutions typically means re-affiliating an existing Commons ID rather than issuing a new one — preserving a continuous record of that individual’s role across applications and awards.

Where it’s used

The same Commons ID authenticates a person across several linked eRA systems:

• eRA Commons itself — the account/profile hub, status tracking, and the Personal Profile page where an individual links other identifiers (such as an ORCID iD).
• ASSIST — NIH’s online system for preparing and submitting grant applications and multi-project/complex applications.
• xTrain — the module for appointing, tracking, and reporting on trainees under NIH training and career-development awards.
• RPPR — the Research Performance Progress Report, NIH’s standard mechanism for annual and final progress reporting, which pulls on Commons-registered personnel and trainee data.

How it differs from other identifiers

An eRA Commons ID is easy to conflate with adjacent identifiers because NIH’s application and reporting workflow now touches several of them at once. It is not an ORCID iD: NIH requires Senior/Key Personnel to link their ORCID iD to their eRA Commons Personal Profile as part of application validation, but the ORCID iD is a universal, portable researcher identifier usable across publishers, other funders, and institutions, while the Commons ID is specifically an NIH eRA account credential. It is also not a general institutional login, a grants.gov/SAM.gov registration (which operates at the organizational rather than individual level), or a degree/professional credential — it is strictly the account-level credential that authorizes a specific person’s role inside NIH’s eRA ecosystem.

Why it matters for research administration

Because self-registration is not possible, eRA Commons ID issuance is a recurring administrative dependency for sponsored-programs offices: new hires who will serve as PI or key personnel, incoming trainees, and newly designated Signing Officials all require timely account creation before an application, progress report, or trainee appointment can be submitted. Missing or unlinked Commons IDs (or an unlinked ORCID iD for Senior/Key Personnel) are a common source of submission validation errors on NIH applications, making the Commons ID one of the more operationally consequential — if administratively invisible — pieces of NIH grants infrastructure.

Related terms

• ORCID iD
• ORCID iD for NIH Senior/Key Personnel
• ORCID Sign-In / Authentication
• Office of Extramural Research (OER)
• NIH Grants: An Overview

Frequently asked questions

Can a PI create their own eRA Commons ID?

No. A PD/PI cannot self-register; their institution’s Signing Official or an Account Administrator must create the account and assign the PI role.

Does an eRA Commons ID change if a researcher moves institutions?

Typically the existing Commons ID is re-affiliated with the new institution rather than replaced, so the individual keeps one ID across their NIH-facing career.

Is an eRA Commons ID the same as an ORCID iD?

No. They serve different purposes and NIH requires them to be linked, not treated as interchangeable — see the ORCID iD and ORCID iD for NIH Senior/Key Personnel entries linked above.

Who needs an eRA Commons ID besides the PI?

All Senior/Key Personnel and Other Significant Contributors named on an application, trainees on training/career-development awards (via xTrain), Signing Officials, Account Administrators, and anyone entering data directly in ASSIST.