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 someone who cannot access its owning space area. The document keeps the access rules of the space, subspace, or activity where it belongs.
Bring A Document Into The Conversation
Drag a document from Documents into Chat when the discussion needs the original material close at hand. You can drag one item directly, or select several related items and drag one of the selected cards to carry the whole set. This is useful for gathering a brief, references, and supporting media in one message without uploading each item again.
Chat accepts only the items that fit in the message's remaining attachment capacity. Existing attachments in the composer count toward the same limit, so a large selection may be accepted only in part. Visual Space warns when the limit is reached and leaves the accepted items in the composer for review.
Before sending, check the composer as you would for any other message:
Stored images, videos, and files can use their existing material in the message. Other document types are shared as links that return readers to their Visual Space content. In either case, the item stays in Documents; sending the message does not move it out of its folder or change its audience.
For the complete drag, review, and send flow, see Share Documents in Chat. Files and Previews explains how different uploaded formats behave when opened.
Keep A Personal Return Path With View Later
Use View Later when a document deserves attention but not an immediate interruption. Open the document's menu and choose View Later. The menu then offers Remove View Later, making the saved state easy to recognize and reverse.
View Later creates a personal return path, while Add To Expo is a separate space-curation action.
View Later is a personal reminder, not a new folder and not a shared collection. Saving an item does not move it, duplicate it, publish it, or tell other members to revisit it. When you open the saved entry, Visual Space returns you to its Documents context so you can continue from the shared library.
The saved entry is only a route back. If the document is deleted or your access to its space area changes, View Later does not preserve a private copy or bypass the current access check. Remove the entry from the document menu when you no longer need the reminder.
Curate Published Work In Expo
Expo is the space's selected showcase, while Documents is the broader working library. Use Expo for published material that helps members understand the space, discover a strong contribution, or find an important result without browsing every folder and upload. The Expo guide explains how eligible work reaches the showcase.
This is a space-curation responsibility. The document menu shows Add To Expo or Remove From Expo only to the space owner and members with permission to manage Expo. Drafts are excluded. An item must be an eligible published document before it can be featured, which prevents unfinished work from entering the showcase.
For eligible material, the two actions have focused effects:
Expo does not replace publication or access rules. Featuring a document helps the appropriate audience discover it, but does not turn a private-area item into unrestricted content. If a document needs editing, publication, or a clearer public presentation first, continue with App Files and Publishing.
Collect Durable Articles In Wiki
Wiki is the space's curated reading tree for durable published articles. It differs from Expo in both content and presentation: Expo can showcase several kinds of published work in a visual collection, while Wiki accepts article documents only and presents them under their current space areas and folders.
The space owner or a member with the Manage Content permission can choose Add to Wiki from an eligible published article's Documents menu. After the change succeeds, the menu offers Remove from Wiki. Drafts, folders, uploaded files, and other app files remain outside Wiki.
Adding the article records a curation choice, not another location. Moving the article or renaming one of its folders in Documents changes the next Wiki tree automatically. Removing the Wiki placement leaves the article published in its normal Documents location. Follow Curate a Wiki for the complete workflow.
Respond To Shared Work
Some published content opened from Documents carries the same reactions wherever that content appears in Visual Space. This lets appreciation and feedback stay attached to the work instead of fragmenting between its Documents entry and connected article, post, event, goal, or retrospective view.
Reaction controls show the emoji and combined count. Open an emoji to inspect the reaction details, including the people who chose it. When your access and reaction permissions allow, you can add your own reaction or select your existing reaction again to remove it.
Reactions are best for quick, visible acknowledgement. They do not change the document's publication state, move it, or add it to Expo. Use Chat when the response needs context or a decision; use a reaction when the shared signal is enough.
Choose The Connection That Fits
These paths solve different needs while keeping Documents as the source:
If the real need is to change where the source belongs, use Organizing Documents instead. Sharing and revisiting create routes to the document; organizing changes its library location.
Common Questions
Does sharing a document in Chat move it out of Documents?
No. Chat receives an attachment or document link for the message, while Documents remains the source location.
What happens if my selection is larger than the available Chat attachment capacity?
Chat accepts the items that fit and warns that the limit was reached. Review the composer before sending, then share any remaining items in another message if needed.
Can someone open a shared document link without access to its space area?
No. A message link, View Later entry, or Expo appearance does not bypass the document's current access rules.
Is View Later a Documents folder?
No. It is a personal saved route back to the document's context. The document remains in its original Documents location.
Who can add a document to Expo?
The space owner and members with permission to manage Expo can curate eligible published documents. Drafts do not offer the Expo action.
Does removing a document from Expo delete it?
No. It removes the showcase placement only. The document remains in Documents for people who can access its owning area.
Does adding an article to Wiki give it a separate Wiki folder?
No. Wiki follows the article's current space area and folder placement from Documents. Move or rename the source in Documents when that structure needs to change.
Why do reactions look the same on connected content surfaces?
Document-backed content uses shared reaction totals and author details, so the response stays connected to the same work when it appears in supported views.