# Multiuser Form for approval process **URL:** \ **Category:** Questions\ **Created:** [April 2, 2026, 2:06pm UTC](https://community.n8n.io/t/multiuser-form-for-approval-process/284024 "2026-04-02T14:06:47Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Anshul\_Namdev](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/anshul_namdev/32/178229_2.png) [@Anshul\_Namdev](https://community.n8n.io/u/Anshul_Namdev)\ **Post date:** [April 2, 2026, 2:40pm UTC](https://community.n8n.io/t/multiuser-form-for-approval-process/284024/4 "2026-04-02T14:40:57Z")
@TheLuBu i think we might be hitting some limitation on n8n architecture, read this: > [@Integrate SSO credentials with node credentials](http://community.n8n.io/t/integrate-sso-credentials-with-node-credentials/257935/2): > > Short answer: **no, this isn’t supported in n8n right now**. > > SSO (SAML) in **n8n** is only used to authenticate users into the UI. The SSO token or session is **not exposed to workflows or custom nodes** , and it can’t be reused for node authentication. > > Because of that, nodes must always use **their own credentials** (API keys, OAuth, etc.) configured in n8n. This separation is intentional for security and execution consistency. > > If you need user context, the usual workaround is to **pass the user identity explicitly** (like email or userId) to the workflow and let the external service handle authorization. And to truly trustworthy identity i think you need to setup a redirect to external auth endpoint like azure, and to basically control that. (you can just add a basic auth in your form so that only limited people know the password, also if any user would be able to create an auth for another user that still would require a password or some amount of information that is somewhat safe, but you are correct on that one!) --- _[View the full topic](https://community.n8n.io/t/multiuser-form-for-approval-process/284024)._