Skip to main content
v2026.11,610 entries · CC-BY 4.0
Dictionary termTrack Proposedv2026.1

eRA Commons: Accounts, Roles, ORCID Linking & Troubleshooting

eRA Commons (commons.era.nih.gov) is NIH's web-based portal for post-submission electronic Research Administration: the system where a Principal Investigator, institutional Signing Official, or other registered role accesses and manages an NIH application and award after it has been submitted through Grants.gov. Grants.gov is where an application package is transmitted to NIH; eRA Commons is where nearly everything that happens to it afterward -- assignment tracking, summary statements and scores, Just-in-Time (JIT) submissions, Research Performance Progress Reports (RPPR), ORCID linkage, no-cost extension requests, prior-approval requests, and final closeout -- takes place. A task counts as "in eRA Commons" if it requires an eRA Commons account and role-based login (era.nih.gov credential) to view or act on, as distinct from the one-time act of transmitting an application via Grants.gov.

ByCASRAI Editorial Board
· Last updated 16 Aug 2026

Ask about eRA Commons: Accounts, Roles, ORCID Linking & Troubleshooting

Answers are drawn from this dictionary entry and the rest of the CASRAI corpus, with a link to every source.

Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this

Examples

Worked examples

  • Is an instance

    A grantee institution's Signing Official logs into eRA Commons to submit a Final RPPR within 120 days of a project period's end, one of the three documents required for NIH closeout alongside the Final Federal Financial Report and Final Invention Statement.

  • Is an instance

    When a program officer requests Just-in-Time information after a fundable score, the PI or their delegate uploads Other Support and IRB/IACUC approval documentation through the JIT module inside eRA Commons -- this happens before an award is issued, not before the application was submitted.

  • Is an instance

    A PI's Signing Official uses eRA Commons' expanded-authority Status screen to notify NIH of a one-time, no-prior-approval no-cost extension, available in roughly the 90 days before a project period's end date.

  • Is an instance

    A postdoc registers for My NCBI/SciENcv using their eRA Commons sign-in and then links their ORCID iD from the eRA Commons Personal Profile page, satisfying NIH's requirement that senior/key personnel have an ORCID iD connected to their Commons account.

Counter-examples

Looks similar, but isn't

  • Not an instance

    Submitting the initial SF424 (R&R) application package itself happens through Grants.gov (or, increasingly, NIH's ASSIST system built on top of it), not eRA Commons -- eRA Commons only becomes the system of record once NIH has received and validated that submission.

  • Not an instance

    A reviewer's substantive scientific critique of an application is written and managed through NIH's separate Internet Assisted Review (IAR) module, not through general eRA Commons account functions, even though IAR is accessed via an eRA Commons login.

Editorial commentary

Quick answer: eRA Commons is NIH’s account-based portal at public.era.nih.gov/commons for everything that happens to an NIH application or award after submission — status tracking, Just-in-Time (JIT), RPPRs, ORCID linkage, and closeout. You cannot register yourself; your institution’s Signing Official or Account Administrator creates your account. The sections below cover the actual tasks people search for: creating an account, finding your Commons ID, understanding roles, linking ORCID, and fixing the errors that show up most often.

What eRA Commons is

eRA Commons is the National Institutes of Health’s web-based system for electronic Research Administration (eRA) — the online portal where institutions, investigators, and NIH staff carry out nearly every step of NIH grant administration that happens after an application has been submitted. It sits alongside Grants.gov and NIH ASSIST (the application-preparation and submission side of the eRA system) as the administration side: the place a Principal Investigator (PI), Signing Official (SO), Business Official, or other registered role logs in to track an application’s status, respond to award conditions, and manage a funded project through to closeout.

Access to eRA Commons is not optional for anyone with a defined role in an NIH award. NIH’s Grants Policy Statement requires PDs/PIs and other Senior/Key Personnel named on an application to be registered in eRA Commons and to include their eRA Commons ID in the application itself, before the application can be reviewed. Once an application clears Grants.gov submission and validation, status tracking, JIT, Notice of Award access, RPPR, xTrain, prior-approval and no-cost-extension requests, and closeout all run through eRA Commons — see CASRAI’s guides to the NIH RPPR, JIT submission process, and NIH Closeout for detail on each.

How to create an eRA Commons account

The single most common misconception about eRA Commons is that a researcher can sign up the way they would for most web accounts. They can’t. Individuals cannot self-register. A Signing Official (SO) or Account Administrator (AA) at an already eRA Commons-registered institution creates every individual account and assigns it one or more roles. If your institution has never registered in eRA Commons at all, the SO registers the institution first, which is a separate, one-time step from creating individual PI or staff accounts.

If you’re a PI, trainee, or staff member who needs an account, the request goes to your institution’s SO or AA (usually in the sponsored programs or research administration office), not to NIH directly. For the exact screen-by-screen steps an SO or AA follows — including institutional vs. individual registration and setting up a new PI, trainee, or staff account — see CASRAI’s How to Set Up an eRA Commons Account guide.

eRA Commons roles: who can do what

Every eRA Commons account is assigned one or more roles, and the role — not just having an account — determines what a login can see and do. Roles also determine who can legally commit the institution: a PI can prepare and route an application or report, but only an SO can formally submit most of them to NIH.

Role Who holds it What it can do
Signing Official (SO) Institutional grants official Broadest authority: registers the institution, creates any account type, legally binds the institution, and is the only role that can formally submit most applications and post-award actions to NIH.
Administrative Official (AO) Grants/research administration staff Creates most account types (not SO, BO, or FCOI); can receive PI delegation for status checks and RPPR editing.
Account Administrator (AA) Departmental or central admin staff Narrower account-management role; typically handles routine registration of new PIs and trainees.
Business Official (BO) Sponsored programs/finance staff Financial and business certifications, e.g. Loan Repayment Program (LRP) IBO certifications.
Principal Investigator (PI) Project’s responsible investigator Initiates, edits, and manages their own applications and most reports; cannot submit without SO sign-off.
Assistant (ASST) PI’s delegate Views/edits the PI’s profile and assists with applications and reports on the PI’s behalf, without holding the PI role.
Trainee roles Undergrad, grad student, postdoc, project personnel Limited to their own personal profile and institution profile; tracked through xTrain on training and career-development awards.
FSR / FCOI / PACR / IAR Specialized reporting staff / peer reviewers Scoped to Federal Financial Reports, conflict-of-interest disclosures, Public Access Policy reporting, or peer review (IAR), respectively.

This is a condensed summary — see CASRAI’s eRA Commons Roles for the full permission structure, including exactly how delegation works between a PI and an AO or ASST.

Finding your eRA Commons ID

Your eRA Commons ID (sometimes called your Commons username or Person ID) is the identifier that has to match exactly what’s entered in an application’s Senior/Key Person profile — a mismatch is one of the most common causes of an eRA “Not Registered” validation error at submission. If you’re already logged in, your own ID is visible on your Personal Profile page. If you need to look up someone else’s — a co-investigator, a new trainee, or your own ID after you’ve forgotten it — an SO or AA can search for it in the institution’s account roster. See CASRAI’s How to Look Up an eRA Commons ID for the exact navigation path in both cases, and eRA Commons ID for how the identifier itself is issued and structured.

Linking your ORCID iD to eRA Commons

Since NIH Guide Notice NOT-OD-26-018, senior/key personnel named on an application must have an ORCID iD connected to their eRA Commons account, and as of May 8, 2026 (NOT-OD-26-079) that check is a hard error at submission, not a warning. The connection happens on your eRA Commons Personal Profile page, not inside the application form itself:

  1. Log into eRA Commons with your own individual account credentials.
  2. Select Personal Profile from the left-hand menu.
  3. Click Create or Connect Your ORCID iD, then sign in with an existing ORCID account or register a new one.
  4. On the ORCID authorization screen, click Authorize Access so eRA Commons can read your ORCID record.

An ORCID iD can be linked to only one eRA Commons account at a time — if you’ve ever had two Commons accounts (common after an institutional transfer), the ORCID iD may already be tied to the wrong one, and unlinking or reassigning it requires the eRA Service Desk; it isn’t self-service. Linking ORCID to eRA Commons is a separate step from linking ORCID to My NCBI/SciENcv (which is what actually populates a biosketch document) — CASRAI’s full ORCID-to-SciENcv linking walkthrough covers both connections step by step.

Login.gov and two-factor authentication

NIH requires eRA Commons accounts to authenticate through Login.gov, the federal government’s shared identity-verification and multi-factor authentication (MFA) service, rather than a Commons-only username/password. If you’re setting up Commons access for the first time or your institution is migrating existing accounts, you’ll be prompted to create or link a Login.gov account and register an MFA method (authenticator app, security key, or similar) as part of account access. If Login.gov sign-in fails or loops back to a login screen, that’s typically a Login.gov-side MFA or account issue rather than an eRA Commons account problem — Login.gov has its own separate help channel, and the eRA Service Desk (below) can confirm which side an issue is on.

Maintaining your Personal Profile

Your eRA Commons Personal Profile is more than a login screen — it’s where NIH pulls Senior/Key Person information from for applications and reports, so keeping it current avoids validation failures later. It holds your degrees and institutional affiliation history, your linked ORCID iD, your eRA Commons roles, and (for PIs) any delegate assignments such as an ASST authorized to edit on your behalf. Trainees’ Personal Profiles are the record xTrain draws on for appointment and termination forms (PHS 2271, PHS 416-7).

How to route and submit an RPPR in eRA Commons

RPPRs are drafted and routed, not just filled in and submitted directly. Only the PD/PI (or their PD/PI delegate) can initiate an RPPR; from there it’s routed for internal review — typically department administrators, the sponsored-programs office, and back to the PD/PI — using the Route to Next Reviewer action, and only a Signing Official can formally submit it to NIH. If a report is routed to the wrong person or gets stuck, it can be recalled (by whoever routed it, the last reviewer, or — while it’s in Reviewer Work in Progress status — an SO or the Contact PD/PI) rather than restarted. Full section-by-section RPPR guidance, including report types and deadlines, is in CASRAI’s NIH RPPR: How to Complete the Research Performance Progress Report.

Troubleshooting: common eRA Commons problems

Problem Likely cause Fix
“Not Registered” error at submission A named Senior/Key Person has no eRA Commons account, or the Commons ID on the application doesn’t match their account exactly SO or AA creates/verifies the account before resubmission; confirm the ID via the ID lookup guide
ORCID won’t link, or shows “already connected” The ORCID iD is already linked to a different eRA Commons account Contact the eRA Service Desk — unlinking/reassigning an ORCID connection is not self-service
Can’t log in, or Login.gov keeps looping Login.gov account not yet linked, or an MFA device issue Re-register your Login.gov MFA method, or contact the eRA Service Desk to confirm which system the failure is on
Account locked after failed sign-in attempts Too many failed login attempts Contact the eRA Service Desk to unlock — you cannot self-reset a lock
RPPR stuck in “Reviewer Work in Progress” Report was routed to a reviewer who is unavailable or unaware Whoever routed it, the last reviewer, or (while in that status) an SO or the Contact PD/PI can recall and re-route it
JIT request you expected doesn’t appear NIH hasn’t issued the JIT request yet, or your role lacks visibility into it Confirm timing with the assigned Program Officer; check that your role has JIT access
Forgot your Commons ID or username Check your Personal Profile if logged in, or ask your SO/AA to search the institution’s account roster

Is eRA Commons down? Checking system status

eRA Commons doesn’t publish a real-time public status dashboard the way many commercial SaaS products do. If the system seems unresponsive or you’re getting unexpected errors close to a deadline, the fastest ways to confirm whether it’s a genuine outage are: check for a banner or alert on the eRA Commons login page or era.nih.gov itself, and call the eRA Service Desk directly: 1-866-504-9552 (press 1 for eRA Commons or ASSIST) or 301-402-7469, Monday-Friday, 7 a.m.-8 p.m. ET (busiest 10 a.m.-3 p.m. ET). If you’re up against a submission deadline and suspect a genuine system-side issue rather than a local one, document it immediately — screenshot, exact error text, and timestamp — and contact your Signing Official and the eRA Service Desk right away rather than waiting; NIH’s own guidance (SF424 Application Guide and Grants Policy Statement) addresses system-issue submission problems, but only for issues reported and evidenced promptly, not after the fact.

eRA Commons vs. related NIH and NSF systems

eRA Commons is frequently confused with the systems around it. Grants.gov is the government-wide portal used to transmit a completed application package to NIH; NIH ASSIST is NIH’s own application-preparation tool that feeds into that same transmission step; eRA Commons is where everything happens once NIH has the application in hand. A person can have an ASSIST or Grants.gov login without ever touching eRA Commons, but cannot manage an active NIH award without one. See CASRAI’s eRA Commons vs. Grants.gov comparison, NIH ASSIST vs. eRA Commons Registration, and eRA Commons vs. Research.gov (NSF’s equivalent system) for full side-by-side detail.

Frequently asked questions

What is eRA Commons?

eRA Commons is NIH’s web-based portal for managing an NIH grant application and award after it has been submitted — status tracking, JIT, RPPR, ORCID linkage, and closeout, accessed at public.era.nih.gov/commons.

How do I create an eRA Commons account?

You don’t create it yourself. Your institution’s Signing Official or Account Administrator creates it and assigns your role(s). See the account setup guide for the exact steps they follow.

What is an eRA Commons ID?

It’s the individual login/identifier tied to your account, which has to match exactly what appears in an application’s Senior/Key Person section. See eRA Commons ID and the ID lookup guide.

Is my NIH biosketch prepared in eRA Commons?

No — as of 2026, NIH biosketches are built in SciENcv (My NCBI), not directly in eRA Commons. eRA Commons is where you link the ORCID iD that SciENcv and NIH’s submission validations both rely on. See CASRAI’s SciENcv biosketch guide.

How do I check eRA Commons status if I think it’s down?

There’s no public status dashboard; check the login page/era.nih.gov for an alert banner, or call the eRA Service Desk at 1-866-504-9552 (option 1). See the troubleshooting section above.

What are the eRA Commons roles?

PI, Signing Official (SO), Administrative Official (AO), Account Administrator (AA), Business Official (BO), Assistant (ASST), trainee roles, and several specialized reporting roles (FSR, FCOI, PACR, IAR). See the roles table above and eRA Commons Roles for full detail.

Related CASRAI resources

Content last verified against era.nih.gov and grants.nih.gov sources on 2026-08-16.

Machine-readable encodings

Use in your systems

JATS XML <role> element
xml
<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="eRA Commons: Accounts, Roles, ORCID Linking & Troubleshooting"
      vocab-term-identifier="https://casrai.org/dictionary/term/era-commons" />
Schema.org DefinedTerm (JSON-LD)
json
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/era-commons",
  "name": "eRA Commons: Accounts, Roles, ORCID Linking & Troubleshooting",
  "identifier": "https://casrai.org/dictionary/term/era-commons",
  "description": "eRA Commons (commons.era.nih.gov) is NIH's web-based portal for post-submission electronic Research Administration: the system where a Principal Investigator, institutional Signing Official, or other registered role accesses and manages an NIH application and award after it has been submitted through Grants.gov. Grants.gov is where an application package is transmitted to NIH; eRA Commons is where nearly everything that happens to it afterward -- assignment tracking, summary statements and scores, Just-in-Time (JIT) submissions, Research Performance Progress Reports (RPPR), ORCID linkage, no-cost extension requests, prior-approval requests, and final closeout -- takes place. A task counts as \"in eRA Commons\" if it requires an eRA Commons account and role-based login (era.nih.gov credential) to view or act on, as distinct from the one-time act of transmitting an application via Grants.gov.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/grants-management#set",
  "url": "https://casrai.org/dictionary/term/era-commons",
  "sameAs": [],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-08-16T21:22:50",
  "inLanguage": "en"
}

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →