> ## Documentation Index
> Fetch the complete documentation index at: https://docs.libratech.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Folder structure

> Organise Project files into folders: documents, Reviews and Discoveries, with drag-and-drop and nesting.

<video autoPlay muted loop playsInline src="https://mintcdn.com/libra-4206ec93/azhR9hqtFjs66ITC/assets/videos/features/documents-folder-structure.webm?fit=max&auto=format&n=azhR9hqtFjs66ITC&q=85&s=9fe496505ad7db31b36e088c47b98f4e" className="rounded-xl border w-full" data-path="assets/videos/features/documents-folder-structure.webm" />

Every project has a **Project files** panel that behaves like a file system you've used before: folders, subfolders, drag-and-drop. It holds everything a matter accumulates — the documents you upload, the files you attach in Chat, and your finished Reviews and Discoveries — so the whole artefact set can sit in one folder tree.

<div className="libra-buddy-callout">
  <img src="https://mintcdn.com/libra-4206ec93/wgVZXcGnHS4aJk9T/assets/images/libra-buddy/clipboard.png?fit=max&auto=format&n=wgVZXcGnHS4aJk9T&q=85&s=cde036cf23ea2d67cd50f1c295db549a" alt="Libra mascot with a clipboard" width="725" height="605" data-path="assets/images/libra-buddy/clipboard.png" />

  <div className="libra-buddy-callout-content">
    Dragging a folder from **Project files** into the message box attaches everything inside it — every document plus every completed Review and Discovery, subfolders included. Useful when the whole matter sits in one folder. (`@`-mentioning a folder attaches only the files sitting directly in it.)
  </div>
</div>

## Working in Project files

Three folders that Libra maintains sit pinned at the top of every project: **Reviews**, **Discoveries** and **Chat uploads**. You can't rename them, drag them, delete them, or put a folder inside them. **Reviews** and **Discoveries** take only their own kind of work product — drop a document on either and Libra refuses the move. **Chat uploads** is protected in the same way but holds ordinary documents, so files move in and out of it freely and it stays available wherever Libra asks you to pick documents.

Everything else nests the way you'd expect. Files, Reviews, Discoveries, and any folder you created can be dragged into any folder you created. Selecting the checkboxes next to several files — or holding <kbd>Shift</kbd> to take a whole range — lets you drag a batch at once.

Hovering a row reveals a **⋯** button. On a folder it offers **New Subfolder**, **Rename**, **Upload Files**, **Move to project** and **Delete Folder**, plus **Add from SharePoint** when SharePoint is connected. On a file: **Rename**, **Download**, **Move to project** and **Delete** — and, when several files are ticked, an extra entry that deletes the whole selection at once.

You create a folder with the **Create folder** button at the top of the panel. New folders land at the project root and can be dragged anywhere afterwards. Naming matters more than it looks like it does: *"Inbound documents"* and *"Drafts"* are clearer than *"Folder 1"* and *"Folder 2"* in three months when you've forgotten which version is which.

## Where Libra files things for you

When you start a Review or a Discovery, it is filed in the project's **Reviews** or **Discoveries** folder. Treat those two as landing zones rather than final homes — the item inside can be dragged into any folder you create, and the pattern that makes this feature pull its weight is to move it into the matter folder it describes. A folder called *"Schneider employment package"* holding *Schneider — employment contract.pdf*, the Schneider contract Review and *Schneider — counterproposal.docx* keeps the contract, the analysis and the negotiation drafts side by side.

A file you attach to a message in Chat is filed into **Chat uploads** and becomes a normal project document: you can preview it, move it into a folder of your own, attach it to another chat, and delete it. Attaching a file in Chat therefore adds it to the project, where everyone with access to the project can see it. The exception is view-only access — if you can only view the project, your chat attachment stays with that conversation and is never added to the project's shared files.

Email threads exported from the Outlook add-in land in a folder called **E-mails**. That one is an ordinary folder — it isn't protected the way the pinned folders are — but leave it named **E-mails** at the project root: the add-in files every export into a root-level folder by that name, and renaming or nesting it just makes the next export create a fresh one beside it.

<Warning>
  Deleting a folder permanently deletes every document inside it, including in its subfolders. Reviews and Discoveries are not deleted — they move back to the project's **Reviews** and **Discoveries** folders. Move documents out before you delete if you want to keep them.
</Warning>

## Moving files to another project

**Move to project** on the **⋯** menu re-homes a document, or a whole folder, into a different project. The submenu lists the projects you can edit — archived projects and ones you only have view access to aren't offered — and **New project** creates the destination on the spot. Libra asks you to confirm before the move goes through.

A folder move takes the entire subtree with it: every subfolder and every document inside. Any Review or Discovery caught in that subtree is filed into the destination project's **Reviews** or **Discoveries** folder rather than travelling inside your subfolder. A document you move on its own arrives at the top level of the destination project. A move is refused while any document in it is still being processed — wait for the upload to finish and try again — and a folder move is refused if the destination project already has a folder of the same name. Either way the item leaves this project, so anyone who can see the destination project can now see what you moved there — check the destination's access before moving anything sensitive.

<Note>
  The pinned **Reviews**, **Discoveries** and **Chat uploads** folders can't themselves be moved to another project. A document sitting in **Chat uploads** has its own **Move to project** — use that. A Review or Discovery doesn't: drag it into a folder you created and move that folder instead, and it arrives in the destination project's **Reviews** or **Discoveries** folder.
</Note>

## Common folder structures

There's no single right way to organise. The pinned folders always sort above whatever you create, so the patterns below show only your own folders:

<AccordionGroup>
  <Accordion title="By document type">
    ```
    Project/
    ├── Inbound documents/
    ├── Drafts/
    └── Signed versions/
    ```

    Best for transactional matters where the same kinds of documents flow through.
  </Accordion>

  <Accordion title="By matter phase">
    ```
    Project/
    ├── 01 — Initial documents/
    ├── 02 — Due diligence/
    ├── 03 — Negotiation/
    └── 04 — Closing/
    ```

    Best for long-running matters with distinct phases (M\&A, complex litigation).
  </Accordion>

  <Accordion title="By party">
    ```
    Project/
    ├── Acme Corp documents/
    ├── Counterparty documents/
    └── Joint documents/
    ```

    Best for negotiations where each party has a clear set of documents.
  </Accordion>

  <Accordion title="By topic, with Reviews and Discoveries inline">
    ```
    Project/
    ├── Employment contracts/
    │   ├── Schneider/
    │   │   ├── Schneider — employment contract.pdf
    │   │   ├── Schneider — contract Review
    │   │   └── Schneider — counterproposal.docx
    │   └── Hofmann/
    └── Service agreements/
    ```

    Best for high-volume matters where each topic has its own contract, Review and drafts.
  </Accordion>
</AccordionGroup>

<div className="libra-buddy-callout">
  <img src="https://mintcdn.com/libra-4206ec93/wgVZXcGnHS4aJk9T/assets/images/libra-buddy/celebrating.png?fit=max&auto=format&n=wgVZXcGnHS4aJk9T&q=85&s=f7fc1dceea53e00af4228bcfcdc9c0d5" alt="Libra mascot celebrating" width="626" height="630" data-path="assets/images/libra-buddy/celebrating.png" />

  <div className="libra-buddy-callout-content">
    Drag-and-drop is multi-select aware. Tick the checkboxes of several files — or <kbd>Shift</kbd>-click to take a range — then drag in one move. Beats 30 PDFs one at a time.
  </div>
</div>

## Tips

<AccordionGroup>
  <Accordion title="Set up the structure on day one">
    Decide on the folder structure when the project is created; it's much easier than reorganising 200 files later.
  </Accordion>

  <Accordion title="Don't let the pinned folders accumulate">
    **Reviews**, **Discoveries** and **Chat uploads** are fine as landing zones. Once you have more than five items in any of them, drag them out into folders of your own, organised by document type or matter phase — you can't create subfolders inside the pinned folders themselves.
  </Accordion>

  <Accordion title="Use folders consistently across projects">
    A consistent structure across projects makes it easier to find things. *"Inbound documents"* / *"Drafts"* / *"Signed versions"* in every M\&A project, for example.
  </Accordion>

  <Accordion title="Subfolders are your friend">
    Don't be afraid of nested folders. *"Inbound documents > Counterparty drafts > v1"* is more useful than 50 files in a flat *"Inbound documents"* folder.
  </Accordion>
</AccordionGroup>

## Next steps

<Columns cols={2}>
  <Card title="File types & previews" icon="file" href="/en/features/documents/file-types">
    Every supported format and what the preview looks like.
  </Card>

  <Card title="Project files" icon="folder" href="/en/features/documents/library">
    Back to the Project files overview.
  </Card>
</Columns>