> 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/reuse-a-screen-in-navigation.md).

# Reuse a Screen in Navigation

Put the **same** list or form in the tab bar / drawer more than once — then detach that extra tab when it needs its own filters or name.

This is for app makers editing navigation in the builder.

{% hint style="info" %}
Reuse is not Duplicate **Reuse screen** adds another navigation entry that still points at the same screen. **Duplicate Screen** makes a full independent copy immediately. **Detach** turns one reused tab into its own copy later.
{% endhint %}

If you only remember one sentence:

> Use **Reuse screen** when two tabs should stay in sync. Use **Detach** when that extra tab must diverge. Use **Duplicate Screen** when you want a separate copy from the start.

***

### When to reuse vs duplicate vs detach

| Goal                                                                  | Use                        | What happens                                               |
| --------------------------------------------------------------------- | -------------------------- | ---------------------------------------------------------- |
| Same list in two places (for example Home and a group)                | **Reuse screen**           | One screen, two nav entries. Edits apply to both.          |
| Same layout, but this tab needs different filters or a different name | **Reuse**, then **Detach** | The extra tab becomes its own screen.                      |
| Start from an existing screen and never keep them linked              | **Duplicate Screen**       | Immediate full copy (including secondary Details / forms). |

***

### Step 1 — Reuse a screen

1. Open the screen in the builder (the one that already lives in navigation).
2. In the screen title bar, click **Reuse screen**.
3. NotionApps adds a second nav entry. The new tab gets a copy of the icon and a slightly different tab name so you can tell them apart.
4. Open **Edit Navigation** and drag the extra tab where it belongs (another group, another role menu, or next to the original).

A banner on a reused screen says it is **Also in navigation as** the other tab names, with **Detach to edit this copy only.**

***

### Step 2 — Edit while it is reused

Anything you change on the screen — Filtering, fields, appearance — applies to **every** nav entry that points at it.

That is the point: one Assets list reused under **Field** and **Admin** stays one list.

***

### Step 3 — Detach when this tab must be different

1. Select the **extra** nav tab (the alias you want to split off).
2. Click **Detach** in the screen title bar. Detach only appears when the screen is in navigation more than once.
3. NotionApps clones that screen (and its secondary Details / forms) and points **this** nav entry at the clone.
4. The original tab keeps the original screen.

Now you can change filters on the detached copy without changing the original. Example:

* Tab A: Assets, filter **Status** equals Open
* Tab B (detached): Assets, filter **Status** equals Closed

{% hint style="warning" %}
Detach clones the screen After Detach you have two screens to maintain. If you only needed a second label in the menu, stay on Reuse.
{% endhint %}

***

### Removing a reused tab

If a screen is in navigation more than once, deleting from the extra tab **removes that nav entry only**. The screen itself stays. Deleting the last remaining entry deletes the screen (and its secondaries) as usual.

***

### Related

* [App Navigation](https://docs.notionapps.com/screens-and-components/app-navigation)
* [Open Screens That Are Hidden From Navigation](https://docs.notionapps.com/how-to-guides/open-screens-that-are-hidden-from-navigation)
* [Filter lists with groups and dynamic values](https://docs.notionapps.com/how-to-guides/filter-lists-with-groups-and-dynamic-values)
* [15 Sep 2026 Release](https://docs.notionapps.com/release-notes/15-sep-2026-release)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/how-to-guides/reuse-a-screen-in-navigation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.