What revocation actually changes
Revoking a trusted organization is a permission change, not a deletion of the organization’s records. Before you click revoke, separate three things: future write access, what remains visible to that organization, and records it supplied earlier.
ORCID lists authorized organizations on the Trusted parties page, where the owner can revoke access. Source
The practical consequence is that revocation stops new authorized activity but does not reach into the organization’s own systems. If a publisher or funder imported your ORCID iD into its workflow, its copy of that record is outside ORCID’s control.
Build the matrix before you revoke
Use one row per organization. The columns below match the three claims in this guide; fill them from what you know about each organization’s role, not from assumptions.
| Organization | Why it has access | Items it added to your record | Items it can still read after revocation | Action |
|---|---|---|---|---|
| Example publisher (hypothetical) | Author workflow | Publication entry, affiliation | Public record plus its own imported data | Revoke if the workflow is finished |
| Example institution (hypothetical) | Employment verification | Employment entry | Public record plus its own imported data | Revoke or keep, depending on ongoing updates |
Editorial advice, not a platform rule: treat any organization that is still expected to update your employment, education or publication entries as one to keep until the update is complete. Revoking early can leave a record that only you can maintain.
What the organization can still see
After revocation an organization can still read public information and information it added itself. Source
So “revoked” does not mean “blind.” Public information stays public, and anything the organization itself added remains readable to it. If the concern is visibility rather than write access, revocation alone will not solve it; you would need to review what is public on your record.
What the organization can still change
A revoked organization cannot add or edit items but can still delete items it previously added. Source
The asymmetry matters: write access narrows, but deletion of its own previously added items remains possible. If a record must survive, confirm with the organization how it handles deletions before you revoke, rather than after.
A usable checklist
- List every trusted organization and note why it has access.
- Mark which items on your record each organization added.
- Decide whether each organization still needs to add or edit anything.
- For organizations you will revoke, ask how they treat records they previously supplied.
- Revoke only after steps 3 and 4 are settled.
- Re-check your public record afterward; revocation changes permissions, not public visibility.
Failure paths to plan for
- Revoking mid-update. If an institution is still processing an employment or publication update, revocation can interrupt it. Wait until the update appears on your record.
- Expecting deletion. Revocation does not delete the organization’s copy. If that copy matters, raise it with the organization directly.
- Expecting privacy. Public information remains readable. Review your public record separately if exposure is the concern.
- Assuming the list is complete. A trusted-party list covers authorized integrations, not every place your name or iD appears. For a broader sweep of public profiles, see how to find all accounts linked to a name.
What this guide does not establish
The exact menu labels, confirmation screens and any waiting period for revocation are not covered by the approved facts here, so treat them as unverified and check the current ORCID interface. This guide also makes no claim about how quickly an organization’s systems update after revocation.