Finding your way around a Project

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.

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

The same Project with the sidebar collapsed to the icon rail

I need Lleverage to work through a case

Go to the Agent.

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 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.

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 if you need the distinction.

I want to know what happened

Builders use Monitoring 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.

• Automate for repeatable Workflow execution;

• Intelligence for reusable methods and context;

• Monitoring for evidence about what actually ran.

I need to manage access or systems

Go to Control.

• Connections for external systems;

• Members for Project access;

• Channels for Slack and Microsoft Teams Agent routing;

• Settings 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 — choose the broader docs path that matches your role in the work.

• What Lleverage is — understand how Agent, Workflows, human handoffs and Projects fit together.