Comments, history & assigning people

Working on records together: the comment thread with @mentions, the per-record history of who changed what, watching, the People field for assigning teammates, and what a Contributor can and can't edit. Comment on any record Every row carries a speech-bubble at its right-hand end. It shows a number when the record has discussion, and turns accent-coloured when someone has @mentioned you there and you haven't read it yet — so you can see at a glance which rows are talking, and which are talking to you. Click it and the record opens straight on its Comments tab. You can also open a record any other way — click the row, press Space, or open the full record page — and pick Comments. The box at the top takes a comment; Ctrl+Enter posts it. Type @ to mention a teammate — pick them from the list and they're notified in their bell, and by email too if their notification settings say so (Settings → Notifications, Mentions). The same thread appears in the peek drawer, on the full record page and in the table panel; it is one conversation wherever you open it. Commenting automatically starts watching the record, so replies come back to you. Everyone in the workspace can comment — including read-only Viewers, whose seats are free: commenting is how a stakeholder weighs in without edit rights. You can delete your own comments; admins can delete anyone's. These threads are internal — on tables connected to email or the chat widget, the customer conversation is a separate thread and nothing here is ever shown to a customer. Ask a question about a whole table Some questions aren't about one row — "where are all the US orders?", "should this table have a region field?". Those go in the table's own thread: press Discussion in the toolbar above the grid. It works exactly like a record comment, @mentions included, and the button shows how many messages the thread holds. A table thread belongs to the table, not to the view you happen to be looking through — so everyone finds the same conversation whether they're on the grid, the board or the calendar, and a thread can never end up stranded on a personal view only its owner can see. Mentioning someone links them straight back to the table with the discussion open. Read the record's history The same Activity tab is the record's memory: who created it, every edit with the field name and the old → new values, moves to and from the Trash, posting and unposting, approvals — and the comments, woven in between. Linked records and people show by name, not by id, and edits made by an automation or through the API say so. History respects field permissions: a field hidden from you stays hidden in history too. Assign people with a People field Add a People field (Fields → add a field → People) to put teammates on records — an assignee on tasks, an owner on deals. Its cells open a member picker; assigned people show as avatar chips, and being assigned notifies the person in their bell. Only actual members of the workspace can be assigned. People fields group boards, filter (has a person, is empty), and appear in history and notifications by name. One shared view, everyone’s own list Filter a People field by @me and the view answers per person who opens it. One saved view called Assigned to me serves the whole team — there is no need for a view each, and somebody who joins next month gets theirs by existing. Assigning somebody now starts them watching the record as well, so the next comment reaches them without anyone remembering to arrange it. And if the person you want isn't in the workspace yet, you can invite them from the mention or the People field itself — as a Viewer only, because an invitation sent mid-sentence shouldn't be able to hand out edit rights by accident. Everything waiting on you My Work gathers what is assigned to you, what you are watching, what is waiting on your approval and your watchpoints — across every workspace you belong to, not just the one you are in. It is the answer to “what do I owe anyone?” without opening eight tables to find out. What a Contributor can edit The Contributor role reads everything and creates records — and can edit and delete the records they created, nobody else's. It's the right role for someone logging their own work in a shared table without being able to reshape everyone else's rows. Field-level read-only and hidden overrides still apply to their own records; an Editor or Admin can edit anything their permissions allow.