Notification Bankruptcy
Every tool that adds notifications eventually reaches the same end state: everyone turns them off. The first few weeks feel useful — you know when tasks are assigned, when comments are posted. Then the volume grows. Automated updates, status changes from integrations, replies in threads you loosely watched three months ago. The red badge becomes a meaningless number. You stop reading, stop trusting, and check the board manually instead.
The notification feature has failed. Not because it was poorly implemented — but because it wasn’t designed around the signal-to-noise problem from the start.
What Actually Needs Your Attention
There are roughly four categories of notification, ranked by urgency:
- Direct asks — someone @mentioned you, assigned a task to you, or replied to your comment. You need to respond.
- Watching signals — a task you’re explicitly tracking changed state. You chose to care about this.
- Flow activity — things are happening in your team’s work. Useful for awareness, not urgent.
- System noise — automated status transitions, bulk imports, integration syncs. Almost never actionable.
Most tools treat all four categories identically. A ping for every automated transition trains you to ignore every ping, including the ones that matter.
How FlowEra Handles This
FlowEra’s notification system is built around explicit subscription. You are notified by default only when:
- A task is assigned directly to you
- You are @mentioned in a comment or message
- A task you’re a participant on is marked complete
Everything else — flow activity, task updates, comment threads — requires you to explicitly subscribe. Open a task and click “Watch”. Open a flow and choose your notification level. The system doesn’t assume you care about everything just because you have access to it.
Grouping and Deduplication
When FlowEra does notify you, it groups related events. If ten tasks in the same flow were updated while you were away, you get one notification: “10 tasks updated in Sprint 7”. Not ten separate pings. Clicking the group shows you the breakdown.
Consecutive mentions in the same thread are collapsed. A conversation that generates 15 replies surfaces as one notification with a reply count.
The @mention is Sacred
Because FlowEra keeps the default notification level conservative, @mentions stand out. When someone @mentions you, it means they need you — not that the system generated an event that happened to include your user ID.
We deliberately don’t allow integrations to generate @mentions. If your CI/CD pipeline wants to notify the team, it posts to a channel or updates a task status. It doesn’t @mention you. The @mention stays a human-to-human signal.
Notification Channels
FlowEra delivers notifications in-app, with email digest as an optional opt-in for users who prefer async review. We don’t push email by default — most people on a team are in the tool regularly enough that in-app is sufficient.
Push notifications for mobile are on the roadmap.