Murmurd for Slack
Run async check-ins inside Slack without widening data access.
Murmurd sends check-ins, blocker flows, and manager digests in Slack. It is built for admin review, with explicit boundaries around direct messages, channels, and profile data.
Reviewer-ready links
Murmurd Slack review
Install flow, scope summary, and DM boundaries
In Slack
09:00 Daily prompt
What moved forward? Any blockers?
Reply-based check-in
Replies are processed only when sent to the Murmurd bot.
/escalate and /priority
Fast blocker routing and weekly priority capture.
Admin view
Can access
Bot DMs for replies, profile data for linking, workspace metadata
Cannot access
Employee DMs, public channels, private channels, Slack files
Review package
Install URL: app.murmurd.com/slack/install
Support: murmurd.com/support
Privacy: murmurd.com/legal/en/privacy
Admin guide: murmurd.com/docs/integrations/slack-enterprise-approval/
What Murmurd handles in Slack
A calm operating rhythm for teams that do not want meetings doing the work of software.
Murmurd keeps the important moments in Slack: the morning check-in, the blocker escalation, and the end-of-week digest. No dashboard hunting required.
Slack rhythm
09:00
Daily prompt lands
Murmurd opens the loop in DM before the day gets noisy.
Midday
Blockers escalate fast
Teams can route issues the second they appear.
Friday
Leads get a clean digest
Summary, blockers, and follow-through land in one place.
01
Daily check-ins in DM
Prompt teammates in Slack, collect replies, and keep standups out of the calendar.
Slack moment
Prompt, reply, and follow-up happen in one thread.
Reviewer note
Reply processing applies only to Murmurd bot DMs.
02
Slash commands for blockers
Use /escalate and /priority without leaving Slack or opening another dashboard.
Slack moment
Capture action without context-switching to the web app.
Reviewer note
No additional channel history is required.
03
Friday digest delivery
Send leaders a clean weekly summary of activity, blockers, and follow-through.
Slack moment
Leadership receives a polished summary instead of a message pile.
Reviewer note
Digest delivery uses the same narrow DM messaging model.
Data access boundary
No employee DMs. No channel history. No ambiguity.
Murmurd uses Slack to collect check-ins and route actions. It does not turn Slack into a general-purpose data source.
Reviewer shorthand
Slack is a delivery surface, not a surveillance surface.
The only message-reading permission is used to process replies sent to the Murmurd bot in direct messages.
Access design
Murmurd can access
- Direct messages sent to the Murmurd bot for reply-based check-ins
- Slack profile and directory data used for account linking and admin setup
- Workspace metadata needed to identify the connected Slack workspace
Murmurd cannot access
- Employee-to-employee direct messages
- Public channel history
- Private channel history
- Slack files or a permanent full copy of the Slack directory
Why im:history exists
So a teammate can reply directly to a Murmurd prompt.
Murmurd matches that reply to the pending check-in thread. It is not used to inspect employee conversations or channel traffic.
Admin handoff
Pair this section with the enterprise approval guide when a platform team needs an explicit written boundary.
Open approval guideRequested Slack access
Scope-by-scope justification for workspace admins.
Every requested permission maps to one concrete user-facing workflow. Nothing here exists for generic workspace monitoring.
Fast summary
5
requested scopes
1
message-reading scope
0
channel history scopes
Slack scope
Why Murmurd needs it
chat:write, im:write
Send check-in prompts, reminders, and manager digests.
commands
Run /escalate, /priority, and Slack modal flows.
users:read, users:read.email
Match Murmurd users to Slack accounts during setup and linking.
team:read
Identify the connected Slack workspace.
im:history
Process replies sent to the Murmurd bot in direct messages only.
Admin resources
Everything an approver should need in one place.
Use these public pages in Slack Marketplace submissions, enterprise review questionnaires, or internal security requests.
Enterprise approval guide
Scope-by-scope explanation of what Murmurd reads, stores, and does not access.
Open guideSupport page
Public support contact details, response expectations, and escalation routes.
Get supportPrivacy policy
Public privacy notice covering data categories, retention, subprocessors, and requests.
Review privacy policyReady to install
Start the Murmurd Slack install flow or hand this page to your admin.
Murmurd keeps the install path simple, while still giving security and platform teams a clear explanation of scopes, support, and data handling.