> 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/build-and-improve/automate/build-a-workflow/canvas-reference/canvas-controls.md).

# Canvas controls

Canvas controls help you navigate and organise the Workflow without changing its business logic.

## Bottom canvas bar

The current bottom bar contains, from left to right:

* **Zoom Out** and **Zoom In**;
* **Fit to View**;
* **Collapse all / Expand all** Workflow actions;
* **Show Copilot / Hide Copilot**;
* the **Freeform / Structured** layout switch;
* **Add Action**.

The minimap is a separate floating panel at the bottom of the canvas rather than part of this control bar. It is useful when the Workflow extends beyond the current viewport because it shows the overall shape of the flow and your current position inside it.

## Moving around the canvas

Pan across the canvas to reach actions outside the current view. Zoom out when you need structure; zoom back in before editing detailed configuration.

Use **Fit to View** when you have lost the main path or after moving several actions. These controls change presentation, not the execution semantics of the Workflow.

## Adding actions

Use **Add Action** when you want to place another step in the Workflow. You can then connect it into the execution path. In places where the UI exposes a connection point from an existing action, you may also be able to extend the path directly from that point.

## Layout is not logic

Moving a card or making the canvas visually tidy does not by itself change the business rule. Connections, action configuration, branches, variables and bindings determine what runs.

Keep the visual layout aligned with the execution path because it makes review and debugging easier, but verify the actual connected path before publishing.

For the cards themselves, see Action Cards. For path semantics, see Action Connections.


---

# 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/build-and-improve/automate/build-a-workflow/canvas-reference/canvas-controls.md?ask=<question>&goal=<user_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.