> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/basics/screen-navigation-visibility.md).

# Screen Navigation Visibility

### Screen Navigation Visibility

Screen Navigation Visibility lets you choose whether a screen appears in your app's navigation menu.

{% hint style="success" %}
**July 2026 update**\
Screens with **Show in navigation** turned off stay out of bottom, side, and top navigation, and they **still open** from buttons, links, form redirects, and other configured actions. See [Open Screens That Are Hidden From Navigation](https://docs.notionapps.com/guides/open-screens-that-are-hidden-from-navigation).
{% endhint %}

Use this setting when you want a screen to exist in the app, but you do not want users to see it as a normal navigation option. Hidden screens can still be opened from buttons, links, form actions, redirects, or other configured workflows.

{% hint style="info" %}
This feature controls whether a screen is shown in navigation. It does not control whether a user is allowed to access the screen. To restrict access, use your app's user access, personalization, role, or permission settings.
{% endhint %}

#### What This Feature Does

Each screen has a navigation visibility setting.

When a screen is visible in navigation:

* The screen appears in the app's navigation.
* Users can select the screen from bottom navigation, side navigation, or top navigation, depending on the app layout.
* The screen behaves like a normal primary screen.

When a screen is hidden from navigation:

* The screen does not appear as a navigation item.
* The screen can still be opened by configured actions.
* The screen can still be used as a destination for buttons, form submissions, links, redirects, or other app flows.
* The screen is not deleted.
* The screen's components, data, and configuration are preserved.

#### When to Use This Feature

Use Screen Navigation Visibility when you need a screen to support an app workflow but do not want it listed in the main navigation.

Common examples include:

* A confirmation screen after a form is submitted.
* A detail screen that should only open after selecting a record.
* A screen used by a button action.
* A screen used as part of a guided workflow.
* A screen that should be available only from a specific entry point.
* A screen that acts as a supporting step instead of a main destination.
* A private utility screen for app admins or specific flows.

#### Important Behavior

Hidden screens are still part of the app.

Hiding a screen from navigation does not:

* Delete the screen.
* Disable the screen.
* Remove buttons or actions that point to the screen.
* Prevent the screen from opening if a user reaches it through another configured path.
* Restrict access to the screen.
* Remove the screen from the builder.
* Remove the screen from publishing.

Hiding a screen only removes it from the end-user navigation display.

{% hint style="warning" %}
Do not use this setting as a security control. If a screen contains sensitive information, configure access rules or user permissions separately.
{% endhint %}

### Finding the Setting

The visibility control is available in the screen navigation configuration area of the builder.

#### Open the All Screens Panel

{% stepper %}
{% step %}

#### Open the All Screens Panel

Open your app in the builder.
{% endstep %}

{% step %}

#### Go to the screen/navigation configuration area

Go to the screen/navigation configuration area.
{% endstep %}

{% step %}

#### Open the All Screens panel

Open the **All Screens** panel.
{% endstep %}
{% endstepper %}

The panel lists the screens included in your app navigation configuration.

#### Locate the Screen Row

Find the screen you want to show or hide.

Each screen appears as a row in the navigation list. The row includes the screen name and a visibility control.

#### Use the In Nav Switch

Each screen row includes an **In nav** switch.

* Switch **on** means the screen is shown in navigation.
* Switch **off** means the screen is hidden from navigation.

<figure><img src="/files/5CK5ZFcP90PaqVrxlM3F" alt=""><figcaption></figcaption></figure>

#### Expand a Screen for More Details

You can also click a screen row to expand it.

Inside the expanded screen settings, you will see the full setting:

**Show in navigation**

This is the same visibility setting as the **In nav** switch on the screen row.

### Showing a Screen in Navigation

Use these steps when a screen is currently hidden and you want users to see it in navigation again.

{% stepper %}
{% step %}

#### Open the app in the builder

Open the app in the builder.
{% endstep %}

{% step %}

#### Open the All Screens panel

Open the **All Screens** panel.
{% endstep %}

{% step %}

#### Find the screen you want to show

Find the screen you want to show.
{% endstep %}

{% step %}

#### Turn the In nav switch on

Turn the **In nav** switch on.
{% endstep %}

{% step %}

#### Confirm the screen no longer shows the Hidden label

Confirm the screen no longer shows the **Hidden** label.

<figure><img src="/files/k1ksGbtqHRaXhvFNHbDh" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Preview the app

Preview the app.
{% endstep %}

{% step %}

#### Confirm the screen appears in the navigation

Confirm the screen appears in the navigation.
{% endstep %}

{% step %}

#### Publish the app

Publish the app when you are ready for users to see the change.
{% endstep %}
{% endstepper %}

#### Expected Result

The screen appears in the app's navigation.

Depending on your app's navigation style, it may appear in:

* Bottom navigation.
* Side navigation.
* Top navigation.
* A grouped side navigation section.

### Hiding a Screen From Navigation

Use these steps when you want a screen to remain available in the app, but not appear as a navigation item.

{% stepper %}
{% step %}

#### Open the app in the builder

Open the app in the builder.
{% endstep %}

{% step %}

#### Open the All Screens panel

Open the **All Screens** panel.
{% endstep %}

{% step %}

#### Find the screen you want to hide

Find the screen you want to hide.
{% endstep %}

{% step %}

#### Turn the In nav switch off

Turn the **In nav** switch off.
{% endstep %}

{% step %}

#### Confirm the screen shows the Hidden label

Confirm the screen shows the **Hidden** label.
{% endstep %}

{% step %}

#### Preview the app

Preview the app.
{% endstep %}

{% step %}

#### Confirm the screen no longer appears in navigation

Confirm the screen no longer appears in navigation.
{% endstep %}

{% step %}

#### Test the configured actions

Test any buttons, links, forms, or actions that should still open the hidden screen.
{% endstep %}

{% step %}

#### Publish the app

Publish the app when you are ready for users to see the change.
{% endstep %}
{% endstepper %}

#### Expected Result

The screen is removed from the visible navigation menu.

The screen remains available as a destination for configured actions.

### Hidden Badge

When a screen is hidden from navigation, the builder displays a **Hidden** badge on the screen row.

The badge helps you quickly identify which screens are excluded from navigation.

#### What the Hidden Badge Means

The **Hidden** badge means:

* The screen will not be shown as a navigation item.
* The screen still exists.
* The screen can still be edited.
* The screen can still be opened by configured app actions.
* The screen can still be published.

The badge does not mean the screen is disabled.

### Navigation Types

Screen Navigation Visibility works across the app's navigation styles.

#### Bottom Navigation

If a screen is hidden from navigation, it is removed from bottom navigation.

If only one visible screen remains in bottom navigation, the bottom tab bar may not appear because there is no meaningful tab choice for the user.

#### Side Navigation

If a screen is hidden from navigation, it is removed from side navigation.

If the screen belongs to a navigation group, the hidden screen is removed from that group in the end-user navigation display.

#### Top Navigation

If a screen is hidden from navigation, it is removed from top navigation.

If top navigation has an overflow menu, the hidden screen is removed from both the visible tab area and the overflow menu.

### Buttons, Links, and Actions

Hidden screens can still be opened by configured app behavior.

This allows you to build workflows where users only reach certain screens after taking a specific action.

#### Examples

A hidden screen can still open from:

* A button that navigates to another screen.
* A form submission action.
* A redirect after adding or updating a record.
* A link configured inside the app.
* A record detail workflow.
* A reference selection or related screen flow.

#### Example Workflow

You may want users to complete a form before seeing a confirmation screen.

{% stepper %}
{% step %}

#### Create a form screen

Create a form screen.
{% endstep %}

{% step %}

#### Create a confirmation screen

Create a confirmation screen.
{% endstep %}

{% step %}

#### Hide the confirmation screen from navigation

Hide the confirmation screen from navigation.
{% endstep %}

{% step %}

#### Configure the form submission action

Configure the form submission action to open the confirmation screen.
{% endstep %}

{% step %}

#### Preview the app

Preview the app.
{% endstep %}

{% step %}

#### Confirm the navigation behavior

Confirm users cannot select the confirmation screen from navigation.
{% endstep %}

{% step %}

#### Confirm the workflow

Confirm users reach the confirmation screen after submitting the form.
{% endstep %}
{% endstepper %}

### Start Screen Behavior

The first configured screen in the app can act as the app's starting screen.

If the starting screen is hidden from navigation, users may still land on it when they open the app.

In this case, the builder may show a warning to help you understand the behavior.

#### What This Means

If the start screen is hidden:

* It may still be the first screen users see.
* It will not appear as a navigation item.
* Users may need buttons, links, or redirects to move from that screen to other screens.

#### Recommended Practice

If you hide the starting screen, make sure the screen includes a clear path forward.

For example:

* Add a button to open the next screen.
* Configure a form action that redirects users.
* Make sure users are not stranded on a screen with no navigation options.

### All Screens Hidden Warning

If all configured navigation screens are hidden, the builder may show a warning.

This warning means users will not see normal navigation items.

#### What This Means

If all screens are hidden from navigation:

* Users may not see any navigation menu.
* Users must rely on buttons, links, redirects, or other workflows to move through the app.
* This can be intentional for guided apps, but it should be tested carefully.

#### Recommended Practice

Only hide all screens if your app has a guided flow.

Before publishing, confirm:

* The first screen opens correctly.
* Users can move forward.
* Users can complete the intended workflow.
* Users are not stranded.
* Any required back or restart path is available.

### Bottom Navigation Limit

Bottom navigation can only show a limited number of visible screens.

If bottom navigation already has the maximum number of visible screens, you may not be able to turn another bottom navigation screen back on until you make room.

#### How to Resolve the Limit

{% stepper %}
{% step %}

#### Hide another bottom navigation screen

Hide another bottom navigation screen.
{% endstep %}

{% step %}

#### Move a screen to side navigation

Move a screen from bottom navigation to side navigation.
{% endstep %}

{% step %}

#### Remove a screen from bottom navigation

Remove a screen from bottom navigation if it is no longer needed.
{% endstep %}

{% step %}

#### Try turning the desired screen back on

Try turning the desired screen back on.
{% endstep %}
{% endstepper %}

### Publishing

Screen navigation visibility changes must be published before end users see them in the live app.

#### Recommended Publishing Flow

{% stepper %}
{% step %}

#### Change the screen visibility setting

Change the screen visibility setting.
{% endstep %}

{% step %}

#### Preview the app

Preview the app.
{% endstep %}

{% step %}

#### Test navigation

Test navigation.
{% endstep %}

{% step %}

#### Test actions that open hidden screens

Test any actions that should open hidden screens.
{% endstep %}

{% step %}

#### Publish the app

Publish the app.
{% endstep %}

{% step %}

#### Open the live app

Open the live app.
{% endstep %}

{% step %}

#### Confirm the behavior

Confirm the live navigation matches the expected behavior.
{% endstep %}
{% endstepper %}

### Preview Testing Checklist

Before publishing, test the change in preview.

Use this checklist:

* The hidden screen no longer appears in navigation.
* The hidden screen still opens from the intended button, link, form action, or redirect.
* Visible screens still appear in navigation.
* The starting screen still makes sense.
* The user can move through the app without getting stuck.
* Mobile navigation behaves as expected.
* Desktop navigation behaves as expected.
* Side navigation groups behave as expected.
* Top navigation overflow menus behave as expected.

### Common Use Cases

#### Confirmation Screen

Use a hidden screen when users should see a confirmation screen only after completing a form.

Recommended configuration:

* Form screen: visible in navigation.
* Confirmation screen: hidden from navigation.
* Form action: opens confirmation screen after submission.

#### Details Screen

Use a hidden screen when users should only reach a details screen after selecting an item.

Recommended configuration:

* List screen: visible in navigation.
* Details screen: hidden from navigation.
* List item action: opens details screen.

#### Admin Utility Screen

Use a hidden screen when a screen supports a specific admin workflow but should not be a main navigation destination.

Recommended configuration:

* Main admin dashboard: visible in navigation.
* Utility screen: hidden from navigation.
* Admin button: opens utility screen.

{% hint style="warning" %}
If an admin utility screen contains sensitive information, hiding it from navigation is not enough. Configure access rules so only the correct users can access it.
{% endhint %}

### Frequently Asked Questions

<details>

<summary>Does hiding a screen delete it?</summary>

No. The screen remains in the app and can still be edited.

</details>

<details>

<summary>Does hiding a screen block users from accessing it?</summary>

No. Hiding a screen only removes it from navigation. Users may still reach it through configured actions.

</details>

<details>

<summary>Can I still link to a hidden screen?</summary>

Yes. Hidden screens can still be used as destinations for buttons, links, forms, and redirects.

</details>

<details>

<summary>Will hidden screens be published?</summary>

Yes. Hidden screens are still part of the app and can be included in the published version.

</details>

<details>

<summary>Will users see a hidden screen in bottom navigation?</summary>

No. Hidden screens are removed from bottom navigation.

</details>

<details>

<summary>Will users see a hidden screen in side navigation?</summary>

No. Hidden screens are removed from side navigation.

</details>

<details>

<summary>Will users see a hidden screen in top navigation?</summary>

No. Hidden screens are removed from top navigation and top navigation overflow menus.

</details>

<details>

<summary>Can all screens be hidden?</summary>

Yes, but use caution. Users will need buttons, links, redirects, or other configured workflows to move through the app.

</details>

<details>

<summary>Why can users still land on a hidden start screen?</summary>

The visibility setting controls navigation display, not whether a screen can be loaded. If the hidden screen is configured as the app's starting screen, users may still land on it.

</details>

<details>

<summary>Can I hide a screen for one role but show it for another?</summary>

Screen navigation behavior depends on how your app and roles are configured. If your app uses role-specific navigation, review the screen visibility setting in the relevant navigation configuration.

</details>

### Troubleshooting

#### I Do Not See the In Nav Switch

Confirm you are in the **All Screens** or navigation configuration area of the builder.

The switch appears on screen rows in that panel. If you are editing the screen content itself, you may not see the navigation visibility control.

#### The Screen Is Hidden, But Users Can Still Open It

This is expected.

The visibility setting only hides the screen from navigation. It does not block access from configured actions.

If users should not access the screen, review access control, personalization, or role settings.

#### The Screen Does Not Appear After I Turn It Back On

Check the following:

1. Confirm the **In nav** switch is on.
2. Check whether the screen is in bottom navigation, side navigation, or top navigation.
3. If using bottom navigation, confirm the visible screen limit has not been reached.
4. Preview the app again.
5. Publish the app if testing the live version.

#### The Bottom Navigation Bar Disappeared

If only one screen is visible in bottom navigation, the bottom navigation bar may not appear.

This is expected because there is no second visible tab for users to switch to.

#### I Hid All Screens and Users Cannot Navigate

If all screens are hidden, users need another way to move through the app.

Add or confirm at least one of the following:

* A button that opens another screen.
* A form action that redirects users.
* A link to another screen.
* A workflow that moves users forward.

#### The Live App Does Not Match the Builder

Confirm the app was published after the visibility change.

If the app was already open in another browser tab, refresh the live app.

### Best Practices

Use hidden screens intentionally.

Recommended practices:

* Keep main destination screens visible.
* Hide supporting workflow screens.
* Always test the path to a hidden screen.
* Avoid hiding all screens unless the app is intentionally guided.
* Do not use this setting as a security feature.
* Add clear buttons or redirects when users need to move from hidden start screens.
* Publish and test the live app after changing navigation visibility.

### Glossary

#### Visible in Navigation

A screen is visible in navigation when it appears as a selectable item in the app's navigation.

#### Hidden From Navigation

A screen is hidden from navigation when it does not appear as a selectable navigation item, but still exists in the app.

#### In Nav

The compact switch on each screen row. It controls whether the screen is shown in navigation.

#### Show in Navigation

The expanded screen setting for the same visibility control.

#### Hidden Badge

The label shown in the builder when a screen is hidden from navigation.