Skip to main content
Version: 13 - TBD

Record Comments

Record comments are a threaded discussion trail attached to a record. They are the place to leave feedback, ask a question, record a decision, or flag that a record needs another look — the human conversation about a record, kept alongside the record itself instead of in a separate tool.

Every record type carries comments: flows, executions, connectors, custom objects, bundles, and so on.

Reading and writing comments​

Open a record and select its Comments tab to see the full thread and add a new comment. Each comment shows its author and the time it was written, and the thread is ordered oldest-first so it reads like a conversation.

A comment can:

  • reply to an earlier comment, forming a sub-thread;
  • be assigned to a user, turning it into a lightweight request directed at that person;
  • be resolved, marking a question or request as dealt with.

The comment indicator​

Wherever a record's name is shown as a link, a small indicator next to the name carries the number of comments on that record. It appears across the Console — resource and execution lists, search results, dashboard record-table widgets, subrecord tables, "used by" lists, and object-template canvas nodes — so you can tell at a glance which records carry a discussion before opening them, the same way the provisioning-state dot signals a custom object's state.

A record with no comments shows no indicator, so uncommented records stay visually quiet and only records that carry a conversation stand out.

A record's comment thread is part of its full-text search document: a record matches when your words appear in any comment attached to it, not only in the record's own fields. The indexed text stays in sync as comments are added, edited, or removed.

Comments for flows and agents​

When a flow or an MCP agent reads a record, that record's most recent comments are folded into the result, so automated logic can see human feedback on a record without a separate lookup.