What actually changes when you move the default
The default visibility control is a forward-looking setting. It decides how newly added record data is treated; it does not reach back into entries already on the record.
ORCID default visibility applies to newly added record data. Source
That is the practical point of confusion: a researcher who switches the default to a more restricted option may reasonably assume the whole profile tightened. It did not. The setting governs the next things added, not the current contents.
Changing the default does not overwrite visibility of existing record items, which have individual selectors. Source
So after changing the default, the old works, affiliations and other entries are still governed by whatever visibility each item already carries. If you want a tighter record, the work is item by item — there is no single switch that rewrites history.
Four things people merge into one
A record audit goes wrong when these are treated as a single visibility state. Keep them separate:
| Layer | What the setting does | What you must do |
|---|---|---|
| The ORCID iD | Stays public | Treat it as an identifier you publish, not something the default hides |
| Existing items | Keep their own selectors | Open and review each item individually |
| Future items | Follow the new default | Check the default is what you intend before adding more |
| Email addresses | New ones default to Only me | Review any existing addresses separately |
The ORCID iD itself remains public; new email addresses default to Only me. Source
The iD line matters most for expectations. A researcher who restricts the default and expects the profile to become hard to find is working from the wrong model: the identifier remains public, and the visibility setting is about record data, not about withdrawing the iD from circulation.
A field-by-field audit checklist
Work through the record in this order. The steps describe what to inspect; the exact menu labels and controls in your ORCID account are not established by the sources reviewed here, so locate each section yourself rather than relying on a quoted path.
- Confirm the current default. Before touching items, verify which visibility the default now applies to. This is the baseline for anything you add later.
- List every item on the record. Works, affiliations, funding, invitations and other entries each appear as separate items. Do not assume a category is uniform.
- Open each item and read its own selector. Record the visibility shown against each entry — this is the operative state, not the default.
- Flag mismatches. Any item whose visibility is broader than you now intend goes on a short fix list.
- Change flagged items individually. Each item has its own selector, so this is a per-item edit, not a bulk setting.
- Review email addresses. New addresses default to Only me, but check what is already listed and what each entry shows.
- Re-check after editing. Confirm the item now shows the visibility you chose; an edit that did not save looks identical to one you never made.
- Record what you changed and when. A short personal log makes the next audit faster and stops you re-litigating the same entries.
Decision criteria for each item
Use these questions to decide whether an item needs changing:
- Is this item accurate? Visibility is the second question; a wrongly attributed work should be corrected or removed regardless of who can see it.
- Does the item’s visibility match its sensitivity? A published article and a funding entry may not warrant the same setting.
- Would a broader setting expose something you would not say publicly? If yes, narrow that item.
- Are you changing this because of a policy requirement? If so, note the requirement and the date you addressed it, so a later reviewer can see the reasoning.
Items that already match your intent need no action. Resist the urge to touch everything — each edit is a chance to introduce an error.
Failure paths to expect
Assuming the default covered old items. This is the central failure. The default is not retroactive, so a record can look unchanged after a settings change.
Editing the profile text and calling it done. A revised biography or trimmed profile does not change the visibility of individual works or affiliations, and it does not establish that any stored data was removed.
Expecting anonymity from a visibility change. The iD remains public, and narrowing record items does not make the researcher unfindable. Visibility settings manage record data; they are not an anonymity tool.
Expecting ORCID edits to propagate to employer systems. Changing a record does not edit an employer’s HR, faculty or repository system. If an institution holds its own copy of your details, that copy is a separate matter and outside what an ORCID visibility change does.
Treating a saved edit as verified. Re-open the item. The sources reviewed here describe selectors, not save behaviour, so verification is your own check.
Where this audit fits a wider footprint review
An ORCID record is one public surface among several a researcher may maintain. If the goal behind the visibility change is a broader tidy-up of what a name turns up, the ORCID audit is a good starting point because the record is structured and itemised. From there, a sensible next step is to look at the other profiles attached to the same name using how to find all accounts linked to a name — with the caveat that username matches are leads, not proof of ownership, and a search cannot produce a complete account inventory.
TraceSeek, the app covered by TruthsSeek, lists 3,000+ platforms and runs a free first scan; the product states a scan takes 20-30 seconds. It is a discovery aid for public profiles, not a verification service and not a substitute for editing your ORCID record directly.
Recap
After changing the ORCID default, the only thing that changed is what future additions will do. Existing items keep their individual selectors; the iD remains public; new email addresses default to Only me. The audit is therefore manual and per item, and the useful output is a short fix list plus a record of what you changed.
Editorial note on sourcing
This article separates what the reviewed ORCID claims establish — the scope of the default setting, per-item selectors, the public iD and the email default — from editorial advice about how to run an audit. The checklist order, decision questions and failure paths are recommendations, not platform rules. Specific menu locations and control labels were not established by the reviewed material and are deliberately not described.