Restricting n8n Chat/Workflow Access to Specific Users or Groups (AD Integration?)

Questions
, , , , , , , ,
1

Title: Restricting n8n Chat/Workflow Access to Specific Users or Groups (AD Integration?)

Hey everyone,

I’m wondering if there’s a way to build a security concept in n8n so that workflows — especially chat-based workflows — are only accessible to certain users or groups.

For example:

  • Only a specific group of people should be able to use the chat

  • Certain users should only get access to information about specific topics

  • Ideally with some kind of authentication/authorization system

Would something like this be possible with Active Directory (AD) integration or similar user/group management?

I’d prefer a solution without external tools if possible, but I’m open to all suggestions and best practices.

Thanks in advance!

2

You may configure different levels of access by creating Projects to group your workflows and assigns specific roles to users in individual project.

Some best practices for user management can be found in the link.

n8n supports LDAP and SAML authentication

Hope this helps.

4

@Leon22 for the chat side specifically, don’t expose the built-in chat trigger publicly, put a Webhook node in front with header auth adn check the incoming token against your AD group membership via an HTTP Request to your AD/LDAP endpoint, then route with an If node, that way topic-level filtering lives in the workflow itself instead of relying on n8n’s role system which is project-scoped only.