> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/getting-started/studio-navigation.md). # Studio navigation

UI	Description	Related topics
Top bar	The top bar includes the menu, tools, mode switching, and a button to share the project.	Design mode Animations Interactions Comments Sharing Menu - Settings
Left panel (scene panel)	The panel displays the entire structure of the project (objects, modifiers, UI, lighting, etc.). In the Workspaces tab, access is provided to all user projects that can be imported into the current scene.	Scene panel Asset library
Right panel	The properties panel dynamically displays settings based on the current selection. When no object is selected, the panel shows the canvas settings by default. When no object is selected, the scene settings are displayed. To return to the scene settings, press `Esc` or left-click on any empty area of the canvas.	Environment Background Ground plane Augmented Reality (WebAR) Variables & Expressions Effects Loading screen Mouse controls Interaction prompt WebXR (beta) Performance analyzer
Canvas	The main viewport where all scene objects are displayed and manipulated.	Scene orientation Rendering Background Ground plane Effects
Control bar	A small bar located at the bottom of the canvas for quick access to frequently used functions	Control bar

--- # 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://help.vectary.com/documentation/getting-started/studio-navigation.md?ask=&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.