> 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/getting-started.md).

# Getting Started

Welcome to the Avis Creative Studio User Guide. Learn how to set up Studio, work on the Canvas, use each node and tool, and combine them into real creative workflows.

> Avis Creative Studio is in active development. Some sections are still being expanded and will be updated alongside new releases.

This section helps you get familiar with Avis Creative Studio, from signing in and installing the app to organizing your projects, workspaces and assets. You will learn how Studio is structured, how to create a new project and how to prepare your workspace for the creative workflows that follow.

#### In this section

* **What is Avis Creative Studio?** Learn what Avis Creative Studio is and where it fits in the Avis ecosystem.
* **Sign in & Install** - Sign in, create an account and install the version that matches your device.
* **Interface Overview** - Get to know the main areas of the Studio interface.
* **Create a New Project** - Create a project and open its workspace to start working.
* **Workspace Basics** - Understand how Projects, Workspaces and Canvases relate to each other.
* **Import Assets** - Bring images, videos, audio and other assets into your workspace to use in your workflows.

By the end of this section, you will have everything you need to start building and managing creative work in Avis Creative Studio.


---

# 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/getting-started.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.
