Home | Visual Space - Page 22

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

Search can look across Visual Space or stay within the space you are currently using. That choice changes the range of a query, but it never opens content that you could not already read. This distinction matters most when a familiar item is missing. The active scope may be too narrow, or your current access may not include the space, area, or conversation that owns the item. Search keeps both boundaries visible and applies them together.

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

This walkthrough helps you share files with the right people, follow the upload through completion, and confirm that recipients can open what you sent. It applies to both [Activity Chat](../activity-chat.md) and [Direct Messages](../direct-messages.md), with an important difference in where the files live.

This walkthrough turns one valuable Activity Chat message—or an idea that has grown beyond a chat message—into a reviewed article. Use it when a contribution deserves a durable life outside the rapid conversation, but does not represent the outcome of the whole topic.

Use this walkthrough to keep important conversations close, quiet noisy discussions, clear unread attention at the right scope, and step away when a conversation should no longer reach you. Most of these choices organize only your own **Messages** view. Blocking and leaving go further because they change who can communicate or participate.

This walkthrough takes an Activity Chat topic from an author-only draft to a focused live discussion and a durable summary. Use it when a group is beginning a distinct question, phase, or decision that should remain understandable after the rapid exchange has ended.

Use this walkthrough when one message needs to answer an earlier point, reach a specific participant, and keep a durable link to the work being discussed. You will prepare the message in the right topic, send it without losing its context, verify the result, and correct it in place if needed. The workflow applies to both [Activity Chat](../activity-chat.md) and [Direct Messages](../direct-messages.md). Their audiences differ, but their reply, mention, goal-reference, formatting, and editing tool