Flow: mentions
A mention is a way to bring a colleague into a task: type @ and a name, pick the person from the list, and they get a notification. You can mention people in a task's description and in its comments. This article explains where @ works, who you can mention, what the mentioned person gets and how to turn these notifications off.
Where @ works
Where | What the mention looks like | What the mentioned person gets |
|---|---|---|
Description and other "Text" fields in the card and in the creation form | A chip with the name in the editor; after saving, the name as a link | A "You were mentioned" notification from the "Sensever Flow" bot |
Object comments (the private discussion in the card) | The name as a link in the comment | The comment in their own chat, like a mention in a regular chat |
Text fields use the same editor as chat messages. A mention in it is indivisible: you can delete it as a whole, but you can't "break" it by editing the text around it.
In tables and in the change history, a mention is shown as @Name. In CSV exports and in the API it's stored as [@Name](principal:…) markup and isn't lost when you import it back. Editing text right in a table cell is a plain field without people search; to mention someone, open the card.
Who you can mention
The list after @ shows only people who can see this object:
active workspace members — people, not API keys or bots;
who currently have permission to open the object (taking into account who its assignee and author are);
excluding yourself.
The list shows up to 8 people matching the letters you've typed, each with a photo or initials. If the person you need isn't there, they most likely can't see the object: give them access first (a role or a team).
In the object creation form there is no assignee yet, so the list is wider: it includes everyone who can read objects of this type. Still, only those who will see the created object get the notification.
Mentions in the description
Open the task card or the creation form and start typing in the "Description" field (or another "Text" field).
Type
@and the first letters of a name, then pick the person from the list.Save the object.
After saving, the mentioned person gets a "You were mentioned" message in the "Sensever Flow" conversation with the text "<author> mentions you in the object text." and the object name as a link. The text arrives in the recipient's interface language. The description itself isn't in the notification: the text is visible only when the person opens the card.
The rules:
Only new mentions trigger notifications. If a person was already mentioned in this field, editing the text around it won't notify them again. If you delete the mention and add it again, they get a notification.
The author doesn't get notified about themselves — you aren't in the list anyway.
Anyone who can't see the object won't get a notification, even if their name is in the text: permissions are checked at the moment of sending.
No more than 20 people are notified per save.
Mentions notify only about edits by people (and API keys). Automations, processes, copying the description into the next recurring task, and imports without automations don't send mention notifications.
The notification follows your personal workspace settings: the "Mentions" category, channels and quiet hours — see below.
Mentions in comments
Task comments are a private discussion in Sensever chat built into the card (the "Comments" block). @ search there works the same as in the description and shows the same people — those who can see the object.
Anyone who can post in the discussion can mention people in comments: they have permission to edit the object, and the object isn't archived.
Before the comment is sent, the mentioned people join the discussion, even if they've never posted there. They can see the whole comment history, but old comments don't become unread for them.
The mentioned person gets the comment in their own chat, like a mention in a regular chat: with an unread counter and a push according to their chat settings. There's no "You were mentioned" notification from the "Sensever Flow" bot for a comment — the message itself arrives.
If a person loses access to the object, they also leave the discussion, like any member.
Someone who has never signed in to Sensever chat can't be added to the discussion — their name stays in the comment as plain text.
Public comments on external sites have no
@search: visitors shouldn't see your staff.
To open the whole discussion, click "Open in chat" in the header of the "Comments" block.
Who doesn't get a notification
Who | Why |
|---|---|
The author of the mention | Flow doesn't notify you about your own actions |
A person who can't see the object | They aren't in the list; if their name is typed into the text, no notification is sent |
A member disabled in the workspace | Disabled members don't get notifications |
Someone who turned off the "Mentions" category or all workspace notifications | Personal settings |
A person mentioned in text copied by a rule, a process or a task recurrence | Only edits by people trigger notifications |
How to turn them off
"You were mentioned" notifications are set up separately in each workspace: workspace settings → "Notifications" tab.
"What to send" → "Mentions" checkbox ("you were named with @ in a task description"). It's on by default. Turn it off and mentions in descriptions in this workspace stop arriving.
"How to send" → "Email" → "Mentions" — a copy by email. By default, mentions don't come by email.
"Quiet hours" — during this time the notification arrives without a push.
"Don't send me notifications from this workspace" turns off mentions too.
Mentions in comments are chat messages, and Flow settings don't apply to them. Their sound and notifications are set up in Sensever chat itself, like any conversation.
What's next
Flow: notifications and reminders — personal settings, channels and quiet hours.
Flow: the object card — description, comments and history.
Flow: email and calendar subscription — mentions by email.
Flow: members, roles, teams and billing — how to give someone access to an object so they can be mentioned.
Flow API: personal lists, calendar and email — personal settings through the API.
コメント