Notification channels

Admin → Notifications holds the settings that belong to the organisation rather than to a person. What each user receives by email and push is theirs to decide under notification preferences; whether an email arrived is on Email deliverability. This page is about the channel in between: SMS.

SMS

SMS costs money per message, so the channel is off until an administrator turns it on, and capped once it is.

• SMS enabled is the master switch. Off means every SMS is refused, whatever the other settings say.
• Allow-list (job types) names the notification types that may go out by SMS, separated by |. The default is schedule_change alone; add call_sheet to let call sheets through as well.
• Monthly cap (cents) stops sending for the rest of the month once the spend reaches it. The line under the field shows what has been spent against the cap this month. 0 means no cap.
• Provider is the SMS gateway: Twilio, MessageBird or Vonage. Not set keeps the channel configured but unable to send.

Save SMS settings writes the row. There is one row per organisation, so the page always shows the current state.

Two gates, not one

The switch and the cap decide whether the organisation sends SMS at all. Who may trigger one is a permission — Send SMS notification — granted per role under Roles. Both have to allow it.

Related surfaces

The links at the bottom lead to the three places SMS and email meet the rest of the system: the deliverability log, outbound webhooks and the bulk-message composer under Notifications.

The page is open to administrators only.