Feature Request: Allow multiple Admins on self-hosted (Community) n8n
The idea
Enable multiple Admin-level users on self-hosted (Community) n8n instances.
My use case
On self-hosted deployments, only the single Owner can perform certain admin actions.
In real teams (agencies, MSPs, internal platforms), we need at least two people with full administrative capability for continuity (leave, illness, after-hours incidents) without sharing the Owner’s credentials.
Why this would be beneficial
- Operational continuity: Avoid single-person bottlenecks for urgent admin tasks (user resets, environment changes, global fixes).
- Security & accountability: Stop sharing the Owner login; use named admin accounts with distinct credentials.
- On/Off-boarding: Cleanly promote/demote admins without transferring the Owner account.
- Fewer brittle workarounds: Running extra instances or blanket-elevating Members doesn’t cover true admin duties.
I realise this restriction exists in part to encourage teams towards Pro/Enterprise plans. But the reality is that the vast majority of self-hosted users will never migrate to those tiers, regardless of this feature. Enabling multiple Admins in Community wouldn’t undercut Enterprise value — it would simply make the self-hosted experience far more usable and sustainable for small teams. Pro/Enterprise already have plenty of clear differentiators (SSO/LDAP, RBAC, audit logs, support, projects, etc.), so this small lift in Community would be a huge win without cannibalising paid features.
Alternatives I’ve tried / considered
- Sharing the Owner account (bad practice).
- Making a Member do “admin-like” work (still blocked by Owner-only tasks).
- Running multiple instances (ops overhead; not the same as instance-level admin).
Proposed approach (any of these would help)
- Allow more than one Owner; or
- Introduce a Community “Admin” role with the same instance-level powers as Owner except licensing/billing; or
- Add instance-level toggles (Manage users, Reset MFA, View/CRUD all workflows/credentials) that can be granted to specific users on Community.
Acceptance criteria (example)
- Owner can assign/revoke Admin to multiple users.
- Admins can perform all instance-level actions Owner currently can (except license/billing, if you want to keep that Owner-only).
- No requirement to share Owner credentials.
- Backwards-compatible with existing env/DB; clear migration note.
Any resources to support this?
- n8n user management exists for self-hosted; Admin role and full RBAC are positioned for Pro/Enterprise.
- There are multiple community threads asking for multi-admin on self-hosted.
Are you willing to work on this?
No. Happy to test and provide feedback if there’s an early build/flag.