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 will 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.