The idea is:
Add node-level edit permissions in n8n workflows, so specific nodes can be locked or made read-only, with edit access granted only to selected users or roles. Ideally this would also include a clear visual lock indicator on restricted nodes.
My use case:
At my company, we use n8n extensively for complex, multi-step AI-powered customer support workflows. These workflows are often shared across multiple users, but some nodes contain highly sensitive or business-critical logic, such as AI agent configuration, prompts, routing logic, and key integrations. We want team members to be able to work on operational parts of a workflow without risking accidental edits to those protected nodes.
I think it would be beneficial to add this because:
Current project-level permissions are too broad for this use case. Viewer access is too restrictive, while editor access allows changes to everything in a workflow. Node-level permissions would make collaboration much safer for teams managing shared production workflows, especially when some parts of the workflow must remain protected. This would help prevent unintended changes, improve governance, and reduce the need to split workflows apart just to protect a few critical nodes.