NebulaNebula
Workspace

Notifications: destinations, rules and write approval

Get Nebula notifications on your phone or in Slack, Discord or Telegram DMs, choose which events reach you, and turn on write approval for risky actions.

You can get Nebula's updates outside the app — on your phone, by email, or as a Slack, Discord or Telegram DM — and choose exactly which events get through. Your Mentions inbox always receives everything, so rules only add delivery, they never hide anything.

Destinations

Destinations are the places Nebula can reach you beyond the app. Email is always available as a destination. The others appear as Connected once they're set up.

DestinationWhat you getHow it's switched on
EmailMessages to your account emailAlways available
MobilePush notifications from the Nebula mobile appEnable it on your phone
Slack DMDMs from the Nebula Slack botThe Nebula Slack bot is connected
Discord DMDMs from the Nebula Discord botThe Nebula Discord bot is connected
Telegram DMDMs from the Nebula Telegram botThe Nebula Telegram bot is connected

Open Settings → Workspace → Notifications. Destinations shows each one as Connected or Not connected.

Open Settings → Notifications, under Workspace Settings. Destinations has a Connect button for each chat app that isn't connected yet.

Turn on push on your phone

Nebula doesn't turn on push by itself when you sign up, so switch it on once on each phone.

In the mobile app, open Settings → Notifications.

Under Destinations, find Mobile and tap Enable.

Allow notifications when your phone asks. The row changes to Connected.

If you see "Push notifications could not be enabled on this device.", you probably declined your phone's prompt earlier. Allow notifications for Nebula in your phone's own settings, then tap Enable again.

Rules

A rule sends one kind of event to the destinations you pick. Without any rules, events stay in your inbox.

In Notifications, choose Add rule.

Pick the Event, such as Approval needed or Task failed.

Under Deliver via, tick one or more destinations. A new rule starts with Email ticked, and a rule with nothing ticked stays Inbox only.

Choose Add rule. Edit or delete it from the same list any time.

These are the events most people route somewhere:

EventWhen it fires
MentionSomeone mentions you
Approval neededA task is waiting for your approval
Task completed / Task failedA task finishes or runs into an error
Job completed / Job failedA scheduled task's run finishes or fails
Reconnect neededA connected app needs you to sign in again
Call inviteSomeone invites you to a call

The Event list also covers channels, apps, devices, agents and scheduled tasks being created, changed or removed. Billing alerts and workspace invites always reach you, so they aren't offered as rules.

Route Approval needed to your phone. A task that's waiting on you then reaches you wherever you are, instead of sitting until you next open the app.

Write approval: the safety gate

The safety gate makes agents pause before a write that looks risky or unexpected, and shows you why. It's off by default, and each person turns it on for themselves.

Open Settings → Account → Profile and, under Write approval, turn on Write approval safety gate.

Open Settings → Profile, under User Settings, and turn on Safety gate in the Write Approval section.

With the gate on, actions that only read run as normal. When a write looks dangerous or doesn't match what you asked for, it doesn't run. The task stops and tells you, in plain words, what it wanted to do and why. Reply in the task to tell it to go ahead or to change course, and the work picks up from there.

Gate offGate on
ReadsRunRun
Ordinary writesRunRun
A write that looks risky or off-briefRunsStops and asks you in the task, or is refused outright
The same write in work nobody is watching, like a scheduled runRunsIs refused, and the run reports it

Tools on your Always allowed list, under Write approval, skip the check. To put one back under the gate, choose Remove next to it on desktop, or tap the ✕ on its chip on mobile. Shell commands are always checked, whatever the list says.

Actions on a device are approved separately, with a card in the chat. Choosing Always allow there adds the action to Device access in the same settings page, where you can remove it the same way. See Tasks.

Common questions

On this page