Notifications

Notifications inform users about important events, such as task assignments, task state changes, or mentions in comments. Most workspace notifications can be sent as Slack or Discord direct messages, or by email. When browser push notifications are available for your web app deployment, you can enable them in User Settings -> General and your browser will ask for permission. For supported notifications, Bnder uses browser push first. If push is disabled, unavailable, or cannot be delivered to any registered browser, Bnder falls back to the normal workspace channel.

Browser push covers task assignment, repeat, comment, subscriber, and deletion notifications, plus event invites and updates, milestone reminders, shared files and folders, billing or Pro-seat alerts, and internal ticket assignment, mention, reporter-update, SLA, and booking-owner notifications.

Browser push has three layers of control. The account-level Notification delivery preference controls whether browser push is attempted before normal workspace channels. The Browser push notifications switch controls whether this browser can receive push at all. Workspace preferences then let each member turn task, ticket, calendar, file, milestone, or billing browser push on or off for that workspace. Notifications can appear whether the app is open in a tab or running in the background.

Warning: 

Discord notifications require direct messages from server members to be allowed. Slack notifications require the user to remain in the linked Slack workspace and allow messages from the installed Bnder app.

Notification Types

There are several types of notifications:

  • Task Assignment: Sent when a user or a role of the user is assigned to a task.
  • Task deadline due: Sent when a task deadline is due within 12 hours.
  • Task deadline was missed: Sent when a task deadline was in the past 12 hours and the task is still not done.
  • Task deadline was missed on urgent tasks: Sent when a task deadline was in the past 36 hours and the task is still not done and the priority is high or urgent.
  • Assigned task was repeated: Sent when a task was repeated and the user was assigned to the new task.
  • Task has a new comment: Sent when a task is assigned to a user and a new comment is added to the task or when the user previously commented on the task.
  • Task subscriber updates: Sent when you subscribe to a task and someone changes it. Task subscribers require a Starter or Pro seat.
  • Milestone is due: Sent to the project manager when a milestone is due within 6 hours and has tasks that are not done.
  • Booking owner updates: Sent to calendar owners for new booking requests, auto-confirmed bookings, cancellations, and reschedules.
  • Ticket updates: Sent for assigned tickets, ticket mentions, reporter replies, new-ticket project notifications, and SLA warnings or escalations when the notification is connected to your workspace user.

Notification restrictions

  • Notifications to role members are sent only if the role has less than 10 members. If a role has more members, no notifications are sent to the role members.