Collaborators on a shared workflow
When you share a workflow for editing, your collaborators can run it without connecting their own accounts. Nodes that use your credentials resolve them as you, the workflow owner, at run time. What collaborators see and get:- The node shows the credential’s name with an owner note: “Owned by [you]. It’s shared with this flow.”
- The secret itself is never shown, copied, or added to their account; values are only decrypted server-side when the node executes.
- Edit, share, and delete controls are hidden for them, and the backend rejects those actions from anyone but the owner.
This works one workflow at a time. Sharing a workflow never grants access to your credentials in the collaborator’s other workflows.
Sharing a credential directly
You can also share a credential itself, so someone can use it in their own workflows:- Open Settings → Credentials and click the share icon on a credential you own (or use the share icon next to it in any node’s credential picker).
- Add people by email, or share with an organization to cover all its members. Each recipient gets Can view or Can edit permission.
- Recipients see it under Shared With Me in their own Settings → Credentials and can select it on nodes like any other credential.
Organization credentials
Inside an organization, the Organization tab in Settings → Credentials collects credentials owned by or shared with the org. These are available to all members, and they count against the organization’s plan limit rather than anyone’s personal cap. Runs of organization workflows bill the org owner’s credit pool regardless of who runs them; see Organizations.Next steps
Workflow sharing
Invite links, view/edit access, and public links.
How credentials are protected
Encryption at rest and what other users can see.