Threads

Threads keep team comments on the record they concern — transactions, invoices, bills, journal entries, vendors, or customers — with Pending review / Reviewed status so close questions do not get lost in email.

Key capabilities

• Comment threads on transactions, journal entries, invoices, bills, vendors, and customers
• One thread per object, created automatically the first time someone comments
• A review workflow — each thread is Pending review (shown as Pending on the row) or Reviewed
• Posting a new comment auto-resurfaces the thread back to Pending review, so addressed items don't go stale silently
• A centralized Threads page with a split list / detail layout
• Filter by object type and status; the page title shows how many threads match
• Cross-business view for advisors: with no business selected you see threads across every client business you can access
• Delete your own comments (after a confirmation)
• Each list row shows object type, status, business, author, comment count, latest-comment preview, and last-updated time
• AI thread summary — a recap with key decisions and action items
• One-click View to jump to the underlying record
• The list loads more threads as you scroll, with a Load more button as a fallback

How it works

Any object can carry a thread. The first comment creates the thread (and sets it to Pending review); each later comment appends and resurfaces it; an advisor marks it Reviewed once the question is settled.

flowchart TD
  obj["Object (transaction / invoice / bill / journal entry / vendor / customer)"] --> first["First comment"]
  first --> thread["Thread created (Pending review)"]
  thread --> more["More comments appended"]
  more --> review{"Advisor reviews"}
  review -->|"Mark reviewed"| reviewed["Reviewed"]
  reviewed -->|"new comment"| thread
  thread --> nav["View record / Summarize"]

How to use it

1. Open Threads from the sidebar (under Communication). To start a thread, comment on a record: use the Comments column on a row in Transactions, or the comments on a journal entry's detail view. Invoice, bill, vendor, and customer screens have no comment box yet, so threads on those records are not started from the app; any that exist appear here the same way.
2. Use the All types and All statuses filters in the toolbar to narrow the list (e.g. only Bills that are Pending review). Click the refresh icon to reload.
3. Click a thread to open it — the detail panel shows the full comment history with author names and timestamps.
4. Type in the composer and press Enter to post (Shift+Enter for a newline). Comments are limited to 10,000 characters.
5. Click Mark reviewed when the question is settled, or Reopen to send a Reviewed thread back to Pending review.
6. Click View with the record type (e.g. "View Transaction") to open the underlying record in context.
7. Click Summarize on a thread in the list to get an AI recap with key decisions and action items.
8. Use the trash icon next to your own comment to delete it, then confirm.

Pro tips

• Use threads for month-end review questions — the context stays permanently with the record, which is gold during close and audits.
• Lean on the Pending review filter as an advisor worklist: clear questions, mark Reviewed, and let new client comments automatically resurface anything that needs another pass.
• In the cross-business view, filter by object type to batch similar questions (e.g. review every Bill thread at once).
• Run Summarize on long threads before replying so you're not re-reading the whole history.
• Document why a categorization decision was made in a comment — it becomes a durable rationale on the exact record.

In-depth guide

Object types and where View sends you

The first comment on an object creates its thread automatically, so you never create threads explicitly. Commenting on any other object type isn't supported.

Status workflow

Marking a thread Reviewed is reversible with Reopen. Any new comment on a Reviewed thread flips it back to Pending review so resolved items resurface when there's fresh activity.

Permissions and advisor listing

Reading and commenting require access to the business the thread belongs to. Marking threads Reviewed or Reopening them requires write permission, so read-only roles can read and comment but cannot change status. Only the author of a comment (or a platform administrator) can delete it.

The Threads page runs in two modes: scoped to one business, or across every business you can access (typical for advisory firms). There's exactly one thread per object, so commenting again always appends to the same thread.

AI assistance

Summarize returns a concise recap plus extracted key decisions and action items. It is on-demand, and nothing is posted for you. Comment text must be 1 to 10,000 characters. Deleting a comment removes it for everyone, so add a follow-up comment instead when you want to keep the record intact.