Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • Setting up Slack notifications
  • Setting up project-level Slack notifications
  • Setting up personal Slack notifications
  • Setting up email notifications
  • To set up at the project level
  • To set up at the code deployment or feature flag level
  • To set up at the Team level

Was this helpful?

Slack & Email Notifications

PreviousJenkinsNextAuto-verify deploys

Last updated 6 months ago

Was this helpful?

Sleuth can send emails or Slack notifications when something of significance happens, including messages for your entire team, yourself, and/or to commit and pull request authors.

Using Microsoft Teams? Check out the to see our rich library of notifications for Microsoft Teams

Setting up Slack notifications

Before you set up project-level Slack notifications, the must first be enabled in your Slack workspace. Once that's done, you can configure who and how those notifications are sent and who receives them.

You must be the owner of or have admin access to an organization to setup an integration. See for more information.

Setting up project-level Slack notifications

  1. Select a project in the sidebar, then click Project Settings.

  2. Click Slack Notifications.

  3. In the Slack channel dropdown, start typing the name of the Slack channel that will receive change notifications. If the channel is private, you will need to invite the Sleuth bot to the channel first.

  4. Click Save.

At this point, you can notify users in your Slack organization that a notifications channel for this project has been set up and that they should join it to receive any and all change notifications that occur in that project.

Setting up personal Slack notifications

In the previous section, you created a project-level Slack notification. Team members will only receive change notifications if they join the corresponding Slack channel. However, you might want customized notifications sent directly to yourself. You can do this by configuring your user-level Slack notifications preferences:

  1. Select your username in the bottom of the sidebar, then click Manage Account.

  2. Click Notifications.

  3. Any you've already set up will be displayed here. Enable the Slack notifications toggle. sends a notification only if a deployment occurs in which the impact of your code on production errors is anything except

  4. You can enable or disable Deployed code and/or Impact of your Code:

    • Deployed code: Selecting All means you will receive a Slack notification every time code in which you are the author is deployed. Selecting Exclude my deployments notifies you of all deployments except those in which you're the author. This option is great if you're up to speed on your own code but want to keep tabs on how the rest of your team's deployments are doing.

    • Impact of your Code: Selecting All means you will always receive a Slack notification about the impact of your code on the rate of production errors. Selecting **Exclude healthy **will only notify you when a deployment is not fully healthy_; _this includes any that are marked as Unhealthy, Ailing, or Improved.

Setting up email notifications

Email notifications are sent at the frequency you select, and can be configured individually at the project and change source level.

To set up at the project level

  1. Select a project in the sidebar.

  2. Click My Notifications in the upper-right corner of the Dashboard.

3. Select a notification frequency in the dropdown. More than one can be selected.

To set up at the code deployment or feature flag level

  1. Select a project in the sidebar. The project's dashboard is displayed.

  2. Select a code deployment or feature flag in the sidebar and click on its title link. The dashboard for the code deployment or feature flag is displayed.\

  3. Click the bell icon for My Notifications in the upper-right corner of the dashboard. \

  4. Select a notification frequency in the dropdown. More than one can be selected.

Add noreply@email.sleuth.io to your email provider's or your email application's spam filter whitelist to prevent the notification email from getting caught up in spam filters.

The notification email provides a digest of the following activity during the selected timeframe:

  • Number of deployments made from each project in your organization

  • Number of pull requests

  • Number of commits

  • Number of issues

  • Number of changed files

  • Number of unique authors

To set up at the Team level

Team-level notifications keep you and your teams up to date on how they're performing across projects. To set up team-level email notifications, perform the following steps:

  1. Select a Team in the sidebar. The Team's dashboard is displayed.

  2. Click the bell icon for My Notifications in the upper-right corner of the dashboard.

  3. Select a notification frequency in the dropdown. More than one can be selected.

Add noreply@email.sleuth.io to your email provider's or your email application's spam filter whitelist to prevent the notification email from getting caught up in spam filters.

Read the for information regarding the collection, use, and disclosure of Personal Information we collect.

Sleuth Privacy Policy
Automations Marketplace
Access control
email notifications
Sleuth DORA App for Slack