Skip to main content

​
The bell

The bell in the top bar shows a dot when a new notification arrives. Opening it lists your notifications, newest first, and scrolling down loads earlier ones until the list reaches the first. Each unread notification has a dot, and closing the panel marks them all as read. Selecting a notification opens what it is about and closes the panel. A notification that has no page of its own, or whose page your role doesn’t open, is shown without a link. Preferences at the top of the panel opens the notification settings.

​
What you can be notified about

Notifications cover what happens around you:
  • A teammate accepted an invitation that you sent, joined or was removed.
  • Someone shared a dashboard with you.
  • Support replied to one of your tickets.
  • A teammate mentioned you in a response note.
  • A teammate published a survey.
  • A webhook failed several times in a row, or an integration stopped sending (only for people whose role manages integrations, workflows or developer settings).
  • Your organization used 80% or 100% of its monthly response limit, its extra responses are running low, or Usertick stopped collecting responses because the organization reached the limit or its extra responses ran out. The notices about stopped collection offer Buy extra responses to the people who manage billing.
  • Plan changes, failed payments and a canceled subscription. Every member sees these in the bell, and the emails go to the people who manage billing. When a plan change pauses, suspends or makes something read-only, or brings it back, the owner and the people who manage billing get one notice that lists it instead, and the other members get the short one. A failed payment names the date by which the card has to be updated, and Usertick sends it once for each unpaid invoice.
A notification about a survey reaches only the members whose role opens that survey. See Survey access. Each type can reach you on four separate channels: in the dashboard, by email, in Slack and in Microsoft Teams.

​
Choose your notifications

Notification preferences are under Settings → Preferences, in the Notifications group, with one row per channel: Each row has one selector: Under Recommended and Everything, View next to the selector opens the same list to read: its switches show what the setting sends, and they can’t be changed there. To choose types one by one, select Custom. Under Custom, Edit opens the list again. A channel that is Off has neither. Turning off a notification on one channel leaves it on for your other channels. Changes wait in the bar at the bottom of the page, which counts them: Save changes applies them and Discard drops them. Leaving the page with unsaved changes asks first. The email about a failed payment can’t be turned off, so its switch stays on and locked. It is sent only to the people who manage billing.

​
Browser notifications

Browser notifications, under the In-app notifications row, shows a desktop notification for each notification that arrives in the bell, while Usertick is open in a browser tab that you are not looking at. Selecting the desktop notification brings the tab forward and opens what the notification is about.
  • It follows the bell. It shows what the In-app notifications row sends, for the organization that is open in the tab. A type that is off in the bell is not shown on the desktop.
  • It needs an open tab. With every Usertick tab closed, nothing is shown. Email, Slack and Microsoft Teams reach you then.
  • Each browser has its own switch. The switch is stored in the browser and takes effect at once, without Save changes. Turn it on in every browser where you want desktop notifications.
  • The browser asks first. The first time, the browser asks whether Usertick may show notifications. When the browser blocks them, the row says so, and the switch stays off until you allow notifications for the site in the browser’s site settings.
The notification settings of your operating system, such as Do Not Disturb, apply to these notifications too.

​
Slack and Microsoft Teams

Slack and Microsoft Teams are the two tools that can message you directly. Every other integration writes records or events to a tool and sends no personal notifications. Both start Off for every type, and their defaults are off too, so Recommended sends nothing there. Each member turns them on for themselves. Until a tool can reach you, its row shows Connect in place of the selector and says what is missing. The Slack row reads as follows, and the Microsoft Teams row says the same about Teams: Connect asks the tool who holds the email address of your Usertick account, and links you to that user:
  • Slack: a user of the connected workspace whose email address Slack confirmed.
  • Microsoft Teams: a person in a team that has the Usertick app, who signs in with that address in one of your Microsoft 365 organization’s verified domains. Usertick then also knows where to message you in Teams.
When the tool has no such user, a dialog says how to link from the tool:

​
After connecting

The row shows its selector, set to Off. Set it to Everything, or to Custom to choose the types under Choose what Slack sends you or Choose what Microsoft Teams sends you. In Microsoft Teams, a linked account can still be out of the app’s reach. The row then says “Usertick cannot message you in Microsoft Teams yet. Add the Usertick app to a team you are in, or open your chat with it in Teams.”, and its selector is grayed out until the app can reach you. Each Slack or Teams message has the notification’s title, its text and an Open button. Usertick sends each notification email as the notification happens, one email per notification. The email names the organization it is about. Its Open button, like the one in a Slack or Teams message, opens the dashboard in that organization, also when you last worked in another one.

​
Mentions

Mentioning a teammate with @ in a response note notifies them in the dashboard and, with the default preferences, by email. Mentions are personal and time-sensitive, so their email default is on.