ORCID Researcher Connect is a member-exclusive institutional feature, launched by ORCID on 3 February 2026, that lets member organisations automatically notify affiliated researchers who hold a verified institutional email on their ORCID record but have not yet linked that record to the institution’s own systems. Researcher Connect is ORCID’s automated, institution-triggered notification workflow: it closes the gap between a researcher having a verified email-domain affiliation and that researcher actively authorising an institution to read and write data on their record.
For research offices, the launch matters because it converts a largely manual outreach problem — chasing researchers to link accounts — into an automated, recurring workflow built into the ORCID registry itself. This article sets out what the feature actually does, how it differs from a standard affiliation claim, what a pilot cohort of seven institutions found, and exactly what a research office must configure before it can switch Researcher Connect on.
- What is ORCID Researcher Connect?
- How does it differ from a standard affiliation claim?
- How does the notification workflow operate?
- What must a research office configure?
- What did the pilot cohort show?
- Frequently asked questions
- Implications and outlook
What is ORCID Researcher Connect?
Researcher Connect is a benefit available to ORCID member organisations with an active integration capable of adding and updating affiliations. It builds directly on ORCID’s verified institutional email domains, a trust-marker feature launched in 2024. According to ORCID’s own 3 February 2026 announcement, more than four million active ORCID records now carry a verified institutional email domain — a large pool of researchers who are identifiable to an institution but not necessarily connected to that institution’s integrated system.
Researcher Connect uses that verified-domain data to find the gap: researchers whose ORCID record shows a verified @institution.ac.uk-style email but who have never granted the institution’s system permission to read from or write to their record. The feature then automates the outreach that would otherwise require a manual email campaign from the research office.
How does it differ from a standard affiliation claim?
A standard affiliation claim on ORCID can be added in three ways: a researcher self-reports it manually, a member organisation adds it via API after the researcher has already authorised a connection, or the institution’s Affiliation Manager tool pushes bulk affiliation records. Researcher Connect sits upstream of all three — it is the mechanism that gets an unconnected researcher to the point of authorisation in the first place, rather than a way of writing affiliation data once permission already exists.
Crucially, ORCID’s documentation states that Researcher Connect is not available to institutions that only use Affiliation Manager, because Affiliation Manager already generates its own researcher notifications. The two are complementary, not interchangeable, and a research office needs to know which workflow it is already running before requesting activation.
| Mechanism | Who initiates it | Trigger | Requires prior authorisation? |
|---|---|---|---|
| Manual self-report | Researcher | Researcher edits their own record | No — researcher-entered directly |
| Affiliation Manager | Institution (bulk upload) | HR/HRIS data feed | Institution-managed; sends its own notifications |
| Standard API affiliation write | Institution’s integration | Researcher has already connected | Yes — OAuth already granted |
| ORCID Researcher Connect | ORCID, on the member’s behalf | Verified email domain + no existing connection | No — this is the step that obtains authorisation |
How does the notification workflow operate?
Once enabled, ORCID runs the matching and notification cycle automatically. Eligible researchers are identified daily, and notifications are sent at 1pm UTC to everyone matching the institution’s supplied email domains who has not connected and has not already received a Researcher Connect notification from that member within the past year.
- Researchers receive an ORCID-inbox message and, depending on their notification-frequency settings, an email invitation.
- The notification links to the institution’s own ORCID landing page, where the researcher signs in and authorises the connection via OAuth.
- If no action is taken, ORCID sends one reminder notification after 30 days.
- The full cycle repeats annually, or immediately whenever a researcher newly adds a matching verified institutional domain to their record.
Once a connection is authorised, the institution can add employment affiliations directly to the record, and those affiliations carry ORCID Trust Markers — signals that the underlying data was asserted by a verified institutional source rather than self-reported.
What must a research office configure?
ORCID’s documentation sets three prerequisites before Researcher Connect can be activated, and none of them involve new engineering work — the feature is delivered on ORCID’s side once the following are in place.
- An active ORCID member integration that can add and update affiliations (not Affiliation Manager alone).
- A verified list of institutional email domains the institution wants ORCID to match against, supplied to the ORCID Engagement Support Lead.
- An ORCID landing page — a maintained institutional webpage explaining why researchers should connect, what data will be read or written, and a clearly labelled “Connect with ORCID” button leading directly to the sign-in flow.
Research offices supplying organisation identifiers for affiliation records should also note that ORCID stopped receiving updates to the legacy Ringgold identifier database on 1 August 2023 and now recommends the Research Organization Registry (ROR) identifier for parent-organisation entries — a detail worth checking before any bulk affiliation push, since stale Ringgold-only records will not resolve correctly going forward. Institutions without an existing member integration must first join ORCID membership before Researcher Connect becomes available at all.
What did the pilot cohort show?
ORCID piloted Researcher Connect with seven member organisations ahead of the full rollout: Bodleian Libraries at the University of Oxford, Erasmus University Rotterdam, Dun Laoghaire Institute of Art, Design and Technology, Aalborg University, Aarhus University, Imperial College London, and the University of Vienna. Across the pilot period, ORCID reports that these institutions connected over 5,700 previously unconnected users and updated their records with verified affiliations.
Jason Partridge, Collections Support Senior Manager at the Bodleian Libraries, University of Oxford, described the effect of verified institutional linkage on researcher behaviour: the verified link with the institution “gives a feeling that this makes it ‘official’ and tracks as part of the CV element that the ORCID profile offers a user” — a signal ORCID also cites as driving disproportionate uptake among early-career researchers specifically.
Frequently asked questions
Does ORCID cost money?
An ORCID iD is free for individual researchers to register and use for life. Institutions, however, must hold an active ORCID membership, which carries fees, and maintain a working member API integration before they can enable Researcher Connect notifications for their affiliated researchers.
How do I connect my ORCID iD?
A researcher clicks the “Connect” button in a Researcher Connect notification, which opens the institution’s ORCID landing page. From there, they sign in with their ORCID credentials and authorise the connection via OAuth, granting the institution permission to add or read affiliation data on their record.
What is ORCID connecting research and researchers?
ORCID is a non-profit organisation providing a free, persistent digital identifier — the ORCID iD — for researchers, alongside a registry linking that identifier to institutional affiliations, funding and publication records across nearly 1,200 member integrations spanning universities, publishers and funders worldwide.
Implications and outlook
For research offices, Researcher Connect shifts affiliation-verification effort from repeated manual email campaigns to a maintained landing page and a supplied domain list — a lower ongoing burden once the initial setup is done. It also raises the bar for what “current affiliation data” means: with Trust Markers now distinguishing institution-asserted affiliations from self-reported ones, downstream consumers of ORCID data — funders, publishers, national assessment exercises — have a stronger basis for treating ORCID affiliation fields as verified rather than declarative.
Institutions running research administration workflows around grants, compliance reporting or researcher CV verification should treat the feature as an operational dependency: enabling it changes who initiates the affiliation-linking conversation, from the researcher to ORCID itself, on the institution’s behalf. Offices that have not yet reviewed their eligibility — an active affiliation-capable integration, a domain list and a landing page — should raise the requirement with their ORCID Engagement Support Lead as a discrete, low-effort configuration task rather than a development project.
Leave a Reply