Mentions
Two kinds of "mentions" live in the editor: people mentions (@name) that notify teammates, and entity mentions — typed references to workspace objects that stay live and clickable.
People mentions
Type
@in the editor to mention a member, team, or agent.The picker filters valid handles as you type.
Mentioned people get notified (per their notification settings) — the standard way to pull someone into a doc review.
Entity mentions
An entity mention is an inline chip that references a workspace object and links to it:
Type | Chip label |
|---|---|
Task | Task |
Epic | Epic |
Deal | Deal |
Contact | Contact |
Company | Company |
Conversation | Conversation |
Doc | Doc |
Typing one
Type @ followed by a type word to scope the search — for example @deal Acme lists matching deals, @task checkout lists matching tasks. Aliases like @tasks, @companies, @support, @docs all work. Then pick the record; the mention renders as a chip (with the entity's icon) and resolves to a live link.
Click behavior
Clicking a mention opens the object — the task, epic, CRM record, or support conversation. If the object was deleted or you lack access, the chip renders in a muted state with a tooltip instead of a broken link.
Mentions vs embeds
Mention = compact inline reference; use inside sentences.
Embed (entity card) = a block with more metadata; use when the object deserves space. Both follow the same access rules, so what a reader can see is consistent.
Why this beats plain links
Entity mentions point at the object itself rather than a URL, so they survive renames and moves, render correctly for every reader with access, and degrade gracefully for readers without access.
Was this article helpful?