Skip to content

Folders

Folders are where threads live. Every thread has exactly one home folder, and folders nest to form a hierarchy. As the empty state puts it: “Folders help you organize threads into meaningful groups. Create a folder to start curating your workspace and make bulk operations easier.”

Folders are single-home organization. For additive, cross-cutting grouping — where one thread belongs to several groups at once — use Categories instead.

Open Folders in the sidebar. The page has two parts:

  • A Folders panel with the tree. It is split into Our folders (owned by your team) and Shared with us (folders other teams shared with your team). Expand and collapse branches, or type in Search folders… to filter. Shared folders are badged with your access: “Shared with you — you can edit” or “Shared with you — view only”; folders you have shared out show “Shared with others”.
  • The selected folder’s contents: a thread count, the list of threads inside, and a Create Thread button that creates a new thread directly into this folder.

Breadcrumbs above the contents show the selected folder’s full path; on long paths, click Show full path to expand the collapsed middle. On small screens the tree is behind a Select Folder button that opens a Browse Folders sheet.

The Folders page with the folder tree on the left and the selected folder's threads on the right
The Folders page: the tree on the left, the selected folder's threads on the right.
  1. Click New Folder in the Folders panel to open the Create a Folder dialog (“Create a top-level folder to organize your threads.”). Enter a name — “Use a short, specific name so the folder is easy to scan later” — and click Create.

  2. To nest, open a folder’s actions menu in the tree and choose Add Sub-Folder. The dialog becomes Create a Sub-Folder and confirms the location: “Create a folder inside path.”

You can also create folders inline from any destination folder picker (New Folder / New Subfolder), for example while creating a thread. “Top-level folders are created in your active team’s workspace.”

Each folder in the tree has an actions menu:

  • Share and Access — share the folder with other teams and review who has access; see Sharing and Access.
  • Rename — “Update the folder name everywhere it appears in your workspace.”
  • Add Sub-Folder
  • Move to Folder and Move to Root (below)
  • Delete — the Delete Folder dialog warns “This action cannot be undone.” and clarifies “This will permanently delete the folder. Threads inside will not be deleted.”

Choose Move to Folder to open the Move to folder dialog and “Choose a destination” for the folder. The dialog:

  • Scopes the tree to Our team folders or, for folders owned by a connected team, Connected team folders — “A folder owned by a connected team can only be re-parented within that same team’s folders.”
  • Marks the Current folder and summarizes eligibility, e.g. “3 of 8 folders can accept this folder.”
  • Moves on Move here; a “Folder moved” confirmation appears.

Move to Root lifts a folder to the top level. If your only access to that folder comes through the shared parent you are removing it from, DICE warns you first:

  • You’ll lose access — moving it out of the shared folder means “you’ll lose access to it completely.” Confirm with Move and lose access, or Cancel.
  • You’ll lose edit access — your access would drop “from edit to view-only.” Confirm with Move and switch to view.
  • Otherwise the dialog is a simple Move to root? confirmation.
  • Create in place — the Create Thread button inside a folder, or choosing that folder in the Folder picker when creating a thread.
  • Move existing threads — select one or more threads and choose Move to Folder. The Move to folder dialog works like the folder move: pick a scope, see how many folders “can accept” the selection, and click Move here. If some of the selected threads already live in the destination, DICE notes “Some selected threads already live here; the rest will join them.”

A few rules the dialog enforces:

  • Threads can only land in folders owned by the same team that owns the threads. A mixed selection shows “Selected threads span multiple teams” — move them in batches grouped by owner.
  • In folder pickers, hover hints explain eligibility: “You can edit — items can be moved here”, “View only — items can’t be moved here”, and “Shared with other teams — items moved here are visible to them”.

DICE remembers the folder you last worked in — per user, per organization and team — and uses it as the default destination everywhere a folder picker appears (creating a thread, importing, slicing, moving). The remembered folder shows a Last used badge in pickers.

The working folder updates when you browse a folder on the Folders page or complete a destination action — creating a thread, committing an import, creating a slice, or finishing a move. It is only a default: DICE re-checks that the folder is still available and editable before pre-filling it, and you can always pick a different destination.