> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/platform/navigation.md). # Navigation Each project's sidebar can be tailored to how that project is used. You can choose between two layouts, decide where people land when they open the project, pin any page to the sidebar, and control which help options appear. Most of this is managed in the project's settings; pinning happens straight from page headers. ### Key Features * Two sidebar layouts: Agent and Workflows * A default page setting that decides where people land * Pinned pages with custom labels, icons, and collapsible groups * Quick access to saved views from the sidebar * Configurable help options at the bottom of the sidebar ### Layouts Open the project's settings and go to the **Navigation** tab. Under Customise Sidebar, the **Layout** setting offers two presets: * **Agent**: an agent-first sidebar, and the default for new projects. It removes Dashboard, Apps, Sessions, and Requests from the sidebar so the agent takes centre stage. * **Workflows**: the classic workflow-building sidebar. It removes the Agent items and keeps the familiar building and monitoring pages. > 💡 The layout applies to everyone in the project, so pick the one that matches how the project is mostly used. ### Default Page The **Default page** setting, on the General tab of the project's settings, decides where people land when they open the project. Depending on the layout, you can choose Dashboard, Agent, Requests, or any pinned page. > 💡 You can also make a pinned page the landing page directly from its pin dialog, using the "Default page" toggle. ### How to Pin a Page Almost any page in a project can be pinned to the sidebar, so the pages a team uses most are always one click away. 1. **Open the page** you want to pin and click the pin button in its header. 2. **Name it**: give the pin a label (up to 40 characters). 3. **Pick an icon** so it's easy to spot in the sidebar. 4. **Click Pin**: the page appears in the sidebar for everyone in the project. To change or remove a pin, click the pin button again on that page and edit the details or choose Unpin. Some lists, such as workflows and data tables, also offer "Pin to sidebar" in their menus. > ⚠️ A project can have up to 30 pins. Pinning is available to builders and up. ### Grouping Pins Pins can be organised in the **Pins** tab of the project's settings, where you can rearrange, rename, group, or remove them. 1. **Create a group**: click "New group" and give it a name. 2. **Fill it**: drag pins below the group row to move them into it. 3. **See it in the sidebar**: the group becomes a collapsible heading that people can expand and collapse. > 💡 Removing a group doesn't remove its pins; they just become ungrouped again. ### Saved Views in the Sidebar In the Agent layout, hover over Monitoring in the sidebar to see your saved activity views and jump straight to a filtered view of your runs. ### Help Options The Navigation tab also controls which help options show in the sidebar: * **Chat Support**: let people reach chat support from the sidebar. * **Report Bug**: let people report a bug from the sidebar. * **External Support Link**: add your own link, such as an internal help desk, with a custom label (up to 20 characters). It opens in a new tab. The same tab includes display options for the sidebar's sessions list, such as whether people can filter it and how it's grouped and sorted by default. > 💡 Project owners manage these settings, so a project shared with a wider team can present exactly the support routes that team should use. --- # 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.lleverage.ai/platform/navigation.md?ask=&goal= ``` `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.