Notification settings in a business web app: who gets what
Short answer: Specify notifications as a grid: every event your app can raise down one side, every channel (email, SMS, in-app, push) across the top, and a default in each cell. Start quiet, let people turn things up, offer a daily digest for anything non-urgent, and add quiet hours for SMS and push. Behind the page, keep a log of what fired, to whom and why, so you can answer "why didn't I get told?" in seconds.
Notification settings tend to be left until the end of a web app project, and then they're one checkbox: "Email us about activity". Six months later, the operations team is drowning in emails about every status change, while a manager complains they never heard about the one that mattered. A small amount of design up front prevents both. Below is a blueprint you can hand to whoever builds your portal or internal tool.
Part 1: List the events
Before thinking about channels, write down every event the app could tell someone about. For a job-management portal, a hypothetical list might be:
- A new job is assigned to you.
- A customer replies to a job you're on.
- A job is overdue.
- A quote is approved or rejected.
- An invoice is paid.
- A weekly summary is ready.
- Your password was changed or a new device signed in.
Mark each event with its urgency (act now, today, or for information) and its audience (the person involved, their manager, everyone with a role). These two labels decide most of the defaults later.
Part 2: The event-by-channel matrix
Build a table with events as rows and channels as columns. Each cell holds one of: on, off, digest, or locked (always sent, can't be turned off).
| Event | In-app | SMS | Push | |
|---|---|---|---|---|
| Job assigned to you | On | On | Off | On |
| Customer reply on your job | On | Digest | Off | On |
| Job overdue | On | On | On (business hours) | On |
| Quote approved/rejected | On | On | Off | Off |
| Invoice paid | On | Digest | Off | Off |
| Weekly summary | — | On | — | — |
| Password changed / new sign-in | On | Locked | Off | Off |
The table above is an example, not a recommendation for every business; the point is that every cell is a decision someone has made on purpose.
Choosing channels
- In-app is the cheapest and least intrusive. Almost every event belongs here, as an item in a notification list with a badge.
- Email suits things people need a record of, or will act on later.
- SMS costs money per message and interrupts people. Reserve it for genuinely time-critical events.
- Push (on the web or in a mobile app) needs the person's permission. MDN's guide to the Notifications API advises requesting that permission only in response to a user action, such as clicking a button, and notes that browsers increasingly block requests that aren't. So the preferences page, not the first login, is the natural place to ask.
Part 3: Defaults that don't spam
Defaults matter more than options, because most people never visit the settings page.
- Start conservative. Turn on only the events directly about the person's own work.
- Never repeat the same alert. Apple's notification guidelines warn against sending multiple notifications for the same thing even if someone hasn't responded, because people may then switch off notifications from the app entirely. The same holds for email and SMS.
- Group bursts. Ten comments in five minutes should become one notification, not ten.
- Keep them short and useful. The same guidelines ask for concise, informative notifications. "Job #2318 is overdue: boiler service, Mrs Patel, due 2 pm" beats "You have a new update".
Part 4: Digests versus instant
Offer a digest option for anything marked "today" or "for information":
- Let each person choose daily or weekly, and the time it arrives.
- Include only events that haven't already been read in the app.
- Send nothing when there's nothing new. An empty digest teaches people to ignore the next one.
Part 5: Quiet hours
For SMS and push, add quiet hours per person, with a sensible default such as evenings and weekends for office roles. Events during quiet hours either wait until the window ends or go to email instead. Allow a small number of events to override quiet hours if your business genuinely needs it (an on-call engineer, for example), and make that override visible in the settings.
Store the person's time zone with their profile, so quiet hours still work for staff or customers outside the UK.
Part 6: Role defaults
A dispatcher, an engineer and a finance manager need different defaults. Define a default set per role, apply it when someone joins, and let individuals adjust from there. When you change a role's defaults later, decide whether to update existing users or only new ones, and say so in the release notes.
Managers often want to be told about their team's events. Make that an explicit setting ("Notify me about overdue jobs for my team") rather than copying managers on everything.
Part 7: Transactional versus marketing
The preferences page should keep two groups clearly apart:
- Service messages about the person's account and work. Security alerts should usually be locked on; most others can be adjustable.
- Marketing and product news. These need their own opt-out, separate from the service settings.
Email providers support this split. Twilio SendGrid, for example, describes group unsubscribes, which let a recipient opt out of one type of email via a link while still receiving others. Whatever tool you use, the app's own preferences and the provider's unsubscribe lists must stay in sync, or someone will unsubscribe in one place and keep getting emails. What consent you need for marketing messages depends on where you operate, so check the rules for your situation.
Part 8: The page itself
- Group settings by topic (Jobs, Quotes, Billing, Account), not by channel.
- Show the matrix as toggles, with "digest" as a choice in a dropdown where it applies.
- Put a "Pause all non-essential notifications" switch at the top, with an end date.
- Show a short note beside locked items explaining why ("for your security").
- Add a "Send me a test" button for push and SMS.
Part 9: The audit log
Record every notification decision: event, recipient, channel, whether it was sent, held for quiet hours, bundled into a digest or suppressed, and why. Give support staff a filtered view per user. This turns "I never got told" from a guessing game into a two-minute check, and shows when a default needs to change.
FAQ
Should users be able to turn off every notification?
Most, yes. Keep a small set locked on, mainly security and account-critical messages, and explain why next to each one.
How many channels should we support at launch?
In-app and email cover most needs. Add SMS or push when there's a clear time-critical event that justifies them.
Who should own the defaults?
Someone in operations, not just the developer. Review them a few weeks after launch using the audit log.
Can we change defaults after launch?
Yes. Decide whether changes apply to everyone or only new users, and tell people when it affects them.
A clear notification spec saves arguments later, and we can help you map the events and defaults for your portal before it's built.