Excluding Custom App Shell from Login Page in UI Builder

[bishalsharm]

Hello Community Members,

I have created a custom App Shell that is currently being used across my experience. The experience contains multiple pages, including a custom Login page.

For the Login page only, I want to exclude the App Shell from loading.

Is this possible in UI Builder, and what are the recommended or best approaches to achieve this?

Looking forward to your suggestions.

Thanks

Bishal

[Matthew_13]

Hi Bishal,

In UI Builder, the App Shell is applied at the experience level, not at the page level, so you can’t directly exclude it for just one page.

The recommended approach is to create a separate experience for your Login page that doesn’t use the custom App Shell. Then keep your main experience with the App Shell for all authenticated pages. After a successful login, simply redirect users to the main experience URL. This is also how most OOTB ServiceNow experiences handle login and keeps things clean and easy to maintain.

If creating a separate experience isn’t an option, a workaround is to conditionally hide the shell components header, nav, etc... based on the current route or page ID. This works but the App Shell still loads in the background so it’s generally not recommended for login pages.

Hope that helps!

@bishalsharm - Please mark as Accepted Solution and Thumbs Up if you find Helpful!!