Contact
Sequence

Comments

Threaded comments per row and per sheet, mentions, resolve and reopen, and why a deleted comment leaves a tombstone rather than disappearing.

Comments are threaded, per row and as a sheet-level conversation. Both are first-class: a sheet-level thread is not a row comment with the row left blank.

Row comments live in that row's detail panel, beside the row they are about. The Comments panel holds the sheet-level conversation.

Threads#

A comment either starts a thread or replies to one. A thread can be resolved and reopened, and resolved threads are retained rather than hidden away — the argument about a row is usually worth more later than it was at the time.

Reactions are per comment, per person.

Mentions#

Typing @ mentions somebody. A mention notifies regardless of subscription settings — see Notifications for exactly how far that bypass goes, and where it stops.

⚠ Mentions work by typing; there is no picker yet.

Editing and deleting#

You may edit and delete your own comments.

⚠⚠ A deleted comment leaves a tombstone. The body goes; the record that it existed stays. The thread keeps its shape, replies do not silently re-parent, and the activity log can say that a comment was deleted and by whom.

A delete that erased the row from the log would let somebody remove their own words from an audit, which is the one thing an audit is for.

Comments survive a row moving#

A comment names a row, and row identity is stable through reorder, indent, sort, move between sheets, import and export. Nothing about a comment stores a position, so there is nothing to update when a row moves — the comment simply goes with it.

Authorship#

⚠ The author is a declared name, worth exactly what the identity behind it is worth. See History, which states the same caveat about the same underlying fact.

Where comments are kept#

Comments travel in the schedule file. A build older than the version that introduced them would open the file happily, ignore the comments and drop every one on the next save — which is why that change was a schema version bump rather than a quiet addition.