# 2 User source connections, 1 project **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 22, 2023, 6:51pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458 "2023-03-22T18:51:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![craigb](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@craigb](https://forum.inductiveautomation.com/u/craigb)\ **Post date:** [March 22, 2023, 6:51pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458/1 "2023-03-22T18:51:17Z")
Our company is split into 2 regions. Each region has its own internal Microsoft AD. Up until now, only one region has accessed the project (dashboards etc) so it was their AD/internal user source that was in the project connections, now we want to allow the other region to access the project. Since their AD is a sperate connection it will be an additional user source in the gateway but I cant add two user source connections in the project. I can however, specify a soft fail over to the other AD/user source which will work but that seems like a plan B method. Is there an option A ? ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [March 22, 2023, 6:59pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458/2 "2023-03-22T18:59:37Z")
A soft failover is how I do it. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 22, 2023, 7:44pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458/3 "2023-03-22T19:44:42Z")
Not sure what option you'd prefer over a soft failover here, to be honest. A module could introduce a "user source splitter" or something...but it would have exactly the same functionality as a soft failover (with the minor benefit of perhaps being a little easier to configure). ---
**Author:** ![craigb](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@craigb](https://forum.inductiveautomation.com/u/craigb)\ **Post date:** [March 22, 2023, 8:02pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458/4 "2023-03-22T20:02:08Z")
I didn't know if there was something I was missing in the settings to combine user sources. We already use the fail over option to a DB user source for adding temp users that are not part of our AD. Can the fail over user source then fail over again ? AD - AD - DB ---
**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\ **Post date:** [March 22, 2023, 8:09pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458/5 "2023-03-22T20:09:05Z")
Yes, if the failover source has its own failover source configured, it will keep going. There might be a limit set up, I've never tried to see how deep it can go. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 22, 2023, 8:18pm UTC](https://forum.inductiveautomation.com/t/2-user-source-connections-1-project/71458/6 "2023-03-22T20:18:22Z")
There can be an indefinitely long chain, but cycles are prevented.