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

# Run operations

Use Lleverage to carry operational work forward, respond when your judgement is needed, and verify what happened.

This part of the documentation is for people using Lleverage to get operational work done.

Start from the work in front of you: an order needs processing, a supplier response needs investigating, a planning question needs answering, a Workflow app needs completing, or an automated process is waiting for your decision.

You do not need to understand how every Workflow is built. What matters is where the work appears, what you are expected to do, and what happens after you act.

## If you need Lleverage to work through a case

Use the [Agent](/run-operations/agent.md).

The Agent is the main flexible foreground work surface. Use it when you need to give Lleverage a task directly, investigate something across systems, work with files or continue a piece of work conversationally.

## If a process gives you a structured task

Use a [Workflow app](/run-operations/workflow-apps.md).

A Workflow app is the operator-facing interface to a published Workflow. You complete the input or interaction the process needs; the rest of the work may then continue in the background.

## If work is waiting for your judgement or information

Go to [Requests](/run-operations/request-inbox.md).

A Request is a deliberate human handoff in a running Workflow. Review the context, provide the requested decision or information, and submit it so the execution can continue.

Agent questions inside a session are separate from these Workflow-created Request items.

## You may only see part of the execution

Some work happens while you are actively using the Agent or a Workflow app. Other work continues in the background through Workflows. It may surface again only when a Request needs your attention or when the result is ready.

That is normal: Lleverage is designed so operators do not have to drive every step in order to remain involved where their judgement matters.

## Orient yourself in the Project

Use the [Project overview](/run-operations/overview/project-dashboard.md) to understand what area of work the Project covers and which capabilities are available. If you are unsure where to go for a specific job, see [Finding your way around a Project](/run-operations/overview/navigation.md).

## Where to go next

* Flexible task or investigation → [Agent](/run-operations/agent.md)
* Structured published process → [Workflow apps](/run-operations/workflow-apps.md)
* Human decision or missing information → [Requests](/run-operations/request-inbox.md)
* Need to understand the Project first → [Project overview](/run-operations/overview/project-dashboard.md)


---

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