n8n
n8n Access Control in 2026: Projects, Roles and Limits
n8n access control explained: instance roles versus project roles, where projects stop isolating data, and the credential leak most teams miss.
5 Nov 2026 · 9 min read · Abhijeet Singh

On this page 6 sections
Most teams set up n8n access control the day someone new needs to log in. A founder adds a developer, the developer needs a credential, the credential gets shared, and six months later nobody can say who can see the Stripe key. The settings that fix this are not hidden, but they sit at two different levels and they do not do what their names suggest.
The core thing to understand is that n8n has two separate role systems, and projects are an organisation tool rather than a security boundary. Get that distinction right and the rest of the configuration is straightforward. Get it wrong and you will build a permission model that quietly does not hold.
n8n access control works at two levels
The first level is instance roles, which govern what a user can do across the whole n8n instance. As of November 2026, n8n documents four built-in instance roles: Owner, Admin, Member and Chat user. Each user has exactly one.
Owner holds every permission, including access to the Cloud dashboard. Admin holds the same permissions as Owner with the Cloud dashboard excluded, and per n8n's documentation the Admin instance role is available only on n8n Cloud Pro and Enterprise, and on self-hosted Enterprise. If you have not settled Cloud versus your own server yet, our self-hosting n8n decision guide explains how that choice affects the editions you can buy. Member is deliberately narrow: manage their own email and password, manage their own workflows, and view, create and use tags.
What a Member cannot do is the more useful list. Members cannot delete tags, cannot view or share all workflows, cannot view, edit or share all credentials, cannot set up source control, cannot create projects, cannot view all projects, and cannot add or remove users. If you want someone to build automations without seeing the whole instance, Member is the correct starting point.
Chat user is the narrowest role. It is for people who only need n8n's Chat feature: they can send messages, manage their own Chat agents and run shared workflows and agents, but they cannot create or edit workflows or credentials. It needs the Chat feature and has the same plan availability as Admin. n8n 3.0 turns Chat Hub off by default, so review this role when you upgrade.
The second level is project roles, which govern what a user can do inside one project. These are Project Admin, Project Editor and Project Viewer. A user can hold different project roles in different projects, which is how one person ends up as an editor on the sales automations and a viewer on the finance ones.
Two edition gates matter here. According to n8n's role documentation, the Project Editor role requires n8n Cloud Pro or self-hosted Enterprise, and the Project Viewer role requires Cloud Enterprise or self-hosted Enterprise. There is also a detail that surprises people: viewers are not able to manually execute any workflows that exist in a project. Read-only in n8n means read-only, not read-and-run.
Projects organise work, they do not isolate it
A project groups workflows and credentials, and only instance owners and admins can create one. Project admins then manage members from project settings. That structure looks like tenant isolation, and this is where teams overreach.
n8n's release notes for version 2.42, released on 29 September 2026, make the limit explicit. Project member lists now always show instance owners and admins with a full access role, and that role cannot be removed or edited. The related API endpoints reject edits and removals of instance admins and ignore them in add requests. In other words, the platform has stopped letting you pretend an instance admin is not in the room.
That change is a clarification rather than a restriction, and it is the single most decision-relevant fact in n8n access control. Anyone with an instance-level Owner or Admin role sees every project, every workflow and every credential, by design. Projects separate work between colleagues. They do not separate work between parties who must not see each other's data.
Two more boundary leaks are worth knowing. Variables and tags are not governed by RBAC at all, because they are global across the instance. And moving a workflow or credential between projects removes all existing sharing on it, which can break other workflows that depended on that sharing, and the moved workflow can stop running if the credentials it needs are not available in the target project. n8n makes you acknowledge both of those in a confirmation dialog, which is a good sign that both happen regularly.
Deleting a project forces a decision too. You either transfer its workflows and credentials to another project or delete them along with the project. There is no quiet middle option, so decide before you click.
Credentials are where access actually leaks
Role configuration gets the attention, but in practice credentials are the thing that escapes. The rules are specific and worth reading twice.
Users can share credentials they created and own, and only project admins can share credentials that belong to a project. People who use a shared credential cannot view or edit its details, which is the behaviour you want. Instance owners and instance admins can view and share every credential on the instance, which follows from the instance-role model above.
The important one is on the workflow side. n8n's sharing documentation states that workflow sharing allows editors to use all credentials used in that workflow, including credentials that are not explicitly shared with them. Least privilege applies only to editing: if the owner has not shared their credentials, an editor cannot edit the nodes that use them, but they can view and run the workflow and edit the nodes that do not. So sharing a workflow effectively lends out every credential inside it at run time. Before you share a workflow, look at which credentials it carries.
There are also two workflow roles, creator and editor, and editors cannot share or delete a workflow. Only the creator can.
For external secrets, n8n gates access behind a setting: project admins and editors can use external secrets in credentials when an instance owner or admin enables external secrets for project roles, available from n8n 2.13.0, and managing project secret vaults stays with project admins. n8n's v3.0 breaking-changes documentation says that release removes the setting and gives project editors and admins external-secrets access in their projects by default on Enterprise, with a recommendation to create custom project roles before upgrading. n8n 3.0 entered beta on 27 October 2026, with a stable release planned for early December 2026, so treat that as a change to plan for rather than one already live on a production instance. Our n8n 3.0 breaking changes guide covers the rest of that release.
What your plan actually gives you
Capability here is tied to commercial tier more tightly than in most parts of n8n, so check before you design.
On n8n's pricing page, shared projects are counted per plan: one on Cloud Starter, three on Cloud Pro, six on Business, and unlimited on Enterprise. All plans include unlimited users and workflows, so the constraint is projects, not seats. Admin roles appear at Pro, custom roles at Enterprise, and SSO with LDAP at Business. Enterprise adds audit logging, log streaming and external secret store integration, which is the tier where governance becomes auditable rather than merely configured.
Two practical notes. The Cloud trial does not include Admin Roles, the project Editor role or Workflow Diffs, so a trial will not show you the model you are buying. And the self-hosted gates differ by feature: n8n's projects documentation lists RBAC as available on self-hosted Registered Community, Business and Enterprise, while the credential and workflow sharing pages list self-hosted Business and Enterprise. Verify the specific feature in your own instance rather than assuming one gate covers all of them.
Custom instance roles are the escape hatch when the built-in three do not fit. They grant granular permissions such as managing users, tags or API keys without handing over full Admin. One maintenance detail from the 2.41 release notes, dated 22 September 2026: custom instance roles now include a tags view permission by default, but existing custom roles do not receive the new scope automatically. If you built custom roles before 2.41, check them.
When to run separate instances instead
The honest answer to strict isolation is more instances, not more projects. If two groups must not see each other's credentials or execution data, and neither group's administrator should hold your instance keys, separate instances are the only structure that enforces it.
Use projects when the parties involved are colleagues who merely should not clutter or accidentally edit each other's work, when you want per-department role assignment, and when a single administration team legitimately oversees everything. Use separate instances when a contractual or regulatory boundary exists, when a client or an external partner needs their own administrator, or when execution data itself is sensitive. The cost is real, because you duplicate upgrades, monitoring and credential rotation, which is exactly why this should be a deliberate decision rather than a default.
A setup sequence that holds up
Run these in order, because each step depends on the previous one.
First, count your real boundaries. Write down the groups of people and ask which pairs must not see each other's data. That list tells you how many instances you need before it tells you how many projects.
Second, demote the owner account. n8n recommends that owners create a second account with the Member role for day-to-day building, and the reason is sharp: workflows do not record who created them, so an owner editing in the wrong place can overwrite someone else's work with no audit trail pointing back.
Third, create one project per functional area and assign project roles rather than sharing individual workflows. Individual sharing is what becomes unmanageable at scale.
Fourth, inventory credentials per project and move the shared ones deliberately, remembering that a move wipes existing sharing. Do this before you invite anyone.
Fifth, audit workflow sharing specifically for borrowed credentials, since that is the path that bypasses your careful credential work.
Sixth, if you are on a tier with audit logging and log streaming, turn them on. A permission model you cannot review is a permission model you are only hoping is correct.
At AbhijeetBuilts we treat this as part of every n8n build and integration project rather than a cleanup afterwards, because retrofitting access control onto a live n8n instance means moving credentials and breaking sharing on workflows that are already running. For client engagements we map the isolation boundaries first, decide instance count before project count, keep the owner account out of daily use, and document which credentials sit in which project so the next person inherits a model instead of a mystery.
If you are running automations on a shared n8n instance and cannot currently say who can see which credentials, that is worth an hour of structured review. Get in touch through the website and we can look at your current setup and the access model it should have.
Related resources
Keep building the automation map
Move from the guide into the services and proof pages connected to this topic.
Related services
Service
Explore n8n Workflow Development
Custom n8n workflow automation for lead capture, CRM sync, AI enrichment, approvals, and notifications — built to keep running when nobody is watching.
Service
Explore AI Agent Development
AI agents for sales replies, lead memory, storyboard generation, data extraction, and structured automation outputs.
Service
Explore AI Operating System
A done-for-you AI operating system built on Claude: a second brain that knows your business, remembers everything between sessions, and safely runs your recurring work.
Further reading
Article
Read: Self-Hosting n8n in 2026: A Founder's Decision Guide
Self-hosting n8n in 2026 can cut costs and keep data in-house, but only when it fits your team. A practical framework for self-host versus cloud.
Article
Read: n8n Handover Checklist: What Clients Should Get in 2026
Use this n8n handover checklist to get the docs, backups, credentials, error alerts and update plan you need before signing off an automation build.
Article
Read: Google Workspace Studio vs n8n in 2026: What to Build Where
Google Workspace Studio vs n8n in 2026: what each tool actually owns, the limits that decide it, and a clear rule for which automations belong where.
Proof pages
Case study
See case study: Complete Zoho Stack for a B2B Packaging Manufacturer
One Zoho operating system for a B2B packaging manufacturer — sales, service, inventory, accounting, ticketing, and analytics — replacing the legacy Excel and Salesforce files the business used to run on.
Case study
See case study: Zapier to n8n Migration for a US Manufacturer: $70 a Month Down to $10
About 20 lead and attribution workflows moved from Zapier to self-hosted n8n, taking the automation bill from about $70 a month to a $10 server the client owns.