Identify which processes depend on the departing person's identity before removing their account. Do not assume that sharing a credential makes the underlying connection independent of its owner.
Distinguish two sharing arrangements
n8n documents that shared credentials can be used by others without those users viewing or editing credential details. Availability differs between n8n Cloud and self-hosted editions.
The documentation also distinguishes sharing an end-user credential: users connect their own account rather than using the owner's connection. These arrangements should occupy different rows in an offboarding map because their identity dependencies are different.
The supplied evidence does not establish exactly what account removal will break in your installation. That outcome needs a scoped review, not a blanket prediction.
Draw an identity-dependency map
For every affected business process, connect five references: process, credential arrangement, underlying service identity, accountable service owner and replacement decision.
Add these review fields:
- Is the connection a shared saved credential or an end-user arrangement?
- Which identity actually authorises the external service use?
- Has the relevant sharing availability been verified for the edition?
- Who can approve continued use after the person leaves?
- What evidence will demonstrate that the replacement arrangement works?
- Who owns a manual fallback if the process is interrupted?
Use internal identifiers rather than secrets or private account details. Ask whether organisational permission and consent cover the planned transition; do not treat this checklist as legal advice.
Assess a hypothetical departure
Suppose a hypothetical Ahmedabad team reviews three synthetic demonstration processes before a contractor leaves. Process A uses a shared saved connection, Process B asks each operator to connect their own account, and Process C has an undocumented identity.
For A, investigate the underlying identity instead of assuming sharing transfers ownership. For B, evaluate each relevant operator's connection rather than treating the contractor's connection as universal. For C, mark the process blocked for transition until its identity is understood.
Evaluate the map by whether each process has an authorised replacement or an explicit retirement decision. A copied workflow or an available teammate is not sufficient evidence of a valid connection.
Coordinate offboarding without bypassing security
Stop declaring the transition complete while identity-dependent processes remain unexplained. Next, arrange authorised validation with synthetic inputs and record fallback owners. If an account must be removed urgently for security reasons, follow that decision and manage interruption rather than preserving access informally.
If the team needs replacement tool access, check the AI tools catalog, verify access format and save terms before buying. Marketplace account, code or token offers do not prove official subscription equivalence or transfer the departing person's service identity.
Sources and scope
Source material checked 29 October 2026; features/policies may change. n8n secure credential sharing establishes the sharing, identity and edition distinctions above. The dependency map and hypothetical offboarding decisions are editorial advice, not guaranteed account-removal outcomes.