Notifications
Control notification defaults, team overrides, and personal preferences.
Where to find it: Settings → Notifications
Who can access it: All team members can manage Your notifications. Only admins can manage Account notifications and Team notifications.
What it does
Notifications let you control which events trigger alerts and how they are delivered.
You can configure notifications at three levels. The most specific setting always wins.
Notification levels
Account notifications
Default settings for the whole account
Applies to everyone unless a team or personal setting overrides it
Team notifications
Settings for one team
Overrides account defaults for that team
Your notifications
Personal settings for one team member
Overrides both team and account settings
The cascade is:
Account < Team < Personal
Notification groups
Events are grouped by entity and ownership so you can tune alerts in bulk.
Built-in groups
Assigned customers — Events for customers assigned to a team member
Involved projects — Events for projects where a team member is involved
Assigned tasks — Events for tasks assigned to a team member
Depending on your setup, you may also see other groups, such as Team's customers, or custom groups created in your account.
You can also click + New notification group to create your own filtered groups.
Delivery channels
Each event can be configured per channel.
In app
Notification, Indicate Activity, or Off
Coming soon
Summary
Coming soon
Other notification settings
Email notifications are account-wide. They are either on or off for the whole account. Startdeliver turns this setting on. You cannot configure it per customer.
For specific notifications, set up an automation.
Slack notifications are controlled in the Slack app inside Startdeliver.
Completed projects send no notifications. Tagged customers receive no email until the project is reopened.
In app options
Notification
Appears in the Notifications tab with a red badge counter
Indicate Activity
Added to the Activity tab as a counter
Off
Not shown anywhere
How notifications appear
In-app notifications appear in two places:
A red badge on the profile avatar in the main menu shows the unread Notifications count
Clicking the profile avatar opens the notification bar on the Notifications tab
The Notifications tab shows notification details
The Activity tab shows items configured as Indicate Activity
Use the filters at the top of the Notifications view to control what you see:
Only unread shows unread items only
Show all includes read items
Mark all as read clears the unread count
Grouped view
Use Grouped to reduce noise from repeated events on the same item.
Grouped view combines related events into one notification thread instead of showing each event separately.
This works well for high-activity records, such as customers or projects with many updates in a short period.
Open the grouped notification to review the latest change without scanning a long list of near-duplicate alerts.
How to configure notifications
What you can change on this screen
Each notification group opens a list of event types.
For each event, you can set the channel behavior individually.
You can also:
Click an In app column header to update all events in that group at once
Use + Add event to add another event to the current eligible group
Use + New notification group to create a custom group
Add event
+ Add event lets you add event types that are not included in a notification group by default.
You can also add a filter so the event only triggers for specific items.
For example, you can notify only for customers in a specific segment.
+ Add event is only available in Account notifications for eligible groups.
It is not shown for every group.
Groups that already reference a base group do not show + Add event.
New notification group
+ New notification group lets you create a custom notification group for a specific subset of items.
This takes two steps:
Pick an entity type: Customer, Project, Task, or Comment
Choose the scope:
All — all items of that type in the account
Team — items assigned to the team
Custom — define a name and add a filter to control exactly which items trigger notifications
Not every entity type supports every scope option.
For example, some entity types may only show Custom.
Use this when the standard groups are too broad.
For example:
enterprise customers only
projects in the onboarding phase only
How defaults work
Default for new event types controls what happens when Startdeliver adds a new event to an existing group.
If it is set to Auto, new event types use the system default.
Change it when you want to override that default before new event types appear.
For example, set it to Off if you want future event types in that group to stay muted automatically.
Common scenarios
We want account-wide defaults, but teams need flexibility
Set the broad baseline in Account notifications. Then let each team adjust only the groups that differ for their workflow.
A user wants fewer notifications than the rest of the team
Keep the team settings as they are. The user can reduce noise in Your notifications without changing anyone else.
We want to avoid noise from future event types
Set Default for new event types to Off in the relevant group. New events in that group stay muted unless someone enables them later.
We need a focused notification set for one subset of customers
Create a + New notification group and use a Custom scope with filters. This works well for cases like enterprise customers, renewal-risk accounts, or any segment your team wants to watch closely.
Last updated
Was this helpful?

