Visual Space manual, Docs, Organizing Documents

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 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 space area, while the space, subspace, or activity determines the access inherited by everything inside it.

Select The Exact Set You Want To Change

On desktop, the grid supports familiar selection gestures for the visible documents:

•

Build a selection one item at a time - Hold Command on macOS or Control on other desktop systems while selecting a card. Select an included card again with the same modifier to remove it from the set.

•

Select a visible range - Select an anchor item, then hold Shift while selecting another card. Documents includes the visible cards between them.

•

Draw around several cards - Start in empty grid space and drag a selection rectangle across the cards you want.

The highlight is the best check of what the next bulk action will affect. Opening the action menu from any card in a multi-item selection gives the whole selected set one compact menu with Move and Delete.

Both highlighted cards form one selection, and the untouched bulk menu makes clear that Move or Delete would apply to the complete set.

A normal selection also changes how dragging behaves. Dragging a selected card carries every selected card. Dragging a card that is not part of the selection carries only that card, which is useful when you want to make one quick move without rebuilding the highlighted set.

Selection follows the current visible collection. Changing location or completing an action clears or prunes the set so documents that are no longer visible do not remain silently armed for a later operation.

Choose Between The Move Menu And Dragging

The Move menu is useful when you know the destination space area. It presents the current space and eligible subspaces and activities as direct destinations, so you do not have to browse into each area first. Archived or draft activities are not offered as move destinations.

Dragging is more spatial. It lets you place one document or a selected set in several ways:

•

Drop onto a folder card - Move the dragged items directly into that visible folder. A valid folder displays Move here while it is ready to accept the drop.

•

Drop onto a side-panel folder - Use a folder already visible in the desktop tree as the destination, including a folder under another activity.

•

Open a destination while dragging - Hover over an eligible folder to open it, then drop into the Documents area for that location.

•

Move through an activity - Drag over another activity to switch the Documents context, then finish the move in that activity's document area. A folder-only drag may also be dropped directly onto an eligible activity row.

•

Drop into the open location - After navigating to the intended folder or activity, use the main Documents landing area to move the dragged items there.

Press Escape while a drag is active to cancel the maneuver before a move is committed. This is especially useful when a selected set is larger than expected or a hover has opened the wrong destination. Escape cancels the active drag; it is not a general undo for a move that already completed.

Valid Destinations Protect The Folder Tree

Documents does not accept every apparent destination. A move is ignored or blocked when the destination is missing, belongs to another space, is already the item's parent, or would make a folder contain itself. A folder also cannot be placed inside one of its own descendants.

These checks preserve a usable hierarchy. If a destination does not react to the drag, stop and inspect the source and target rather than repeatedly dropping. The item may already be there, the target may be an invalid part of the dragged folder's subtree, or the location may not be available to you.

Mixed selections can contain items that are already in the target alongside items that are not. Documents skips items that need no location change and moves the eligible remainder. Afterward, verify the destination rather than assuming every highlighted card changed position.

A Folder Move Keeps Its Contents Together

Moving a folder changes the folder's parent; it does not flatten the folder or scatter its children. Nested folders and documents remain in the same arrangement beneath the moved folder.

What can change is the area that owns that hierarchy. Folders do not have separate privacy controls. They inherit access from their space, subspace, or activity, and every descendant follows that same rule. Therefore:

•

A move between ordinary folders under the same space area changes organization without creating a new audience.

•

A move into a different subspace or activity places the item or moved folder tree under that destination area's access rules.

•

A stable document link does not bypass the destination's membership or privacy requirements.

Treat a cross-area move as an access decision as well as a filing decision. Check that the destination has the intended participants before moving sensitive material, then open the destination and confirm the content appears where expected. The Documents Library And Folders explains the relationship between folders, space areas, and inherited access in more detail.

Manage Folders From The Side Panel

The desktop side panel and the document grid show the same folder hierarchy. A folder moved, renamed, or deleted from one surface is reflected in loaded branches of the other; the panel is not a separate copy of the library.

Folder rows provide a focused menu for routine management:

•

Rename changes the folder's visible name and its folder route name.

•

Info identifies the folder's name, type, and owning space-area location. This is useful when similarly named folders sit under different activities.

•

Delete removes the folder and its contents from the visible library, so inspect the location and descendants before choosing it.

The Engineering row exposes Rename, Info, and Delete in the same tree that shows its Architecture child, while the library remains unchanged.

On desktop, a permitted folder can be dragged by its row. On touch layouts that show the tree, use the dedicated drag handle to move it; a long press remains available for opening the folder menu. These controls are shown to the space owner and to members with space-management permission. The space-owner path is the dependable management path. A member who sees the controls through space-management access may still have an action refused; in that case, leave the content in place and ask the space owner to complete the change.

Rename Without Changing The Kind Of Item

For eligible files and folders, Rename changes the title members see. Renaming a folder also updates the readable route name used while browsing it. Renaming an uploaded file changes its displayed title, but it does not turn the file into an article or replace the underlying uploaded asset.

Use names that remain meaningful outside the current view. A label such as Final can become ambiguous after a move, while Launch brief - approved carries enough context to survive reorganization. For file behavior beyond organization, see Files And Previews.

Understand Delete Before Using It In Bulk

Delete currently differs between the single-item and multi-item menus:

•

A folder, article, or supported app document can show Delete in its individual card menu.

•

A raw uploaded file does not show Delete in its individual card menu.

•

A multi-item selection offers Delete for the selected set, and that set can include raw uploaded files.

This means the available action depends on both the item type and whether it belongs to a multi-item selection. Before bulk deletion, review every highlighted card—especially when files, app documents, and folders are mixed. Deleting a folder also affects its descendants, not only the folder card visible in the current grid.

There is no completed-move or completed-delete undo described by these controls. If your aim is organization rather than removal, prefer Move, confirm the destination, and delete only when the content is genuinely no longer needed.

Check The Result Of Larger Changes

Bulk moves and deletions are completed item by item. If a larger operation stops partway, items completed before the failure stay moved or deleted, while items that were not completed remain or return to the source view. A failure therefore does not guarantee that the whole selected set stayed unchanged.

After any substantial batch:

•

Recheck the source - Note which items remain and whether the original folder still contains the expected descendants.

•

Open the destination - Confirm the moved items arrived and that a moved folder kept its internal structure.

•

Check access after cross-area moves - Make sure the destination's participants match the intended audience.

•

Retry only the remainder - Rebuild a selection from the items that did not complete instead of repeating the original full batch.

This source-and-destination check is the safest way to avoid duplicates in your mental checklist or accidental repeated deletion attempts. For a complete practical flow, follow Organize Documents And Folders.

Common Questions

Who can move or rename documents and manage panel folders?

The interface shows these controls to the space owner and members with space-management permission. The owner path is consistently supported. If a permitted manager sees a control but the change is refused, the space owner should complete it.

Why did dragging one card move several items?

The card was part of an active selection, so the selected set became the drag payload. Drag an unselected card when you want to carry only that card, or clear and rebuild the selection first.

Why did some selected items stay in the original location?

An item already in the destination does not need to move, and invalid items are skipped. A batch can also stop after some changes have completed. Compare the source and destination before retrying anything.

Can I move a folder into one of its own subfolders?

No. Documents blocks moves that would place a folder inside itself or one of its descendants because they would create an unusable loop.

Does moving a folder remove its nested structure?

No. The folder and its descendants move together, preserving their organization beneath that folder.

Does moving a document change who can open it?

A move between folders under the same space area does not introduce a new access boundary. A move to another subspace or activity adopts that destination area's inherited access, so the practical audience can change.

Why can I bulk-delete an uploaded file when its own menu has no Delete action?

That is the current difference between the menus. Raw files omit single-card Delete, but a multi-item selection can include them in its bulk Delete action.

Does Escape reverse a completed move?

No. Escape cancels an active drag before the move commits. It does not undo a move that has already finished.

Related Guidance

Start with Documents for the complete module overview or The Documents Library And Folders for the location model. Use Organize Documents And Folders for an end-to-end cleanup workflow. When the goal is to bring selected material into a conversation instead of moving it, follow Share Documents In Chat.