Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.holace.io/llms.txt

Use this file to discover all available pages before exploring further.

Tags are free-form labels you can attach to any document in a journey. They’re a complement to folders — folders give you the what kind of document axis, tags give you any other axis you want to slice on (provider, body part, case theme, urgency, exhibit number). Tagging launched in WEB-115 and is the recommended way to handle anything you’d previously have done with sub-folders or naming conventions in a Dropbox setup. [Screenshot: Document preview modal with the tag chip section visible, showing several tags and an input for adding more]

​
Adding a tag

  1. Click any document to open the Preview Modal.
  2. In the Tags section at the top of the modal, click into the input field.
  3. Start typing a tag name.
  4. Autocomplete suggests matching tags already used elsewhere on this journey.
  5. Click a suggestion or press Enter to add a brand-new tag.
Tags appear as chips next to the document. Click the × on any chip to remove it.

​
Tag autocomplete

The autocomplete is journey-scoped — it suggests tags that already exist somewhere on this journey’s documents. This nudges your team toward consistent tag vocabulary inside a case (everyone uses imaging rather than half the team using imaging and half using xray). If you start a tag that has no match, autocomplete shows nothing and Enter creates a new tag for the journey.

​
Filtering by tag

The Documents tab has a tag filter bar above the folder list. Click any tag to scope the view to documents carrying that tag — across all folders. Click again to clear. Useful patterns:
  • Tag every document related to a specific provider with the provider’s last name (smith-md). Filter to see everything Dr. Smith touched.
  • Tag exhibits with exhibit-3, exhibit-12, etc., for trial prep.
  • Tag urgent items with urgent to make a fast triage list.
  • Tag everything tied to a specific theory of liability (spoliation, negligence-per-se) for brief-writing.

​
Folder override tags

A special tag form, folder:N (where N is 0–10), explicitly forces a document into a specific folder regardless of its document type. Use this when the auto-assignment lands somewhere you don’t want — for example, an “OTHER”-type document that’s actually a court filing should be tagged folder:8 to land in Litigation. You’ll rarely need this. It’s there for the rare edge case where the type taxonomy doesn’t fit.

​
Bulk tag edits

Select multiple documents in the document list (shift-click to multi-select), then click Tag selection. The tags you add are applied to every selected document in one action. The tags you remove are removed from every selected document. Bulk-untag works the same way.

​
What tags don’t do

  • Tags don’t move documents between folders. Folders come from document type (or folder:N override), not tags.
  • Tags don’t sync with case-level tags or contact-level tags. Document tags are scoped to documents.
  • Tags aren’t shared across journeys. A tag on one journey doesn’t autocomplete on a different journey.
This was rolled out in WEB-115 and replaces older sub-folder workflows for cross-cutting organization. If you’re moving from a Dropbox-style nested folder setup, lean on tags for any axis other than “type of document.”