Visual Space manual, Docs, Organize Documents And Folders

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

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 controls but still have an action refused because the current authorization checks do not fully agree. If that happens, leave the content where it is and ask the space owner to complete the change.

Before You Reorganize

A useful structure starts with the area that owns the work. Ordinary folders arrange documents beneath a space, subspace, or activity; they do not create a new audience or replace that community structure.

•

Open the source area - Go to Documents in the space, subspace, or activity you want to tidy. Confirm the area name in the header before selecting or moving anything.

•

Assess the visible collection - Look for repeated subjects, project phases, or file types that members already search for together. Open existing folders when necessary so you understand their direct contents and do not recreate a structure that already exists deeper in the library.

•

Identify the intended audience - Note whether sensitive material belongs at the space level or inside a more restricted subspace or activity. Moving across those areas changes inherited access even when the move remains inside the same space.

•

Choose a small folder plan - Prefer a few durable names such as Research, Approved assets, or Meeting notes over many one-item folders. Use activities for working context and folders for organization inside that context.

•

Confirm management access - Move, rename, and folder-management controls are shown to the space owner and members with space-management permission. If you are a manager rather than the owner, be prepared for the current authorization mismatch described above.

Checkpoint: you know which area is disorganized, which material belongs together, and whether any planned move crosses into a different access context.

Create The Destination Structure

Create the containers before building a large selection. This lets you check the names and nesting while no documents are armed for a bulk action.

•

Create the first folder - In the intended Documents area, open New and choose New folder. Give the folder a clear name that will still make sense when members encounter it from search or a shared link.

•

Add only useful levels - Open the new folder and create a nested folder only when the extra level represents a real distinction, such as Campaign / Approved and Campaign / Working files.

•

Return to the source - Navigate back to the disorganized location after the destination folders exist. On desktop, the side-panel tree and the document grid are two views of the same hierarchy, so either can help you confirm the new branch.

•

Inspect similar names - If two folders have nearly identical labels, use the folder menu's Info action in the side panel to confirm the owning space area. Rename ambiguous folders before moving a large set into them.

Creating a folder does not make its contents private. The folder and everything nested below it inherit access from the surrounding space, subspace, or activity.

Select Exactly What Should Move

Build the selection from the current visible collection. The highlight is your best preview of what a bulk Move or Delete action will affect.

•

Add individual cards - On desktop, hold Command on macOS or Control on other systems while selecting each document or folder. Use the same modifier on a highlighted card to remove it from the set.

•

Select a visible range - Select an anchor card, then hold Shift while selecting the last card in the range. Every visible card between the two becomes selected, so inspect the middle of the range as well as its ends.

•

Draw a selection rectangle - Start in empty grid space and drag across the cards you want. Adjust the selection if the rectangle overlaps an unrelated card.

•

Review mixed selections carefully - Check whether the set contains folders, raw uploaded files, articles, or other app documents. A selected folder represents its whole nested tree even though only the folder card is highlighted.

•

Open the selected-set menu - Open the action menu from a card that belongs to the multi-item selection. The compact menu applies Move or Delete to the complete highlighted set, not only to the card under the pointer.

Review the complete highlighted set before choosing Move or Delete; the menu applies to both cards.

Changing location or completing an action clears or prunes the selection. Rebuild it from the visible cards when you begin another batch instead of assuming an earlier hidden selection is still active.

Choose The Move Method

Use the method that matches the precision you need. Both methods preserve the document itself and, for a folder, the structure below it.

•

Use Move for an area root - Open the single-card or selected-set menu, choose Move, then select the space, a subspace, or an eligible activity. This is the direct route when the material belongs at that area's top level. Archived or draft activities are not offered as destinations.

•

Drag into a visible folder - Drag the item or selection onto a folder card when the exact folder is already in the grid. A valid target shows Move here before you release.

•

Use the desktop folder tree - Drag onto a visible side-panel folder when the destination is elsewhere in the current hierarchy. You can also hover over an eligible folder to open it, then finish the drop in the Documents area that appears.

•

Navigate across activities while dragging - Hover over another eligible activity to open its Documents context, then drop into its main area or an available folder. A folder-only drag can also be dropped directly onto an eligible activity row.

•

Cancel an uncertain drag - Press Escape while the drag is active if the payload is larger than expected or the wrong location opens. This cancels the active drag before it commits; it does not undo a move that has already finished.

The drag payload depends on the card where you start. Dragging a selected card carries the whole selected set. Dragging an unselected card carries only that card, even while other cards remain highlighted. Check the drag count or highlighted set before releasing.

Keep Folder Moves Valid

Documents rejects destinations that would damage the folder tree or fail to produce a meaningful location change.

•

Stay in the same space - Documents can move material among folders, subspaces, and activities of its current space. It does not use this workflow to move documents into another space.

•

Avoid the current parent - Dropping an item back into the folder or area that already contains it does not create a move. In a mixed batch, items already at the destination are skipped while eligible items can still move.

•

Keep a folder out of itself - Do not drop a folder onto its own card.

•

Protect the descendant tree - A folder cannot move into any folder nested beneath it. If a target does not respond, it may be part of the dragged folder's own subtree.

•

Stop after a blocked drop - Recheck the source, destination, and selection rather than repeatedly releasing onto a target that does not accept the drag. The target may be invalid, unavailable to you, or already the current parent.

When a folder moves successfully, all of its nested folders and documents stay together in the same arrangement. The move changes the parent of the folder; it does not flatten the tree or scatter its descendants.

Treat Cross-Area Moves As Access Changes

A move between ordinary folders under the same space area changes organization without creating a new access boundary. A move into another subspace or activity is more consequential because the destination area's rules become the inherited access for every moved item. Those inherited rules are part of space privacy across connected work.

•

Check the destination participants - Before moving sensitive material, confirm that the destination subspace or activity includes the people who should be able to open it.

•

Consider the whole folder tree - When moving a folder across areas, apply that access check to every descendant. The folder does not keep a separate privacy setting from its new area.

•

Complete the move - Use the area-root Move choice or drag into the intended activity or folder only after the audience is correct.

•

Verify from the destination - Open the target and confirm the items appear there. A stable document link can continue to find moved material, but it never bypasses membership or private-area access.

For a deeper explanation of this relationship, see The Documents Library And Folders.

Rename For The New Context

A move can expose vague names that made sense only in the old location. Rename eligible files or folders when the new context needs a clearer label.

•

Open the item menu - Choose Rename for the moved file or folder. In the desktop side panel, a folder row also provides Rename.

•

Use a durable name - Replace labels such as Final or Latest with a name that identifies the subject and state, such as Launch brief - approved.

•

Confirm the result - Check the title in the destination. Renaming an uploaded file changes the displayed title; it does not convert the file into another document type.

If a manager can see Rename but the change is refused, do not work around the refusal by duplicating the item. Ask the space owner to perform the rename.

Verify Every Larger Move

Bulk moves are completed item by item. If a later item fails, items already completed stay in the destination while the unfinished remainder stays or returns to the source view. Do not assume a reported failure means the whole batch was unchanged.

•

Reopen the source - Note which selected items remain. If a moved folder was part of the set, confirm that no unexpected sibling was included.

•

Inspect the destination - Check that each completed item appears once and that every moved folder retained its descendants and nesting.

•

Recheck access - For a cross-subspace or cross-activity move, confirm the practical audience still matches your intention.

•

Retry only the remainder - Select only the items that did not complete, then move that smaller set. Repeating the original batch can make the result harder to reason about.

•

Escalate a refused manager action - When the controls were visible but the move was denied, preserve the current locations and ask the space owner to finish the verified remainder.

Checkpoint: the source contains only the intended remainder, the destination contains the completed items, and members with the intended access can open them.

Use Delete Only For Deliberate Cleanup

Delete is optional cleanup, not part of a normal move. Use it only after the source and destination checks prove that the remaining content is genuinely unwanted.

•

Inspect folders before deletion - Deleting a folder affects its descendants, not only the visible folder card. Open it and check the nested material first.

•

Recognize the single-item difference - A folder, article, or supported app document can show Delete in its individual menu. A raw uploaded file does not currently show Delete in its own single-card menu.

•

Review a bulk deletion - A multi-item selection offers Delete for the selected set, and that selection can include raw uploaded files. Recheck every highlighted card before choosing it.

•

Expect partial outcomes - Bulk deletion is completed item by item. If the operation stops, items deleted before the failure remain deleted while unfinished items remain or return to view. Reinspect the location before attempting any cleanup again.

•

Do not rely on undo - These controls do not promise an undo for a completed move or deletion. Prefer Move when you are organizing rather than removing content.

If The Result Is Not What You Expected

•

Several items moved when you dragged one card - The starting card belonged to the active selection, so the selected set became the drag payload. Rebuild a smaller selection, or start from an unselected card when only one item should move.

•

The folder would not accept the drop - It may already be the item's parent, the dragged folder itself, or one of that folder's descendants. It may also belong to another space or be unavailable to your account.

•

Some selected items stayed behind - Items already in the target are skipped, an invalid target can exclude items, and a later failure can stop a batch after earlier items completed. Compare both locations before retrying.

•

The destination has the wrong audience - Move the material back to the appropriate area if you can do so safely, then verify access again. If a management action is refused, ask the space owner to correct the placement.

•

Escape did not restore the old location - Escape cancels only an active drag. It is not an undo after the move has committed.

Finish With A Clear Library

The reorganized area should now have a small, recognizable folder structure, correctly named items, and no uncertainty about where a larger batch finished. Members should be able to browse the destination while the access inherited from its space, subspace, or activity matches the intended audience.

Return to Documents for the module overview or Organizing Documents for a full explanation of selection, moving, renaming, and deletion. To add source material without flattening its folder structure, continue with Upload Files And Folders. To bring selected documents into a conversation instead of moving them, use Share Documents In Chat.