> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/shared-features/breadcrumb-navigation.md).

# Breadcrumb Navigation

Breadcrumb navigation appears at the top of CIPP, just beneath the top menu bar, and shows how you reached the page you are on. The bar has three parts: a mode toggle at the far left, the trail itself, and a bookmark button immediately after the last entry in the trail.

## Display Modes

The icon at the far left of the breadcrumb bar switches between the two display modes. Hovering over it tells you which mode you will switch to. Your choice is saved to your preferences and applies the next time you sign in.

### Hierarchy Mode

Hierarchy mode shows where the current page sits in the menu structure, exactly as if you had drilled down through the left-hand navigation to reach it. On pages with tabs, the tab you are viewing is included as the final entry.

Each entry is clickable and takes you to that level. Grouping headers that have no page of their own are shown as plain text rather than links.

### History Mode

History mode shows the pages you actually visited on the way to the current one, in the order you visited them. Clicking an earlier entry returns you to that page and discards everything you visited after it, so the trail always reflects a single path rather than a growing list.

CIPP keeps the last twenty pages and displays the five most recent. The history is held for the current session only, so refreshing the browser or signing in again starts it over.

{% hint style="info" %}
Both modes ignore the tenant selection when building the trail, so switching tenants does not add duplicate entries or leave the tenant name embedded in a breadcrumb label.
{% endhint %}

## On Narrow Screens

On a phone the trail is kept to a single line. The most recent entries are shown, with everything before them collapsed behind an ellipsis that expands the full trail when selected, and the bookmark button moves to the right-hand edge of the row.

Where the trail would say nothing the page does not already say, it is hidden altogether. That covers pages with a single entry, and the Home page and dashboard, whose trail only repeats the views their own picker offers. See [Mobile Layout](/user-documentation/shared-features/mobile-layout.md).

## Bookmark Button

The bookmark button sits at the end of the breadcrumb trail and adds or removes the current page from your bookmarks. An outlined bookmark means the page is not yet saved, and a solid, coloured bookmark means it is.

The bookmark takes its name from the last entry in the breadcrumb trail and is filed under the top-level menu heading that page belongs to, so renaming or restructuring the menu is reflected in new bookmarks automatically.

{% hint style="info" %}
The button is hidden on pages whose address identifies a specific record, such as an individual user or group, because bookmarks store only the page address and saving one of these would reopen an empty page.
{% endhint %}

For managing your saved bookmarks, see [Bookmarks](/user-documentation/shared-features/menu-bar/bookmarks.md).

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cipp.app/user-documentation/shared-features/breadcrumb-navigation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.