What the Agent can use

Understand the main sources and capabilities the Agent can use during a task.

The Agent is useful because it can work with more than the conversation itself.

Depending on the Project and your access, it can use:

• Project instructions — durable direction about the operational area and general behaviour;

• Skills — reusable ways of doing recurring work;

• Files — task inputs, evidence and outputs;

• Connected systems — authorised access to ERP, CRM, email and other systems;

• Knowledge — maintained reference material;

• Tables — maintained structured data and mappings;

• Memory — useful context carried across sessions;

• Workflows — repeatable execution for stable parts of a process.

Lleverage can also provide built-in Skills and general industry or process knowledge as a starting point.

Available does not mean authoritative

Different sources play different roles.

A current ERP record, approved policy or maintained customer-specific mapping can be authoritative. A remembered preference, uploaded case file, general industry pattern or Agent inference can still be useful without having the same status.

When the distinction matters, tell the Agent which source should win and what to do when sources disagree.

Scope matters

In a web Agent session, the current Project is explicit.

Slack and Microsoft Teams can also run without one fixed Project. In that case, the Agent only uses eligible capabilities from Projects the acting user is authorised to access.

Pin a channel conversation when the work should clearly stay inside one Project or when several Projects have overlapping capabilities.

What the session shows

The session's Context and Memory views help you inspect supporting material around the work.

Treat those views as evidence, not a complete ledger of everything that influenced the result. A tool being visible does not make its data authoritative, and an empty panel is not proof that no capability contributed.

For important work, verify against the system, document or maintained source that should own the fact.

Use the pages below when you want to understand one capability in more detail. Builders who need to configure these sources should continue to Build and improve or Control.