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.
One Library For Shared Files
Files arrive in Documents from more than one part of a space. Members can upload directly into the open space, subspace, activity, or folder. Media attached to chat and media embedded in articles is also collected in Documents, making it easier to find after the original conversation or article has moved on.
Direct uploads support several files in one selection. On the web, a folder upload can preserve the selected folder's nested structure, creating matching folders and placing each file under the right parent. This is especially useful when a project already has a useful structure on your computer.
Uploads inherit the access of their location. A folder does not create a separate privacy boundary, so placing a file deeper in the tree does not by itself make it more or less visible. See Library And Folders for how locations and inherited access work together.
Follow Every File
The upload tray shows each selected file separately. A file moves through upload progress, a short processing stage when needed, and then success or failure. You can collapse the tray while uploads continue and expand it again to inspect the batch.
This per-file view matters for large selections:
The tray is part of Documents. Stay in Documents when you need to monitor or review the batch.
Per-File Upload Limits
Each file must fit the limit for its type before the space's remaining storage is considered. The current starting limits are:
These are starting points, not a promise that every member in every space has the same ceiling. Applicable subscriptions, space ownership, and assigned file-size boosts can change an effective limit. A file-size boost adds upload headroom, while some eligible uploaders receive a higher applicable limit without that rule extending identically to every file category. Documents checks the current space and uploader and reports the actual limit when a file is too large.
File size and space capacity are separate. A file can fit its per-file limit and still fail because the space does not have enough remaining storage. Conversely, adding storage does not necessarily raise the maximum size of one file.
What Counts Toward Space Storage
The baseline allowance is up to 5 GB per space before additional space storage is needed. Storage accounting depends on both privacy and file size:
Folders do not consume extra storage simply because they are nested. The files inside them count according to the same privacy and size rules.
For spaces with assigned storage, the Documents side panel can show used capacity against the total, for example 2 GB of 5 GB used. This gives coordinators and owners an early view of capacity pressure. Where purchase options are available, the same area can lead to additional storage.
Upload choices belong to the open Documents location, while the side panel reports the space's separate storage capacity.
Files That Cannot Be Uploaded
Most common document, media, text, table, and archive formats are accepted. Visual Space blocks formats that can act like applications, scripts, or active browser content. Examples include:
A blocked format is rejected with a file-type message. Renaming the extension does not make an unsafe format suitable for upload; use a safe export format or share the material through an appropriate source instead.
Accepted files do not all receive the same preview. Images, videos, PDFs, and several text or table formats may have a richer preview, while other accepted files use a clear generic card and download action. Preview creation is best effort: if a preview cannot be generated, the original upload can still succeed. See Files And Previews for the viewing experience.
Read-Only Archived Activities
An archived activity remains available for reference, but it is not a place for new content. The New control is disabled in an archived activity, which blocks file uploads, folder uploads, new folders, and new app files there.
If you need to add a file, move to an active space area where you have access to contribute. Archiving is an activity-level state; opening a nested Documents folder does not bypass it.
Recover From Upload Problems
Start with the message attached to the failed file. It distinguishes the decisions that often look similar at first:
For a folder tree, review failures individually rather than assuming the entire folder failed. The preserved folders and successful files can already be present even when one item exceeded a limit.
Common Questions
Why did a small private file reduce storage while a similar public file did not?
All private files count toward storage. Public files count only when they are larger than 10 MB, so visibility changes how the allowance is calculated.
Does a storage boost increase my per-file upload limit?
Not by itself. Storage boosts add space capacity. File-size boosts and qualifying uploader rules affect the limit for one upload; Documents shows the effective limit when it rejects an oversized file.
Why can another member upload a file that I cannot?
The effective limit can depend on the file category, assigned boosts, space ownership, and subscription eligibility. Use the limit shown in your own failure message as the current rule for that upload.
Can I upload into an archived activity's folder?
No. The archived activity is read-only, including its Documents folders. Choose an active area instead.
Will one failed file cancel a multi-file upload?
No. Each file has its own progress and result. Check the failed item, correct its specific problem, and retry only that file.
Where can I learn the complete upload flow?
Follow Upload Files And Folders for the end-to-end task. For the wider module, start with Documents.