New | Visual Space - Page 29

Documents supports two ways to begin publishable work. You can create an Article, Event, Retrospective, or Whiteboard from `New`, or you can choose `Publish` on an existing upload to make a separate article-style draft around it. Both paths keep unfinished work private to its author until publication. Choose the first path when the work should begin in a Visual Space editor or collaborative app. Choose the second when you already have a source file that should remain available in its original fo

Use this walkthrough to turn a crowded Documents area into a library that members can understand. You will inspect the current location, build a small folder structure, move the exact items that belong together, and verify both placement and access before cleaning up anything left behind. This guide is for space owners and members who see space-management controls. **The space-owner path is the dependable management path.** A member with space-management access may see move, rename, or folder co

Documents remains the home of a file, article, or app file even when people use it elsewhere. You can bring a document into Chat for discussion, save it to View Later for yourself, feature eligible published work in Expo, collect a published article in Wiki, or respond to document-backed content with a reaction. Each route adds a useful connection without creating a second source location. That distinction matters for access. **Sharing, saving, or featuring a document never makes it available to

Organizing Documents is less about keeping a perfect folder tree and more about making deliberate changes that other members can understand. Select only the material you intend to affect, choose a destination that matches its community context, then check both the old and new locations before continuing. Documents supports quick single-item moves and larger cleanups across folders, subspaces, and activities. The same location rules apply in both cases: ordinary folders organize content beneath a

Documents gives a space one connected library for folders, uploads, articles, and supported app files. Its structure begins with the areas members already know, then adds ordinary folders for more detailed organization. This keeps a file's location understandable without creating a second map of the community.

Documents is the shared library for a space. Use this guide to understand how folders, uploaded files, articles, and supported app files stay connected to the spaces, subspaces, and activities where people work.

Documents is the shared library for a space. It brings uploaded files, folders, articles, and supported app files into one place, then arranges them by the same spaces, subspaces, and activities that members already use elsewhere in Visual Space. That shared structure is the important part. A useful image from Chat, a file uploaded for an activity, and an article created for the same work do not need three unrelated filing systems. They can remain close to the community context that gives them m

Files in Documents form part of a space's shared memory. A direct upload can live alongside images and videos collected from Chat or articles, so useful material remains discoverable after the conversation or publication where it first appeared has moved on. The library accepts many everyday file formats, but it does not pretend that every file can be displayed in the same way. **Preview availability changes how a file is presented, not whether an accepted file remains useful.** A file without a

Use this walkthrough to start a one-to-one conversation, expand it into a group when appropriate, and manage the group without losing sight of who can read its history. The most important decision comes before you add anyone: confirm that every new participant should be able to see the conversation's retained messages and attachments.

Documents can hold more than uploaded files. Articles, Events, Retrospectives, and Whiteboards can appear in the same library, close to the folders and space areas where people expect to find them. These entries are app files: selecting one opens the Visual Space experience that owns the content rather than treating it as a generic download. Publishing an upload uses a related but importantly different path. **The uploaded file and the article-style document created from it remain separate libra