> 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 Find the right Lleverage surface from the operational situation you are dealing with. The easiest way to navigate Lleverage is to think about **what you are trying to do**, not to memorise every menu item. If you are not yet sure what this Project is responsible for, start with the [Project overview](/run-operations/overview/project-dashboard.md). ## Adjust the Project sidebar The left sidebar can be collapsed to a slim icon rail when you want more room for the page, or resized by dragging its edge. Hover a pinned page to open its recent items without changing pages. These controls change how much navigation is visible, not where pages live or what you are allowed to access. Project navigation can still differ between Projects based on its configured navigation and your access. ![Project sidebar expanded](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-4cb68e46d89892166c4106b820bf41b31f4ec350%2Flleverage-shell-expanded-clean.png?alt=media) ![The same Project with the sidebar collapsed to the icon rail](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-10c3fe08958144bacacd6e66563a1894c52a6d8e%2Flleverage-shell-collapsed-clean.png?alt=media) ## I need Lleverage to work through a case Go to the [Agent](/run-operations/agent.md). Use it for work that requires interpretation, investigation, files, connected systems or several steps that may vary by case. ## I need to complete a structured process Go to [Workflow apps](/run-operations/workflow-apps.md) if your organisation has published an app for that work. The app may collect information, guide a conversation or start background execution. ## I need to handle a decision or exception Go to [Requests](/run-operations/request-inbox.md). This is where configured Workflows ask assigned people for a decision or missing information. Agent questions inside a session are separate; see [Requests, exceptions and human attention](/understand-lleverage/readme/requests-exceptions-and-human-attention.md) if you need the distinction. ## I want to know what happened Builders use [Monitoring](/build-and-improve/monitoring.md) to inspect runs, failures, traces and recurring execution patterns. The current **Operator** role does not see Monitoring, Sessions, Automate or Tables. If you are operating the process, first use the visible result, Agent session or Request context and escalate to a builder when deeper execution evidence is needed. ## I need to improve the way the work is executed Go to [Build and improve](/build-and-improve/overview.md). * [Automate](/build-and-improve/automate.md) for repeatable Workflow execution; * [Intelligence](/build-and-improve/intelligence.md) for reusable methods and context; * [Monitoring](/build-and-improve/monitoring.md) for evidence about what actually ran. ## I need to manage access or systems Go to [Control](/administer-and-govern/control.md). * [Connections](/administer-and-govern/control/connections.md) for external systems; * [Members](/administer-and-govern/control/members.md) for Project access; * [Channels](/administer-and-govern/control/channels.md) for Slack and Microsoft Teams Agent routing; * [Settings](/administer-and-govern/control/settings.md) for Project and Agent configuration. Different people may use the same Project differently. These are responsibilities, not necessarily fixed user roles. ## Related pages * [Start here by responsibility](/understand-lleverage/readme/start-here-by-responsibility.md) — choose the broader docs path that matches your role in the work. * [What Lleverage is](/understand-lleverage/readme.md) — understand how Agent, Workflows, human handoffs and Projects fit together. --- # 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=&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.