Notifications
Stay informed when missions are ready — manage email and Slack notifications, configure org-wide Slack channels, and view your notification history
Alloy can notify you by email or Slack when missions, reports, and scenario results are ready. You can manage these preferences at any time.
Notification bell
The bell icon in the sidebar shows your most recent notifications. Click it to open a dropdown with up to 20 recent items.
Each notification shows:
- The mission name (or names, if multiple were batched together)
- A brief label (e.g. "Mission")
- A relative timestamp (e.g. "5m ago", "2h ago")
Click a notification to expand it and see more detail.
The notification bell shows notifications for your entire organization — all team members see the same history.
Managing your preferences
Email preferences are per-user — each person in your organization controls their own email settings. Slack preferences are org-wide because everyone in the configured channel sees the same alerts.
How to access
Missions
Mission email is enabled by default with My missions only selected. You can turn it off with the Missions toggle or change the scope:
| Scope | What you receive |
|---|---|
| My missions only | Missions you personally upload through Alloy in the browser |
| All missions | Missions uploaded by anyone in your organization, including device and integration uploads |
Alloy waits for processing and every automatic report associated with the mission to finish before notifying you. If the mission has no automatic reports, processing completion is enough. Multiple reports for one mission produce one mission notification. Ad hoc report requests and reruns do not create another mission notification.
Nearby mission completions are combined into one email. The batch waits for five minutes without new processed missions, or sends when it reaches 100 missions. Missions still waiting for reports remain queued for a later email. If a report finishes after the quiet period, its mission can notify on the next retry without another five-minute wait.
Enabling mission email only covers missions that finish processing afterward. Turning it off and back on does not send catch-up emails for missions that finished while it was off. Existing members are also enabled for My missions only during rollout; this does not send historical mission notifications.
Scheduled reports
Use Scheduled reports to select the recurring reports you want to receive by email. You can select multiple reports. Your selections remain subscribed when their prompts are edited. Scheduled report subscriptions are separate from your mission scope.
Organizations with the device security alert enabled also show Device needs reprovisioning, which notifies you when a device uses its provisioning key after approval and may require operator action.
Slack notifications
If your organization has the Slack integration connected, Alloy can post notifications directly into a Slack channel. Unlike email preferences, Slack notifications are org-wide — everyone in the channel sees the same alerts.
Available Slack notification types
| Event | Description |
|---|---|
| New mission uploaded | A new mission is uploaded to the platform — whether via the app or from an S3/GCS bucket you've integrated with Alloy |
| Early access ready | Mission data is available for querying (before the full report) |
| Triggered report ready | A mission-triggered prompt finishes generating a report; Alloy posts it in the mission's Slack thread |
| Scenario match found | One of your scenarios detects a pattern match on a mission |
| Scheduled report ready | One of your scheduled prompts finishes generating a report |
How to configure
Most Slack notifications are set up from within Slack. Go to the Slack channel where you want to receive the alerts and ping @Alloy with what you want. For example:
- "@Alloy notify this channel when missions are ready"
- "@Alloy DM me when a scenario match is found"
- "@Alloy post here when a new mission is uploaded"
Once configured, the notification will appear in the Notifications tab with a toggle so anyone in your org can pause or resume it. Unconfigured types show as Not configured until you ask @Alloy to set them up.
Each Slack notification type is configured independently. Triggered reports reply in the relevant mission thread when possible; if that thread does not exist yet, the first triggered report starts it and later triggered reports for the same mission reply there. Scheduled reports are posted as top-level messages. Scenario match notifications can cover every scenario or one specific scenario. When a Slack report notification is re-enabled, Alloy only posts reports generated after it was turned back on.
Can't find Alloy in your Slack workspace? Your org may not have connected Slack yet — see Slack integration to get started.