Skip to content

Set up notification channels

Use Settings › Notification Channels to choose how and where OpenLatch delivers notifications and digest reports. You need the admin role or higher.

The Notifications settings page of the OpenLatch console, in the Crispy Pay demo organization.The Notifications settings page of the OpenLatch console, in the Crispy Pay demo organization.
Notification Channels: each channel OpenLatch can deliver to, and whether it is configured.
ChannelWhat it does
In-app notificationsShows the notification bell in the console. Turning it off hides the bell; notifications are kept
EmailDelivers notifications and digest reports through the email provider your OpenLatch site is configured with
SlackSends notifications to Slack channels
Microsoft TeamsPosts notifications and digest summaries to Microsoft Teams channels
DiscordRoutes notifications to Discord channels through webhooks
Custom webhookSends signed JSON events to any HTTPS endpoint, compatible with the Standard Webhooks specification

Slack, Microsoft Teams, Discord and custom webhook channels can each be added more than once, for example one per team.

  1. On the channel’s card, choose Configure.
  2. Follow the setup guide in the drawer, then enter the destination: a Slack, Microsoft Teams or Discord webhook address, or your own HTTPS endpoint.
  3. Choose which notifications the channel receives, and save.
  4. Send a test, and check that it arrives.

A custom webhook signs every event with a signing secret, so your endpoint can check that an event came from OpenLatch. The secret is shown once, when you reveal it to copy into your endpoint’s configuration. Rotate signing secret issues a new one; update your endpoint at the same time.

To send a recurring report rather than individual notifications, see Schedule activity digests.