Messaging Users
Stemma provides a quick and easy way to send messages to specific groups of users on the basis of their relationship to a table (e.g. are they an owner in Stemma, have they queried the table in the prior three months, etc.). If you need to announce a future change, for example, or notify users when significant events occur, such as when a table has been deprecated, you can use Stemma messaging to ensure that the affected users will receive the notification.

You can compose a custom message to users and teams related to a table by clicking the Message button on the top-right corner of the Table detail page
Select the user groups you want to notify and type your message in the box. Learn more about user groups.
Notification types
There are three types of notifications you can send in Stemma, depending on the receivers and your personal preferences. If a member of a related group is a user, they can receive either email notifications or Slack private messages. If a member of a related group is a team (Slack channel), they will receive a message in Slack.
Slack notifications
After you have completed our Slack Integration, you can send and receive messages from the Stemma bot.

Messages in channels
If a member of a related group is a team, they will receive a message from the Stemma bot in the corresponding Slack channel.
📘 Note
Make sure you add the bot to all channels that need to receive messages.
Slack private messages

You can choose to receive notifications from Stemma as Slack private messages. To receive messages from the bot, you need to add the Stemma application to your Slack configuration.

To modify your preferred notification method, contact your Stemma representative.
User groups
Each group contains a list of users and teams (Slack channels). In Stemma there are four different types of user groups related to a table:
- Owners of the table
- Owners of dashboards using the table
- Owners of derived tables – this is based on the lineage for the table
- Frequent users of the table
Stemma will only show the options that apply to the given asset. For example, if a user is sending a custom message for a table that does not have any downstream lineage there will not be an option for Owners of derived tables.