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.

Every Journey has one chronological Notes / Activity feed that captures both what your team says and what the system does. It’s the audit trail and the team chat in one place — you don’t have to ask “did anyone leave a note about this?” because every relevant event is here. [Screenshot: Notes / Activity tab with a comment composer on top, threaded comments below, and the system-event timeline beneath]

​
Two streams, one tab

The tab combines two underlying streams:

Team comments

Free-text notes your team writes for each other — “Spoke with adjuster, says payment by Friday,” “Client called re: PT progress.” Threaded replies, edits, and @mentions are all here.

System activity

Auto-generated events — Stage transitions, Step completions, document uploads, demand sends, negotiation moves, ownership changes. Read-only.
Both streams appear in chronological order. A filter toggle lets you show All, Comments only, or System only — useful when you’re scanning a long history.

​
Adding a comment

The composer at the top of the tab supports:
  • Plain text with line breaks
  • @mentions — type @ and pick a teammate; they’ll get a notification
  • Markdown shortcuts for bold, italic, lists, links
  • Replies — click “Reply” on any comment to nest your response
Comments are not the place for sensitive client communication. They’re internal team notes. The Communications feature (coming soon) will be the place for adjuster emails, client texts, and call logs.

​
Editing and deleting

You can edit or delete your own comments from the ⋯ menu on each comment. Edits show an “(edited)” marker; deletions leave a tombstone (“Comment deleted by Jane Doe at 3:42pm”) so the audit trail isn’t broken. Firm admins can delete anyone’s comment but with a permanent log of who removed it and when.
System-generated activity events are not editable or deletable by anyone — including firm admins. They’re the immutable history of what happened on the case.

​
What system events look like

Every important automatic moment becomes a one-line entry:
  • 🔄 Stage advanced from “Treatment” to “Records Collection” by Auto-Advancement at 10:14 AM
  • ✅ Step completed: “Records requested from St. Luke’s” by Maria P. at 9:47 AM
  • 📤 Document uploaded: medical-records-st-lukes.pdf (4.2 MB) by Maria P.
  • 💵 Negotiation move: First offer of $42,500 received from Allstate
  • 👥 Ownership changed: Reassigned from Tom B. to Sarah K. by firm admin
Hover any system event to see exact UTC timestamp and the related object (e.g., link to the document, link to the Stage detail). [Screenshot: A long activity feed mixing colored system events with team comment bubbles] The filter strip above the feed gives you:
  • All / Comments / System — the stream toggle
  • Date range — last 7 days / 30 days / custom
  • By user — show only entries from a specific teammate
  • Search — free text across comment bodies and event labels
These filters affect display only — nothing is deleted or hidden permanently.

​
Notifications

When you’re @mentioned in a comment, you get an in-app notification (and an email if you’ve enabled email notifications in your profile). When you reply to a thread, the original author and anyone else in the thread get notified. System events do not generate notifications by default — too noisy. Specific high-signal events (Stage transitions on cases you own, SOL warnings, demand replies) do fire dedicated notifications through the broader notification system.

​
Where to go next

Tasks

Where actions get assigned and tracked, separate from notes.

Documents

File uploads — referenced in the activity feed but managed here.