You can modify the notification delivery behavior using the following server flags.

| Required| CLI| Env| Type| Description| Default|

|:--------:|-------------------------------------|-----------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------|---------|

| ✔️|`--notifications-dispatch-timeout`|`CODER_NOTIFICATIONS_DISPATCH_TIMEOUT`|`duration`| How long to wait while a notification is being sent before giving up.| 1m|

buttons

-`labels`: dynamic map of zero or more string key-value pairs; these vary from event to event

All users have the option to opt-out of any notifications. Go to**Account** ->**Notifications** to turn notifications on or off. The delivery method for each notification is indicated on the right hand side of this table.


Administrators can configure which delivery methods are used for each different[event type](#event-types).

To pause sending notifications, execute`coder notifications pause`.

Administrators may wish to stop_all_ notifications across the deployment. We support a killswitch in the CLI for these cases.

To pause sending notifications, execute[`coder notifications pause`](https://coder.com/docs/reference/cli/notifications_pause).

To resume sending notifications, execute`coder notifications resume`.

To resume sending notifications, execute[`coder notifications resume`](https://coder.com/docs/reference/cli/notifications_resume).

be retried

- after`CODER_NOTIFICATIONS_MAX_SEND_ATTEMPTS` is exceeded, it transitions to`permanent_failure`

Diagnostic messages will be saved in the`notification_messages` table and will be logged, in the case of failure.

Diagnostic messages will be saved in the`notification_messages` table and will be logged, in the case of failure.