Skip to main content
Connect a Slack workspace to DevPerform to receive a weekly team-health digest in a channel of your choice, and to deliver surveys over Slack DM instead of (or alongside) email. It’s optional, admin-only, and you can disconnect at any time.

​
Connect your workspace

  1. Go to Admin → Slack.
  2. Click Add to Slack and approve the requested permissions in Slack.
  3. You’ll land back on the Admin page with Slack connected.
Each DevPerform account connects a single Slack workspace. Only account admins can connect, disconnect, or change Slack settings.

​
Weekly team-health digest

Once connected, pick a channel under Admin → Slack. Every Monday morning DevPerform posts a short digest there:
  • Last week’s delivery headline — PRs merged and median cycle time.
  • Any notable week-over-week changes (e.g. “Cycle time ↑ 40% vs the prior weeks”), so regressions surface without anyone opening a dashboard.
Use Send digest now to preview it immediately instead of waiting for Monday.

​
Deliver surveys over Slack

When you send a survey, choose how it goes out under Deliver via:
  • Email — the default.
  • Slack DM — DevPerform matches each recipient to their Slack account by email and sends the survey link as a direct message. Anyone not in the workspace (or whose Slack email doesn’t match) automatically falls back to email, so no one is missed.
  • Both — email and Slack DM.
Reminders follow the same channel the survey was sent on. Responses stay anonymous exactly as they do over email — a Slack DM is one-to-one, and individual answers are never attributed.
Survey delivery over Slack matches people by their email address, so an engineer must have an email on file in DevPerform and be in the connected Slack workspace with that same address. Otherwise they receive the survey by email.

​
Personal PR notifications (opt-in)

Beyond the team digest, each engineer can opt in to Slack DMs about their own pull requests under Settings → Personal notifications. Pick which events you want:
  • PR approved / Changes requested — a reviewer acted on your PR.
  • Review requested — someone asked you to review their PR.
  • PR merged — your PR was merged by someone else.
  • CI failed / CI passed — a CI run on your PR finished (CI passed is off by default; it can be chatty).
Three things to know:
  • Self-only, always. Notifications go to the person the PR belongs to — never to a manager, never to a channel, never aggregated. There is no admin view of anyone’s notification activity.
  • Off by default. Nobody gets DMs until they turn them on themselves, and there’s a Send test DM button to confirm delivery.
  • Delivery timing depends on your code host (see below). DMs find you by email, so your DevPerform email must match your Slack account’s email.

​
GitHub and GitLab

  • GitHub — near-real-time, driven by webhooks: DMs arrive within moments of the event.
  • GitLab — GitLab connections are OAuth-based with no webhook path, so DevPerform spots your events at sync time: DMs go out when DevPerform next syncs your projects (on the regular sync cadence) rather than instantly, making them near-real-time rather than immediate. Because events are detected by comparing each sync rather than receiving a one-shot webhook, a shared dedup ledger records what’s already been sent — so a re-sync never DMs you twice about the same event. GitLab covers PR approved, PR merged, and CI passed / failed; Review requested and Changes requested aren’t available from GitLab’s OAuth API and so aren’t sent for GitLab merge requests.
  • Bitbucket — personal notifications aren’t available yet.
Requires a connected Slack workspace on a plan that includes Slack features.

​
Permissions

DevPerform requests only what it needs: post messages, list channels for the digest picker, and look up users by email for survey delivery. It never reads your messages.

​
Disconnect

Go to Admin → Slack → Disconnect. DevPerform forgets the workspace token immediately; digests and Slack survey delivery stop (surveys fall back to email).