> 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/how-to-guides/open-screens-that-are-hidden-from-navigation.md).

# Open Screens That Are Hidden From Navigation

Turn **Show in navigation** off to keep a screen out of bottom, side, or top nav — and still open it from buttons, links, form actions, and redirects.

{% hint style="info" %}
**Important**\
Hiding a screen from navigation is a **display** setting. It is not access control. Users who can reach the screen through a configured action can still open it. Use roles, personalization, or permissions when a screen must be restricted.
{% endhint %}

***

### What this guide covers

| Goal                          | Result                                         |
| ----------------------------- | ---------------------------------------------- |
| Hide a screen from nav chrome | No tab / drawer / top-nav item                 |
| Keep button / form navigation | The screen still opens from configured actions |
| Avoid stranding users         | Clear path in and out of the hidden screen     |

![Show in navigation turned off with Hidden badge](https://iili.io/Cw1BCox.png)

***

### Step 1 — Hide the screen from navigation

1. Open the app in the builder.
2. Open **Edit Navigation** / **All Screens**.
3. Find the screen row (for example, a confirmation or support details screen).
4. Turn **In nav** / **Show in navigation** **off**.
5. Confirm the **Hidden** badge appears on the row.

***

### Step 2 — Keep a way to open it

Configure at least one entry path:

* A **Button** with **Go to screen** pointing at the hidden screen
* A form **submit redirect** to the hidden screen
* A list/details action that opens the hidden screen
* An in-app link

![Button action still opens a screen that is hidden from navigation](https://iili.io/Cw1BoPV.png)

***

### Step 3 — Preview and publish

1. Preview mobile and desktop.
2. Confirm the screen is **absent** from navigation.
3. Confirm the button / form action **still opens** the screen.
4. **Publish** and re-test on the live app (hard-refresh if a tab was already open).

{% hint style="success" %}
**July 2026 fix**\
A regression briefly blocked route registration for hidden screens, so buttons appeared to do nothing. That is fixed: hidden screens stay out of nav chrome and remain routable from actions.
{% endhint %}

***

### Recommended patterns

| Pattern             | Visible in nav  | Hidden screen |
| ------------------- | --------------- | ------------- |
| Form → confirmation | Create Form     | Confirmation  |
| List → details      | List            | Details       |
| Dashboard → utility | Home / List     | Admin utility |
| Guided onboarding   | First step only | Later steps   |

***

### Checklist

* [ ] Show in navigation is off for supporting screens only
* [ ] At least one button, link, or redirect opens each hidden screen
* [ ] Users are not stranded (Back, Home, or next-step action exists)
* [ ] Preview and published app both tested
* [ ] Sensitive screens also have real access rules

***

### Troubleshooting

| Symptom                           | Likely cause                                | What to do                                                 |
| --------------------------------- | ------------------------------------------- | ---------------------------------------------------------- |
| Button does nothing               | Stale published client / unpublished change | Publish, hard-refresh; confirm the action target screen id |
| Screen still in nav               | Wrong navigation list / role nav            | Check All Screens for the active navigation configuration  |
| Users can open a sensitive screen | Expected for hide-from-nav                  | Add access control / personalization                       |
| Start screen hidden               | Allowed but easy to strand users            | Add a clear primary button on that screen                  |

***

### Related reading

* [Screen Navigation Visibility](https://docs.notionapps.com/workspace-and-account/screen-navigation-visibility) — full reference
* [20 Jul 2026 Release](https://docs.notionapps.com/release-notes/20-jul-2026-release)
* [Button Component](https://docs.notionapps.com/screens-and-components/type-of-components/button-component)

## Annotated builder screenshots

![Annotated builder screenshot: Guest navigation visibility](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2Ffap9nwuPV53Iywx8XRnH%2Fp23-1786203265-8-21-section-show-in-navigation-for-guests.jpg?alt=media)

![Annotated builder screenshot: Signed-in navigation visibility](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FnUW6JoYc87pDE56o558l%2Fp23-1786203265-9-22-section-show-in-navigation-when-signed-in.jpg?alt=media)

## Complete Builder Options Reference

### Screen accordion / Edit Navigation

#### Show in navigation / In nav

**What it does:** Controls whether the screen appears in the hamburger or bottom tray.\
**How to use it:** Turn off for utility screens opened only from buttons, Actions, or deep links.\
**Why / recommended default:** Hide update forms and intermediate details when a list already opens them.

#### Show in navigation for guests / when signed in

**What it does:** Splits guest vs signed-in visibility on public screens.\
**How to use it:** Hide guest-only welcome pages from signed-in nav.\
**Why / recommended default:** Pair with [Per-Screen Public Access](https://docs.notionapps.com/guides/per-screen-public-access).