Visual Space - Page 3 | Visual Space

Meetings bring voice, video, screen sharing, and shared work into the part of Visual Space where a conversation is already happening. An activity or direct-message conversation provides the room, while the surrounding workspace stays available before, during, and after the call. **Continuity is the defining idea.** Joining does not make the meeting a separate destination that takes over your work. You can open the full meeting stage when you want everyone in view, then return to an activity, doc

Meeting controls keep the essentials close while you are speaking, presenting, or watching someone else. The main call bar handles immediate actions; nearby selectors help you change equipment or choose what to share without leaving the meeting stage. These controls serve different purposes. **Muting changes whether others hear you**, turning off the camera removes your video, stopping a screen share removes only the content you were presenting, and hanging up leaves the meeting altogether.

Meeting live apps turn supported workspace content into a selectable feed inside an activity meeting. The group can read, discuss, and work in the relevant app without leaving the call or replacing the surrounding Visual Space context. **A live app is shared meeting content, not a screen share.** It keeps the workspace interactive and gives its own tools room alongside the meeting controls. Cameras, participant audio, screen shares, and other live apps remain available as separate feeds.

Meetings brings live conversation and shared work into activities and direct messages without separating the call from the rest of Visual Space. Start with the overview, explore the part of the meeting you need, or follow a complete task from joining through hanging up.

This walkthrough takes a Blueprint from an empty, references-first file to a saved CAD-lite design with a closed sketch, a dimension, the supported horizontal constraint, an extruded preview body, a model-linked drawing, and an exported `.svg` sheet. You will also inspect the design, leave review context beside it, and reopen the file to prove that its editable snapshot returned. Blueprints is useful for concept parts, learning, and technical review. **The body, measurements, and drawing remain

This guide helps the active editor make a deliberate choice between keeping a draft editable and publishing its layout entry as permanently read-only. You will export and verify a PNG first, confirm that the current tab still owns editing, publish only when the one-way result is useful, and check the published state afterward.

Use this walkthrough to move from a space area into the right Live App, find or create an item, and confirm both access and persistence before you begin substantial work. You will reach the editor with a clear expectation of what can return after you leave.

You will create or open an unpublished layout, draw a small measured plan, review it, and export the visible canvas as a PNG. This guide is designed for a single focused editing session because the current drawing does not reopen after you leave, reload, or switch sessions.

This walkthrough takes a Canvas from an empty area-owned file to a small layered artwork that you can safely leave and reopen. Along the way, you will paint on one layer, add editable text, test the layer controls, confirm the online save, and optionally keep a local `.vscanvas` project copy.

You will build a small local 3D scene, organize and inspect it, test one reversible edit, and download the supported result as a `.gltf` file. The finished export can carry visible Poly primitives, groups, transforms, and basic materials, but **it is not a saved Poly project** and cannot preserve the whole editing session.

Use this walkthrough to assemble a short local sequence in Frames, check its timing, and capture the editing decisions you want to keep. You will finish with a useful session draft and review plan, **not a rendered or finished video**.

Poly is an approachable 3D scene editor for arranging objects, exploring spatial ideas, and checking how a small scene looks from different views. Its workspace keeps the 3D viewport at the center, with the Scene hierarchy, object controls, materials, camera tools, assets, and history close at hand. **Poly currently keeps drafts and scene edits only in the active app session.** A draft can look like a file in Poly's explorer, but its objects, transforms, materials, imports, and history are not s

Live Apps are focused creative workspaces that stay connected to the space area where the work belongs. You begin with familiar file browsing, then open a dedicated editor for drawing, video, spatial planning, 3D scenes, technical designs, or formulas. That shared shape makes it easier to move between ambitious tools without losing the surrounding Visual Space context.

Layouts gives you a fast, measured 2D workspace for sketching rooms, renovations, office arrangements, event setups, and other floor-plan ideas. It combines a meter grid with approachable drawing tools, so you can communicate dimensions and spatial relationships without starting a full building-design project.

Live Apps bring focused creative tools into the spaces where people already plan, discuss, and review their work. Use this guide to choose the right workspace, understand what will be saved, and continue into a practical walkthrough.

Frames is a focused video-timeline workspace for assembling and reviewing an early sequence. It brings clips, captions, titles, audio, markers, and editing controls together so you can explore the shape of a video before a production media and export workflow is involved.

Canvas is Visual Space's layered workspace for painting, image composition, and artwork drafts. A Canvas belongs to a space area, opens in a focused editor, and stays connected to the documents and conversations around the work. Its editable project can be revisited instead of becoming a flattened picture after every session.

Blueprints is a CAD-lite workspace for people who need a technical idea to keep its measurements and design intent. Makers can explore a simple part, students can learn how references and constraints shape geometry, and reviewers can inspect a design without separating the model from its discussion. The emphasis is **controlled geometry**, not merely producing a convincing picture of an object.

This walkthrough turns a busy Goals workspace into an understandable plan. You will shape the active workflow, move later work into the backlog, make responsibility visible, and then use filters and search without disturbing the order you established. The guide is primarily for space owners and goal managers. Wherever a reporter, direct assignee, or member of an assigned role can perform an action on an individual goal, that step is marked **Goal editors**. For the concepts behind the workflow,

Finishing a goal has two stages. First, a goal editor moves the goal into a column whose category is `Done`. Later, a space owner or goal manager can clear that whole column from the active board into Done Goals history. This walkthrough takes you through both stages and helps you check the result before the completed work becomes a lasting read-only record.

Use this walkthrough when an idea is ready to become visible work. You will place it in the right space area, publish it to a workflow column or the backlog, develop its article, add responsibility and a color tag where useful, then confirm that other members can recognize it on the board. Goal creation is immediate: there is no draft stage in the current board and backlog flow. A clear title is enough to create the goal, but the linked article is where you explain the result, context, and invit

Goals helps a community turn shared ideas into visible, organized work. Use this guide to understand the planning model, choose the right surface, or follow a complete workflow from creation through completion.

Goals gives a community a shared place to turn ideas into visible work. It is a lightweight planning layer for a space: structured enough to show what matters and who is helping, but deliberately less formal than a company project tracker. Each goal combines two useful shapes. On the board it is a compact card that can move through the community's workflow. Open it, and it becomes a full article with the context, discussion, and supporting content needed to help someone understand the work and c

Completed Goals keeps finished work available as a record of progress after it no longer needs space on the active board. It is the second stage of completion: first a goal reaches a `Done` category, then a manager may clear that column into history without deleting the goal or its article.

The Goals board keeps a community's active work visible without turning participation into a heavy project-management process. It gives members one place to see what is waiting, what is underway, and what has been finished, while leaving future work in the [backlog](backlog.md).

Use this walkthrough to place important published work in Expo, confirm where it appears, and remove it when it no longer belongs in the showcase.

Use this walkthrough to find selected work without searching the entire document library. For the broader purpose of the showcase, start with the [Expo overview](../expo.md).

Expo turns selected published work into a focused showcase for a space and its areas. Use this guide to understand what appears at each level, explore community highlights, or maintain the selection as a space owner.

Expo is the official showcase for a space and its areas. It brings selected posts, articles, events, goals, and documents into one visual collection so visitors can quickly understand what the community values and has accomplished.

Use this walkthrough to keep a published event accurate as plans change. You will update the event article, make only the schedule changes allowed by its current state, and confirm that the article and event card still agree.

Use this walkthrough to prepare a scheduled community occasion privately, then publish it for members of the right space, subspace, or activity. You will finish with an event card that opens into a detailed event article.

Events helps a community plan scheduled occasions, make likely attendance visible, and preserve the surrounding context after the date has passed. Use this guide to understand the event model or follow a complete journey from private draft to lasting community record.

Events gives a community one place to coordinate scheduled moments such as planning sessions, workshops, demos, larger meetings, and shared deadlines. It keeps the date and expected attendance easy to scan while giving every event enough room to explain why people should join. Events belongs to the area where the occasion is organized. A space can host community-wide events, while a subspace or activity can keep a more focused schedule close to the people and work it concerns. This makes Events

An event article is the durable home for a scheduled community occasion. The event card gives members a compact view of what is happening and when; opening it reveals the fuller explanation, conversation, and related material that people need before, during, and after the event. This pairing keeps scheduling and context together. Members can scan Events to make an attendance decision, then open the same event to understand the agenda, contribute to the discussion, or revisit what happened later.

Attendance gives members a quick way to share whether they expect to join an event. The three response counts help coordinators estimate likely participation without turning Events into a personal calendar or asking everyone to explain their schedule.

Documents accepts everyday media and project files while keeping upload rules visible at the point where they matter. You can add several files at once, bring in a folder tree, and recover from one failed item without losing sight of the rest of the batch.

Use this walkthrough to add a batch of files or an existing folder tree to Documents, follow every result, and confirm that the new material arrived in the right part of the space. The destination matters as much as the files: everything you upload inherits the audience of the space, subspace, or activity that contains it.

Use this walkthrough to bring one document or a carefully chosen set from Documents into an active Chat conversation. You will keep the source material in its library location, review exactly what Chat accepted, add a useful explanation, and confirm that the resulting attachments or links respect the source access rules.