> For the complete documentation index, see [llms.txt](https://docs.avis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avis.net/avis-creative-studio/canvas-fundamentals.md).

# Canvas Fundamentals

This section explains how the Canvas works and how to use it to organize assets, nodes and workflows in Avis Creative Studio. You will learn how to connect processing steps, manage projects, members and costs, and use shortcuts to work faster.

#### In this section

* **How the Canvas Works:** Understand how the Canvas organizes and connects the steps of a workflow.
* **Canvas Interface Overview**: Get to know the main areas of the Canvas, including the Add menu, the bottom toolbar and the Help menu.
* **Node Mental Model**: Understand inputs, outputs, nodes and how they relate to each other.
* **Connecting Nodes**: Add nodes, connect them and build a processing flow.
* **Projects & Members**: Organize projects and manage the people you work with.
* **Project Costs**: See how much your project has spent on AI generation and who spent it.
* **Shortcuts**: Use keyboard shortcuts and quick actions on the Canvas.

By the end of this section, you will be able to read, build and manage a workflow on the Canvas with confidence.


---

# 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.avis.net/avis-creative-studio/canvas-fundamentals.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.
