> 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/run-operations/overview/navigation.md).

# Project navigation

How the project sidebar works: pinned pages, the Needs me, Chats and Completed list, New, the Configure button and page, and where Members, Agent settings, Chat with us and Report an issue are.

The project sidebar has four parts, top to bottom: the **Configure** button at the top, your **pinned pages**, the list of your chats, tasks and requests (**Needs me**, **Chats** and **Completed**), and **New** at the foot to start a conversation with the Agent. The help buttons, **Report an issue** and **Chat with us**, sit in the sidebar's footer.

What you see depends on your role in the Project. Builders and Admins have the **Configure** button. Operators and Guests do not: they get around the Project from their pinned pages, the list and a **Navigate** section (see [Navigate](#navigate-for-roles-without-configure)).

To see the tour again, open your user menu at the bottom of the sidebar, choose **Lleverage**, then **Tutorials**, then **The new navigation**.

## Pinned pages

Pinned pages are the pages the Project's builders have put in the sidebar for the people who use it, such as the Overview, a Requests view, an app or a Table. Opening a Project takes you to the top page of the sidebar you can see.

* You only see pins for pages you can open. A pin to a page your role cannot reach is hidden for you.
* A pin takes its name and icon from the page it opens.
* Right-click a pin for **Open in new tab**, **Copy link**, **Chat with agent about it** and **Add to favourites**. Builders also get **Rename**, **Move up**, **Move down** and **Remove from navigation**, and for an app **Duplicate** and **Delete**.

### Pin a page to the sidebar

Builders can pin most pages. Choose **Pin to sidebar** in the page's menu, for example on a Workflow, an app, a Table, a page in **Pages**, a Monitoring view or the Requests header. **Unpin from sidebar** takes it out again. On the Overview, use **Pin this page** at the foot of the page.

To rearrange, rename, group or remove several pins at once, open **Customise navigation** (see [Settings](https://docs.lleverage.ai/administer-and-govern/control/settings.md)).

## Needs me, Chats and Completed

Below the pinned pages is one list of everything you are working on, in three tabs with a count on each:

| Tab           | What it shows                                                                                    |
| ------------- | ------------------------------------------------------------------------------------------------ |
| **Needs me**  | Tasks and requests waiting on you, all in one place.                                             |
| **Chats**     | The conversations you started with the Agent. An orange dot marks a reply you have not read yet. |
| **Completed** | Everything that has finished. If something is not done after all, you can move it back out.      |

Each row shows what it is (a chat, a task, a request or an app session), its status and when it last changed. Right-click a row for actions such as **Open in split view**, **Rename**, **Mark as read**, **Complete**, **Archive Request** or **Delete**.

When a tab has more than fits, the last row reads **more…**. It opens **All sessions**, where you can search every chat, request and app session in the Project.

Drag the line above the list to give it more or less room, or hide it with **Hide the agent list**.

## New

**New** at the foot of the sidebar starts a conversation with the Agent. The Agent opens as a tray beside the page you are on and knows which page that is. See [Use the Agent](https://docs.lleverage.ai/run-operations/agent/getting-started.md).

If a builder has switched **Recent Sessions** off on the **Customise navigation** page, the list and **New** are replaced by a single **Agent** link.

## The Configure button and the Configure page

**Configure** is the grid button at the top of the sidebar. It lists every area of the Project, so builders can reach anything without pinning it.

* **Hover** over it to see the areas in groups, with **Search pages** at the top. The cursor starts in the search, so you can type a page name straight away.
* **Click** it, or choose **View all**, to open the **Configure** page. It lists the same areas in columns, with a short description of each, and a search across the whole Project.

On a phone or tablet, tapping **Configure** opens the Configure page.

Every page you open from Configure shows the way back before its title, such as **Project name › Configure › Members**. A page opened from a pin does not.

| Group            | Pages                                                             |
| ---------------- | ----------------------------------------------------------------- |
| **Automations**  | Workflows, Processes, Skills, Schedules, Templates                |
| **Context**      | Pages, Tables, Memory, Files, Knowledge                           |
| **Monitoring**   | Monitoring, All sessions, Programmes, Sessions, Metrics           |
| **Integrations** | Connections, Channels, Databases, API Tokens                      |
| **Settings**     | Members, Agent settings, Customise navigation, Variables, Secrets |

Pages your role cannot open are left out, and an area that only some Projects have (such as Processes) shows only where it is switched on. Any other page you can open appears under **More**.

Whether someone has the Configure button is the **Builder navigation** permission on their role. Admin and Builder have it; Operator and Guest do not. See [Roles and permissions](https://docs.lleverage.ai/administer-and-govern/control/members/roles-and-permissions.md).

## Navigate, for roles without Configure

People whose role does not have the Configure button see a **Navigate** section below the pinned pages instead. It holds the areas their role can open: **Pages**, **Automations**, **Intelligence**, **Data & Storage**, **Monitoring** and **Advanced**. An Operator usually sees only **Pages**. Click **Navigate** to fold the section away.

### Where to find common pages

| To...                                               | Go to                                   |
| --------------------------------------------------- | --------------------------------------- |
| Add people or change their role                     | **Configure → Members**                 |
| Change the Project title, description or Agent tone | **Configure → Agent settings**          |
| Rearrange pins or set the help menu link            | **Configure → Customise navigation**    |
| Connect an external system                          | **Configure → Connections**             |
| Route Slack or Microsoft Teams to the Agent         | **Configure → Channels**                |
| Build or change a dashboard page                    | **Configure → Pages**, or a pinned page |
| See what ran                                        | **Configure → Monitoring**              |

## Help: Chat with us and Report an issue

The help buttons are in the sidebar's footer, next to your user menu.

* **Chat with us** opens Chat support with the Lleverage team. If the Project also has an external support link, the button is called **Help** and opens a menu with **Chat with us** and that link.
* **Report an issue** opens the bug report form.

Whether someone sees these is set per role, with the **Chat support** and **Report a bug** permissions. Both are on for every built-in role, Guest included. The external support link is set on the **Customise navigation** page.

## Collapse or resize the sidebar

Use **Collapse sidebar** at the top to shrink the sidebar to a slim rail, and **Expand sidebar** to bring it back. Drag the sidebar's edge to resize it, or double-click the edge to reset its width. These change how much of the sidebar you see, not what you can open.

## Which area for which job

* Work through a case with the Agent: [Agent](https://docs.lleverage.ai/run-operations/agent.md).
* Complete a structured process: [Workflow apps](https://docs.lleverage.ai/run-operations/workflow-apps.md).
* Handle a decision or exception: [Requests](https://docs.lleverage.ai/run-operations/request-inbox.md). Requests waiting on you also show under **Needs me**.
* See how the work is going: [Pages](https://docs.lleverage.ai/run-operations/overview/pages.md) and the [Overview](https://docs.lleverage.ai/run-operations/overview/project-dashboard.md).
* Find out what happened: builders use [Monitoring](https://docs.lleverage.ai/build-and-improve/monitoring.md).
* Change how the work runs: [Build and improve](https://docs.lleverage.ai/build-and-improve/overview.md).
* Manage access, systems or settings: [Control](https://docs.lleverage.ai/administer-and-govern/control.md).

## Related pages

* [Pages: the Overview and custom pages](https://docs.lleverage.ai/run-operations/overview/pages.md), the dashboards you pin and share.
* [Start here by responsibility](https://docs.lleverage.ai/understand-lleverage/readme/start-here-by-responsibility.md), the docs path for your role in the work.


---

# 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.lleverage.ai/run-operations/overview/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.
