Review from Slack
Connect Slack, understand what each Slack workflow does, and keep the evidence record in Neatlogs.
Slack brings time-sensitive Neatlogs activity into the channels where a team already works: alerts, new incidents, mentions, and answers to questions about your traces. Decisions still happen in Neatlogs. Slack messages link back to the trace, incident, alert, or Eval they describe.
Slack is a notification and question surface. You can't review an Eval, accept or dismiss an incident, or change an incident's status from Slack. The one decision you can make in Slack is approving or rejecting a prompt promotion request that is assigned to you.
Understand the Slack workflows
| Workflow | What it does | Where it is configured |
|---|---|---|
| Alert delivery | Posts an alert to the rule's Slack channel, or sends it as direct messages to members who opted in | The alert's Response step (Slack switch and Slack Channel Override). See Create an alert |
| New incident posts | Posts each new incident in a project to one shared channel | Settings → Project → Project notifications → Incident Slack channel |
| Personal notifications | Sends you direct messages for mentions, approval requests, alerts, the daily digest, and Eval assignments | Settings → Account → Notifications (per user, per project) |
| Ask Neatlogs | Answers questions about traces, detections, and prompts when you @mention the bot, DM it, or run /neatlogs | Available once Slack is connected |
| Link previews | Expands pasted links to Neatlogs traces, spans, and detections | Available once Slack is connected |
| Thread evidence | Lets a linked Neatlogs conversation thread corroborate incidents in a project | A project admin selects Authorize thread under Issue evidence access |
| Slack as an AI tool | Lets Copilot and Neat Agent read Slack channels your own account can see, read-only | Settings → Account → Tools & MCP, connected by each person |
These permissions are separate. Connecting Slack for the organization does not give an AI agent access to channel history; that needs your own connection in Tools & MCP.
Connect Slack
Slack is connected once for the whole organization under Settings → Organization → Integrations. Any organization member can connect or disconnect it, so agree on an owner first. One Slack workspace maps to one Neatlogs organization. For the connection steps, see Integrations.
After connecting:
- The Team members status card on the Slack connection shows which organization members can receive Slack notifications. A member is matched by the email on their Neatlogs account, so someone whose email isn't in the Slack workspace gets no direct messages.
- The Neatlogs app can post in public channels without an invite. If setup shows Update Slack permissions, select it to grant that. For a private channel, invite the Neatlogs bot to the channel, then refresh the channel list.
- To post new incidents to a channel, open Settings → Project → Project notifications, choose the channel under Incident Slack channel, and select Save channel. This needs a Project Member or Project Admin role; other readers see "Ask someone with project write access to configure the incident channel."
If an investigation or evaluator needs Slack context, connect your own Slack account under Settings → Account → Tools & MCP. That connection is personal and read-only.
Read a delivered message
An alert message starts with Heads up and the rule name; a repeat firing starts with Update and is threaded under the first post. It shows the organization and project, the severity and time, a one-line summary, and an Investigate or View matching event button. A new-incident post shows the incident title, severity, project, and time, with a View incident button.
Before acting on an alert, confirm:
- the Neatlogs project;
- the alert rule and severity;
- the detection, metric, or ingestion condition;
- the evaluation window and observed value;
- the representative evidence behind the link;
- the action expected from the recipient.
Slack is the notification surface, not the complete evidence record. Open the linked Neatlogs object before deciding that a model, tool, or deployment caused the problem.
Act on a Slack message
Most Slack messages carry link buttons only. To act:
- read the summary;
- open the linked Neatlogs object;
- make the decision there: change the incident status, submit the Eval answer, or edit the alert rule;
- confirm the change appears on the Neatlogs object.
A normal Slack reply does not update an incident, Eval, or alert. If a message offers a snooze or acknowledge option, selecting it only returns a note that the action is no longer supported from Slack. Manage the alert in Neatlogs instead.
Two exceptions work inside Slack:
- Approval requests. When someone requests your approval for a prompt promotion, the direct message has Approve, Reject, and View Diff buttons. Only the assigned approver can resolve it.
- Questions to Neatlogs. Replies to the bot are answered in Slack, as described next.
Ask Neatlogs from Slack
@mention the Neatlogs bot in a channel it's in, send it a direct message, or use the slash command:
/neatlogs in:checkout-agent Why did refund answers fail this morning?- The first time you ask, the bot sends you a private Link your Neatlogs account message. Open it, link your Slack user to your active Neatlogs account, then ask again.
- Answers are scoped to one project. Add
in:<project-key>to choose the project for that question. - When you mention the bot inside a thread, it reads recent messages in that thread for context.
When you paste a link to a Neatlogs trace, span, or detection, Slack shows a preview card for it.
Keep Slack and Neatlogs consistent
When a Slack conversation changes the decision, summarize it on the linked trace, incident, or Eval. Record the authoritative policy, expected behavior, owner, and next action with the evidence.
Avoid copying complete sensitive payloads into Slack. Link to the permission-controlled Neatlogs object when possible.
Troubleshoot delivery
| Symptom | Check |
|---|---|
| Channel is missing from the picker | Whether the channel is private and the Neatlogs bot was invited; then refresh channels |
| Alert fired but no message arrived | The rule's Slack switch and channel; for direct messages, the member's category toggle and Receive Slack direct messages; quiet hours, which hold non-critical Slack and email until they end; delivery results in the alert's History |
| A teammate never gets direct messages | Team members status: their Neatlogs email must match a Slack account |
| No post for a new incident | Incident Slack channel in Settings → Project → Project notifications |
| Link opens an access error | Neatlogs project access for the recipient |
| A button says it is no longer supported from Slack | Open the linked object and act in Neatlogs |
| The bot asks you to link your account | Follow the private link, then ask again |
| The bot answers about the wrong project | Add in:<project-key> to the question |
| AI cannot read channel context | Your own Slack connection in Settings → Account → Tools & MCP |
Frequently asked questions
Does connecting Slack enable every workflow?
No. Alerts post to Slack only when the rule turns Slack on, new incidents post only after a project sets an Incident Slack channel, and direct messages follow each person's notification settings. AI tool access is a separate, personal connection.
Can I review an Eval from Slack?
No. Eval assignments and updates arrive as direct messages that link back to Neatlogs, where you review under Assigned to me. See Human review.
Can a Slack recipient open every linked trace?
No. Neatlogs project permissions still apply.
Can an investigation read private channels?
Only through your own Tools & MCP Slack connection, and only channels that your Slack account can access.
Does removing the Slack integration remove old messages?
No. Disconnecting stops Slack notifications and bot replies for the whole organization. Messages already delivered to Slack follow that workspace's retention and administration rules.