If you add a screen to your app, it is always shown. However, there are cases where you’d like to hide the screen and only show it in case a button is clicked or after a form has been submitted.
To solve this, we will add a toggle that will show/hide a screen from the side and bottom navigation.
Thanks @jatin_notionapps for adding this.
1 Like
What’s your use case for this feature, @Alvin?
A lot… particularly in Forms/Registration and other relevant use-cases.
Currently I continuously updating the system including NotionApps of the organization. The calendar feature is one of the awesome updates. 
For now, this are the features what I needed and that will be helpful in most use-case scenario of other users.
- URL pass through - mostly useful in forms and other relevant use-case - not in our roadmap
- Login thru user and pass - currently only supported GMail and a the log-in via access code. - already in our Roadmap.
- New Button Action - Change data or EDIT as a button component - already in our Roadmap.
Edit button should be incorporated in the Button Component, not just in the upper right small pencil.
- New Button Action - Go to next - already in our Roadmap
- New Component - Comments - already in our Roadmap
- Custom CSS/JS in the app builder - already in our Roadmap
I’ll add to request features when I have others in mind as I forgot the others too. 
I’d love to be able to hide the screen from the Navigation depending on which user is logged in… Is that was this particularly feature request is about?
2 Likes
Any update on this pleaseeee… ? 
@jatin_notionapps Any update on this features yet?
Linzie (NotionApps)
Mar 2026
Hi everyone — Linzie here. I recently took over ownership of NotionApps from Jatin and Sameer, and I’m currently spending time reviewing the roadmap, community feedback, and feature requests like this one.
First, thank you for raising this use case — it’s a really good one. The ability to conditionally show or hide screens (for example after a button click, form submission, or based on state) would unlock a lot of workflow patterns such as:
- Multi-step onboarding flows
- Conditional navigation
- Post-submission confirmation pages
- Role-based or state-based UI visibility
The approach Jatin mentioned — a toggle to control whether a screen appears in side/bottom navigation — is a solid starting point. I’m currently reviewing how this would fit into the broader navigation and conditional logic model inside NotionApps.
My immediate focus is stability and continuity, but feature requests like this are being cataloged and prioritized as I get deeper into the system.
In the meantime, if anyone in the community has examples of how they would use this feature (screenshots, workflow examples, etc.), feel free to share them here — that context is extremely helpful when evaluating how to implement it.
Appreciate the feedback and keep it coming.
— Linzie
1 Like
Have you found a work around for your use case? Looking at similar. Thx
Greetings, we are not at the point where we can introduce this feature. We are currently prioritizing items that aid in the stability of the system. However, once the roadmap is introduced you’ll be able to see it’s ranking in the list.
1 Like
Was looking for a workaround on this one too.
Yet, this is in the roadmap but still no timeline for production.
Greetings, we have been working on items that address system stabilization. This feature will be addressed within the next month. The dev them has finally ramped up. Thank you for both your patience and for being a part of the NotionApps family.
Alvin, can you better explain your use case?
Greetings, now that we’ve added rollback after a destructive event on the notion side, custom font/css/js, side menu grouping, i’d like to gauge interest in introducing this feature. As I flesh out the requirement i’d love to hear from the community regarding how they’d like to see this functionality realized. Therefore, please feel free to send us an email at founders@notionapps.com or reply here. Once i have a fully fleshed out requirement i’ll summarize it here. Thanks for helping to make NotionApps better.
Screen Navigation Visibility Controls
Feature: Show or Hide Screens in App Navigation
Status: Proposed / Planned
Audience: NotionApps builders
Rollout Date: 28 Jun 26
We’re planning to add a new screen-level setting called Show in navigation that will let builders decide whether a screen appears in the app’s navigation.
Today, when a builder adds a screen, that screen appears in the app’s navigation by default. This works well for main pages, but it can create clutter when builders need screens that are part of a workflow but should not appear as normal navigation destinations.
With this feature, builders will be able to hide screens from navigation while still keeping those screens active and usable inside the app.
How It Would Work
Each screen will have a Show in navigation setting.
When Show in navigation is turned on, the screen appears in navigation like it does today.
When Show in navigation is turned off, the screen will be hidden from navigation areas such as:
- Side navigation
- Bottom navigation
- Mobile or drawer navigation
- Navigation groups
The screen will still exist in the app and can still be opened through:
- Buttons
- Links
- Form submissions
- Redirects
- Direct app routes
Example Use Cases
This is especially useful for:
- Registration forms
- Thank-you pages
- Confirmation screens
- Onboarding steps
- Internal utility pages
- Detail screens
- Screens that should only appear after a button click or form submission
For example, a builder could create an Event screen with a Register button. The button could open a hidden Registration Form screen. After the form is submitted, the user could be redirected to a hidden Thank You screen. The registration and thank-you screens would work normally, but they would not clutter the main navigation.
Who Would Have Access
This feature should be available to builders who can create and edit app screens.
There is no plan-gating requirement in the current MVP proposal, so the expected behavior is that this would be a general builder capability unless product later decides to restrict it by subscription tier.
Important Note
Hiding a screen from navigation is not the same as restricting access.
A hidden screen will not appear in the app navigation, but it may still be reachable through a direct link, button, form action, or redirect. If a screen contains sensitive information, builders should not rely on this feature as a security or permission control.
Future Enhancement
A future phase may allow builders to show or hide screens in navigation based on the logged-in user, user role, group, or user attributes. That would be a larger feature because it introduces conditional navigation and possible access-control expectations.
Why This Matters
This feature gives builders more control over app structure and helps keep navigation clean. It supports common workflows like forms, registration, onboarding, and confirmation pages without forcing every screen to appear as a main navigation item.