Being able to choose how and for what types of content you want to be notified for is important. It's also crucial to understand how you can direct your teammates' attention to some content. This page should help you understand how notifications work in CA Flowdock.
On your computer
CA Flowdock keeps a list of all of your highlighted messages in the notifications list at the top left corner of the screen. A yellow number badge indicates the number of unread items. You can mark messages as read individually or all at once.
Desktop notifications give you a preview of what's going on in CA Flowdock. Clicking on them will open the thread that caused the notification. If you're using CA Flowdock with a browser, you'll need to give CA Flowdock permission to show notifications.
You can adjust what you want to be notified for on the desktop from your Notifications preferences:
- All messages, including team inbox messages.
- All chat messages.
- Only 1-to-1 and messages with mentions.
- No messages.
Push notifications on your mobile device
Users of CA Flowdock's Android and iOS apps will get push notifications for @Username mentions and 1-to-1 messages. Note that @team or @everyone mentions don't trigger push notifications. iOS users should configure notifications using the system-level iOS notification settings, while Android users can configure them from the CA Flowdock app's preferences.
CA Flowdock only sends push notifications when it interprets that you are not actively using CA Flowdock on any other device.
Email notifications are a great way to be notified if you don't have the CA Flowdock app installed on your phone. Similarly to mobile push notifications, email notifications are sent for @Username mentions and 1-to-1 messages for users who have email notifications enabled. You can enable or disable them from your Notifications preferences.
Email notifications will only be sent if you are not actively using CA Flowdock. @team or @everyone mentions don't trigger push notifications.
Mentioning people by @Username
The most surefire way to get someone's attention is to mention their @Username. You can also add their @Username tag to any message in CA Flowdock, even if it was originally sent by someone else. The message will show up in the user's notifications list and will generate a desktop notification. If they're not on CA Flowdock at the time, a push or email notification will be sent (as long as the user has them turned on).
When you hover your cursor over a message with a @Username tag, you can see whether @Username has seen your message or not.
Directing your message at @team
When you want to direct the attention of a flow's core team to a message, using @team is your best bet. The users of a flow can decide whether they want to belong to @team on a flow by flow basis. Users will receive desktop notifications and the message will appear in their notifications list.
Note that @team will not send push or email notifications.
Notifying @everyone in a flow
@everyone and its synonyms, @all, @anyone and @anybody work similarly to @team, except they will notify all the people in a flow.
Use it sparingly – it's nearly always better to use @team. In a flow with more than 10 members, a cautionary message is shown:
Directing your message at a custom flow group
A flow administrator can create a custom group of users in a flow prefixed with @@, and followed by a group name.
To create a group navigate to the flow settings:
Select the “Groups” tab and click the “New Group” button
You will be prompted to create a name for the group. The group name must be unique, may contain letters and underscores, but may not contain special characters or spaces. Once the group is created it will appear in the list of groups for that flow. Click the “Add People” button to select the flow members to add to the group. (To remove an added member hover to the right of their name to expose the “Remove user” button).
When you return to the flow from the “Settings” the new custom group will be available. It will work similarly to @team. The main differences are that it is prefixed with @@ and that membership is managed from the group settings page.