Productivity & Workflows
Sharing an n8n Workflow: Check Credential Use Before Adding a Teammate
Two completed fictional CRM sharing decisions distinguish existing credential use, protected node edits, direct credential grants and broader project roles; no account or credential changes.
Before sharing an n8n workflow, list the services it can access and the actions it can perform through its credentials. A teammate may be able to run an existing workflow with credentials that were never shared directly with them. Secret values can remain hidden while the workflow still lets the teammate act through the connected account.
This LandOffer guide turns that distinction into a completed permissions review for a fictional CRM synchronization workflow. Official n8n documentation was checked on October 25, 2026. The examples are documentation-grounded planning records, not account tests: no credentials, memberships, workflows, exports, or executions were accessed or changed.

Check the sharing route and the available role first
The current workflow sharing documentation lists all n8n Cloud plans and self-hosted Business and Enterprise. Older search snippets may describe narrower availability. Use the current body, then verify the installed version, deployment, subscription, and actual controls before proposing an access change. Availability of sharing does not mean every plan offers the same roles.
A workflow in a Personal workspace can be shared with individual users through its sharing controls. For a workflow inside a project, n8n directs you to project membership instead: the workflow belongs to that project's shared scope. Adding someone to a project therefore requires reviewing the other resources there, not only the workflow that prompted the request.
The project documentation explains that projects group workflows and credentials and that a user can have different roles in different projects. Write down the project, its resources, current members, and proposed role before discussing an invitation. Instance-level privileges also matter; don't use an instance owner as the representative test account for an ordinary teammate.
The distinction changes a seemingly simple request. “Let Ren help with contact formatting” specifies work, not a permission level. Establish whether Ren needs to inspect a diagram, review past data, run a workflow, change a mapping, or administer membership. If the actual controls cannot separate those needs appropriately, leave the proposal pending rather than assigning a broader role merely to unblock the invitation.
Separate credential use from editing and secret visibility
n8n's workflow sharing page says workflow editors can use credentials already used by a shared workflow, including credentials not explicitly shared with them. It also says editors cannot edit nodes using unshared credentials, while they can view and run the workflow and edit other nodes. These are different capabilities; a protected credential node does not make the surrounding workflow read-only.
The page's creator/editor table includes execution viewing, updating, running, and exporting for editors, while sharing and deleting are reserved to the creator in that table. Keep this Personal-workflow sharing model separate from project roles. Do not apply its delete restriction to every user whose role happens to contain the word “Editor.”
The credential sharing documentation describes another grant: sharing a credential allows its use in the recipient's own workflows, without viewing or editing the credential details. It also distinguishes end-user credentials, where recipients connect their own accounts. Identify the actual credential type before assuming every shared credential uses the original owner's connection.
Review both the n8n grant and the connected service's scope. A CRM token capable of writing contacts remains a write-capable service connection even if the teammate cannot read its token string. Ask the service owner which tenant, objects, operations, and environments the connection permits. A friendly credential name such as “CRM sync” does not establish read-only access or limit writes to the records visible in a sample.
Case one: a CRM workflow permission matrix changes the decision
The following is a fully fictional design review. Amara owns Contact Normalize in a Personal workspace. Its stated business purpose is to normalize company names and update a CRM contact's company field after an approved internal mapping review. Ren is asked to help diagnose an incorrect abbreviation, using invented records only.
The workflow contains four steps: fetch a CRM contact, transform its company name, update that contact, and write a short result to an operations log. Credential C1 is an ordinary stored CRM service credential used by both CRM nodes; C2 authenticates the logging destination. Neither is an end-user credential. Both credential details remain owned by Amara, and neither has been explicitly shared with Ren.
Amara's invented inventory records the CRM connection as production-capable with contact read and update permissions. The logging connection can write a result containing a contact reference and before/after company text. Those scopes are assumptions of this example, not claims about an n8n integration's default scopes.
| Resource or capability | Before proposed sharing | Expected after Personal workflow editor sharing | Review consequence |
|---|---|---|---|
| Workflow definition | Ren has no access through this route | Can view and update within documented restrictions | More than a diagram review |
| Existing CRM and log credential use | No workflow access through this route | Can run existing workflow using C1 and C2 | Includes CRM update and log write capability |
| Nodes using unshared C1/C2 | No access | Cannot edit those protected nodes | Restriction does not prohibit running them |
| Company-name transform node | No access | Can edit this non-credential node | Changed output may affect downstream update |
| Executions | No access through this route | Can view workflow executions | Review retained payload exposure |
| Credential details | Not shared | No direct credential grant proposed | Secret invisibility is not an execution boundary |
The phrase “through this route” is deliberate. The fictional baseline assumes Ren has no other project or instance grants; a real reviewer must verify that assumption. Every after-sharing entry is a documentation-based expectation; no teammate login or account check took place.
The completed review rejects the initial proposal for this task. Ren only needs to reason about the transformation, yet the proposed workflow share includes running the existing write-capable flow. Locking the CRM node's parameters does not isolate its input from changes in the preceding transformation. This is a reason to inspect the data path, not a claim that a secret has been extracted.
Amara's alternative is an approved review package containing invented input/output examples and a diagram with no live connections. Ren would review “North Ridge Ltd.” becoming “North Ridge” and flag that “NR Labs” must remain unchanged because the abbreviation is ambiguous. The fictional decision leaves production workflow sharing and credential sharing unapproved. A separately authorized isolated test may be considered later; none was created or run for this article.
Case two: project membership exposes a broader maintenance scope

A second fictional team has a different need. Tariq is expected to maintain the normalization workflow over a month, not merely review a mapping. The workflow is in the Customer Operations project alongside Renewal Notices and Account Cleanup, plus the project's credentials. Project admin Jo must review membership and role scope before adding Tariq.
The available roles page describes Project Editors as able to view, create, update, and delete workflows, credentials, or executions within the project. It describes Project Viewers as read-only across project resources and unable to manually execute project workflows. Its role availability is plan-specific, so an owner must check actual entitlement rather than assume a Viewer option exists.
Jo's fictional inventory finds that Account Cleanup has a production deletion path. Tariq's maintenance task concerns Contact Normalize only; seeing the wider project and receiving edit/delete powers over its resources is a materially broader proposal. A project name does not narrow that scope to the workflow mentioned in the request.
The completed review record compares the proposed states:
| Check | Captured baseline assumption | Expected proposed Project Editor state | Disposition |
|---|---|---|---|
| Contact Normalize definition | No project membership or other grant | Editing possible under the project role | Needed, subject to review |
| Renewal Notices and Account Cleanup | Outside Tariq's existing scope | Project resources included | Broader than assigned task |
| Project credential management | No project role | Broad resource rights described for Editor | Requires explicit owner assessment |
| Execution records | Not accessible through project membership | Project execution access included | Payload handling review needed |
| Viewer alternative | Not assigned | No manual execution; read-only project scope | Cannot satisfy maintenance editing |
| Actual account verification | Not performed | Still not performed | Cannot mark onboarding complete |
Jo defers membership in the broad project. The written proposal is a dedicated maintenance project containing only the reviewed normalization workflow and appropriate service connections, with a separate resource and role review before any transfer. This is a design decision, not proof that moving the workflow would preserve every dependency or automatically reduce its service permissions.
The original service owner must approve any replacement connection and its exact CRM scope; the n8n owner must confirm what can be transferred and which other workflows depend on it. Jo retains ownership of current production operations while the dedicated-project and service-scope decisions remain pending. Tariq receives no implied right to publish, execute, delete, or administer resources merely because the maintenance assignment has been discussed.
Write a verification record without pretending a test occurred
A useful before/after record names an identity, resource, attempted action, expected result, and evidence status. For Amara's Personal-workflow case, the documentation review is complete, the non-credential transformation dependency is identified, and the production share is rejected. The expected protected-node restriction and run capability remain untested in an account. For Jo's project case, the resource inventory and proposed scope decision are complete; new project creation, transfers, membership, and execution checks remain pending.
If an authorized owner later conducts a controlled verification, use a suitable non-production design and approved synthetic data. Separate viewing the definition, viewing executions, editing an ordinary node, editing a credential-using node, and manual execution. Each is a distinct question with possible external effects. A successful view does not prove a run is blocked, and a disabled manual action does not settle every trigger or service access path.
Do not use a production run as a harmless credential test. Before any permitted execution, establish the target service account, allowed records, permitted operations, expected outputs, and stop conditions. Keep the owner responsible for approving the test and its external side effects. Keep expected and observed results in separate columns, recording each actual attempt and any unexpected access; leave untested observations blank.
Even a synthetic payload can reach a real destination if a live credential or URL remains connected. A copy's name containing “test” is not evidence of isolation. The owner must review the actual connections and dependencies before authorizing anything; this article provides no authorization to create or execute that copy.
Preserve evidence and define removal responsibilities
Execution visibility deserves its own review because authentication strings are only one kind of sensitive information. Input fields, output records, internal identifiers, and error messages may reveal business data. Decide which existing records the teammate would encounter and whether a sanitized task package is enough. Do not paste work payloads or credential details into a general support discussion.
Export also needs care. n8n's export guidance warns that workflow JSON includes credential names and IDs, and HTTP Request nodes imported from cURL may contain authentication headers. Review an export’s contents before treating it as safe to share. Have an authorized owner inspect and sanitize any intended share; no real export was produced here.
Record an end date, responsible owner, and review trigger. In Amara's case, the mapping review ends after Ren returns the two-example analysis; the production workflow remains unshared. In Jo's case, the maintenance proposal expires if the dedicated scope is not approved before Tariq's assignment starts. Jo retains responsibility for ordinary operations while the access decision is unresolved.
Removing one grant is not proof that every access path has ended. Check direct workflow access, project membership, explicit credential sharing, and applicable instance privileges. The service owner separately decides whether any connected-service permissions need review; don't rotate or revoke a shared connection casually when other workflows may depend on it.
Keep the completed inventory, rejected alternatives, expected capabilities, and pending account checks together. That record makes the next owner review concrete without exposing secrets or inventing a successful test. For related workplace decision guides, return to LandOffer after saving the task's actual access boundary and unresolved approvals.


