← Help center · Sheets & views

Comments and mentions

Updated Oct 30, 2026

Records and pages both take comments. A record has one thread at the bottom; on a page, you comment on a passage of the text.

A record open with its comment thread
A record open with its comment thread

Mention someone with @

Type @ and start typing a name. They get a Mentions notification with a link straight to the record or the page.

A mention is the difference between a note and a request. If you need something from a specific person, mention them — nobody is watching every record.

Mention an agent

On a record, type @ and pick Dana or a custom agent to ask about the record. The agent reads the record and the recent comments, then replies in the record's comment thread. Up to two agents reply to one comment. Agents don't answer in page comments. See Agents in chat: mentions and hand-offs.

Comment on a page

Select text on the page and choose Add comment in the toolbar that appears. The thread stays on that passage.

A page with a comment thread on a highlighted passage and the Comments panel open, showing the Open and Resolved tabs
A page with a comment thread on a highlighted passage and the Comments panel open, showing the Open and Resolved tabs
  • Reply and react in the thread, and @mention a teammate. The @ list shows every member of your workspace, but only people who can open the page get the notification.
  • Resolve a thread when the text reflects the decision; Re-open it if the question comes back.
  • The Comments button in the page header shows how many threads are open. Its Open and Resolved tabs list threads in page order.
  • You can edit or delete your own comments. People who can edit the page can delete any comment.

Page history

Open History in the page header to see earlier versions of the page.

  • Versions are saved automatically while you edit. Choose Save version to save one yourself, with an optional name such as "Signed off by the client, 14 Oct".
  • Open a version to read it; it is read-only, and Back to current returns you to the page.
  • Restore puts an earlier version back. The current content is saved first as a Before restore version, so nothing is lost.
  • Named and Before restore versions are kept. Automatic versions are all kept for 7 days, then thinned to one per day until 30 days, then one per week.
  • Anyone who can view the page can open History. Saving and restoring need edit access.

Why comment instead of message

A chat message about a project is findable for about a day. A comment on the record or the page is still there in six months, next to the thing it is about, for whoever picks it up. When someone asks "why did we change this?", the answer is where they are already looking.

Use comments for anything that explains a decision, records an approval, or asks a question about a specific record or passage.

Good practice

  • Say what you need and from whom. "@Priya can you confirm the colour ramp before Friday?" beats "thoughts?".
  • Decisions belong in a comment, not only in a meeting.
  • Attach the file to the record, not to a message thread.

Notifications

Mentions are their own notification category, so people can keep them on while muting noisier ones. Replies to page threads you have commented in arrive under Page comments. If someone is missing mentions, check Profile → Settings → Notifications.

What everyone can see

Comments follow access. Anyone who can see a record can read its comments, and anyone with access to a page, view-only included, can read and add page comments — so they are the right place for team discussion, and the wrong place for anything private. Guests and portal customers don't see page comments.

Related: The item peek: open a record · Notifications aren't arriving · Agents in chat: mentions and hand-offs · How to review a client brief and keep the signed-off version

Related articles

Google Drive and Dropbox
Add Google Drive and Dropbox files to File List fields, comments and pages, and give clients a copy on the portal. What works where, and the limits.
See where a row came from
Add the Source field to an Atwork sheet to see which form, agent, workflow, API key or import created each row, then filter and group by it.
Archive and restore rows
Archive rows in Atwork to hide them from views, counts, charts and search without deleting anything, then show or unarchive them again at any time.