I see. What I don&#x27;t understand is why settings need to be so granular.<p>For example, our company uses Slack. All notifications go to Slack. There&#x27;s no need for per-project settings because it&#x27;s all just one room. At some point we will probably want some projects to go to other rooms, but that&#x27;s a coarse-grained exception, not something that warrants a per-project setting.<p>Also, if you need per-person notification settings, then surely that&#x27;s part of the user&#x27;s account&#x2F;profile, not the project. That would be just a single dashboard page with (say) on&#x2F;off sliders for each project.<p>In my mind, the data model used by exception trackers (including, it seems, Sentry) is wrong. There needs to be just one stream of events, tagged by things like application name that you can filter on. How those events map to things like notifications and aggregations and rules and source files and teams and so on is completely orthogonal to the stream. Those things then apply to a subset that you can modify dynamically without having to reconfigure the sender.