# Multiple Projects - Seeking seamless navigation and no reauthentication

**URL:** <https://forum.inductiveautomation.com/t/multiple-projects-seeking-seamless-navigation-and-no-reauthentication/115815>\
**Category:** Ignition\
**Created:** [June 2, 2026, 11:08pm UTC](https://forum.inductiveautomation.com/t/multiple-projects-seeking-seamless-navigation-and-no-reauthentication/115815 "2026-06-02T23:08:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MC2338](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@MC2338](https://forum.inductiveautomation.com/u/MC2338)\
**Post date:** [June 2, 2026, 11:08pm UTC](https://forum.inductiveautomation.com/t/multiple-projects-seeking-seamless-navigation-and-no-reauthentication/115815/1 "2026-06-02T23:08:51Z")

</div>

I have multiple projects on a gateway in a pharmaceutical environment and each project has its own validation requirements.

I am looking for recommendations on the best practice to provide seamless navigation between projects that does not require reauthentication, but authentication is required (for certain functions in certain projects).

I had considered creating a dedicated navigation project that would use embedded views to display the views from the other projects but that got a bit messy with authentication. Another idea was to maybe use Parent projects/inheritance somehow.

Please help!! Any suggestions appreciated!