Setting up notifications
Configuring notification channels requires Admin permissions in Dataedo.
Dataedo offers in-app, email, and integration-based (Microsoft Teams and Slack) notifications. This article covers what needs to be configured in your Dataedo instance for each of them to work. Once a channel is configured, each user decides in their own notification settings which events it delivers to them.
Prerequisites
For the notification system to run in your repository, you have to set up the Dataedo Agent. The Agent processes the events that trigger notifications and delivers them through all channels.
Delivery channels
In-app notifications
In-app notifications work by default once the Agent is configured. No further setup is needed.
Email notifications
Email notifications require you to provide the credentials of an SMTP server that Dataedo will send messages through. This is covered in our article about configuring email notifications.
Email is also one of the channels users can receive their digest through.
Integrations
Notifications can also be delivered to external tools, such as Microsoft Teams and Slack. You can configure integrations in Settings > System Settings > Messaging, and each one usually also requires some configuration in the external tool. See Integrations for the list of available integrations and their setup.
Archiving notifications
In-app notifications are deleted from Portal 180 calendar days after they are read. Unread notifications are never deleted automatically. 180 days is the default value, but you can modify it to have the notifications removed earlier or later. To do so, head to your repository and open the dbo.configuration table. There, locate the row where the key column is set to AUTO_CLEAN_NOTIFICATIONS_INAPP_MESSAGES_PERIOD_IN_DAYS and modify its value to match the number of days after which notifications should be deleted. Only integer values are accepted. If you want to disable the automatic deletion rather than adjust the deletion period, simply set the value to 0.
There are several other keys in dbo.configuration that you should be aware of when it comes to notification history management:
AUTO_CLEAN_NOTIFICATIONS_EVENTS_PERIOD_IN_DAYS— how long the events that trigger notifications are kept. Default: 30.AUTO_CLEAN_NOTIFICATIONS_EMAIL_MESSAGES_PERIOD_IN_DAYS— how long sent emails are tracked. Default: 30.AUTO_CLEAN_NOTIFICATIONS_TEAMS_MESSAGES_PERIOD_IN_DAYS— how long sent Teams messages are tracked. Default: 30.AUTO_CLEAN_NOTIFICATIONS_SLACK_MESSAGES_PERIOD_IN_DAYS— how long sent Slack messages are tracked. Default: 30.AUTO_CLEAN_NOTIFICATIONS_ACTIVITIES_PERIOD_IN_DAYS— how far back the history of what happened on your objects reaches, including the Notifications Center. Default: 180.
The defaults keep the tracked pieces of information from bloating your database. Each of these keys accepts integer values only, and 0 disables the cleaning of that particular kind of record.
We strongly advise that you do not modify these default values; however, you can still change them if necessary for your organization's needs.
