Doc folders

Who can use it: firm staff create folders and move docs. Clients see the folders read-only.

As a project grows, the custom docs pile up. Folders keep them tidy.

Use case

By month three the Harbor project has twelve custom docs. Ravi creates a Payments folder and moves Payment Provider Notes and Refund Rules into it. Then Arjun exports just that folder to give his coding assistant the payment background, without the rest of the project.

• DirectoryBusiness (system folder)

  • Business Problem
  • Personas
  • …
• DirectoryTechnical (system folder)

  • Architecture
  • Tech Stack
  • …
• DirectoryPayments (your folder)

  • Payment Provider Notes
  • Refund Rules
• DirectoryStore Operations (your folder)

  • Delivery Slots

How folders work

• Every project has two system folders, Business and Technical. Each doc starts in the system folder of its group.
• You can add your own folders. There’s one level only, with no sub-folders.
• You can move custom docs between folders. The eight built-in docs stay in their system folders.

Create a folder

1. Open the project and go to Docs.
2. Add a folder and name it (up to 80 characters, unique in the project).

Move a doc

Move a custom doc into a folder, or back to its system folder. Moving doesn’t change the doc’s content, version or sign-off, and doesn’t interrupt anyone who’s editing it.

Export a folder

Export one folder as Markdown instead of the whole project.

Good to know

• A Business doc can never end up in the Technical system folder, or the other way round.
• You can’t delete a folder that still holds docs, archived ones included. Move them out first.
• Archiving a doc keeps its folder, so restoring it puts it back where it was.