Skip to main content
Besides the inbox and email, Collabase can send notifications as a direct message in Slack or Microsoft Teams, report events of a space or project to a channel, and show browser notifications. Chat and browser notifications are off for everyone until a person switches them on. Who can do this?

​
Connect Slack or Teams

Collabase uses the same connections as the automation steps Send Message and Send Direct Message.
1

Create the connection

Create a Slack connection (a bot token) or a Teams connection (tenant, client ID and client secret) under Automation → Connections. For Slack the bot needs the scopes to read a user by email address and to send direct messages.
2

Choose it for notifications

Go to Administration → Notifications. Under Chat workspaces, choose the connection for Slack or Teams. Collabase checks that the credentials work before it saves.
Choose Not connected to disconnect. Both changes are written to the audit log as Notification channel connected or disconnected; the entry names the provider and never a token. If the provider later refuses the credentials, Collabase marks the connection as lost, tells every administrator once by notification (and by email if they have email on for Automation and apps), and sends everyone’s chat messages by email instead until you choose a working connection.

​
What people get

After the connection is set up, Chat appears as a column under Profile → Notifications. People link their own account there; Collabase finds it by their email address. A message carries who did something, the object and where it lives, an excerpt and a link that opens it in Collabase, in the person’s language. Chat follows the person’s choice of immediate or daily delivery, bundles events of the same object and holds back floods like email does. A daily summary goes out as one message.
  • Security notices never go to chat.
  • Without a linked account, or when the link stops working, the message goes out by email instead, if email is on for its category. The person sees Check the chat connection in their settings and a notification.
  • Chat replaces email for that event. Nobody gets both.

​
Urgent items

A mention, an assignment of a work item or of a to-do in a page, and a requested approval count as urgent. If an urgent entry is still unread and not archived after 30 minutes, the person gets it once more by chat, or by email if they have no chat, even when they chose a daily summary. A person can switch this off under Profile → Notifications → Remind me about urgent items. It is on by default. The rule is fixed and cannot be changed per category.

​
Report to a channel

Whoever may manage the settings of a space opens Space settings → Chat channels, adds a channel and chooses the categories it receives, for the whole space or for one project. Collabase sends a first message to the channel, so a wrong channel ID or a missing bot shows right away.
  • Slack: the channel ID, such as C0123456789. Add the bot to the channel first.
  • Teams: the team ID and the channel ID separated by a slash.
A channel message carries only the title of the object, the person who did it, the category and a link. It never carries an excerpt or a comment, because nobody can say who reads a channel. For the same reason, private projects and restricted pages never report to a channel, and a project that becomes private stops reporting at once. The link opens the object only for people who may see it. If a channel is deleted or the bot is removed, the channel is marked as unreachable and the people who manage the space are told once.

​
Browser notifications

On Profile → Notifications, a person turns browser notifications on for a device. The browser asks for permission only then, never on a page view. Several devices are possible, and each can be removed. Browser appears as a column once a device is registered. The notification shows who did something, the object and a link; a security notice only says Security notice for your account. A device the browser reports as gone is removed without further attempts. The desktop app has its own notifications and does not use this. Browser notifications use web push with a key pair that Collabase creates on first use and stores in the instance settings, the private key encrypted. Messages travel through the push service of the person’s browser. Changing the instance’s encryption key replaces the pair and removes all registered devices; people turn them on again.
Last modified on October 17, 2026