Start here by responsibility

Find the part of the documentation that matches what you are trying to do in Lleverage.

Lleverage can be used by people doing operational work, people configuring how that work is executed, and people administering the Project or organisation.

These are documentation paths, not fixed job titles or permission bundles. One person may use more than one path.

If you are new to the product model, start with What Lleverage is. If you already know the operational process you are dealing with, jump directly to the path below.

I am doing operational work

Start with Run operations.

Use this path if you mainly:

• work with the Agent;

• use published Workflow apps;

• respond to Requests assigned to you;

• need to understand the operational area through the Project overview.

If you are unsure which surface matches the task in front of you, use Finding your way around a Project.

I am improving or configuring how the work runs

Start with Build and improve.

Use this path when you need to change:

• repeatable execution in Automate;

• Skills, Memory, Tables, Files or Knowledge under Intelligence;

• testing, publishing and human handoffs;

• execution evidence and recurring issues in Monitoring.

The builder path assumes you need to understand how the execution is configured, not just how to use it.

I am administering access, systems or project configuration

Start with Control.

Use it for Connections, Channels, Schedules, Members, Settings, API Tokens, AI Models, Databases, Secrets, Variables and Metrics.

For broader questions about operational ownership, rollout or assurance, continue to Governance, Rollout and operations or Security and assurance.

I am trying to understand the overall model

Start with What Lleverage is.

Useful next pages are:

• Operational examples for representative processes and language;

• Humans, Agent and Workflows for the execution model;

• From manual to autonomous for the supporting autonomy ladder;

• Projects and solutions for the Project boundary and Solution language.

The throughline is consistent across all paths: start from the operational work that needs to get done, then configure the right mix of foreground work, background execution and human attention.