# More Robust Slack Notifications

**URL:** <https://forum.buildkite.community/t/more-robust-slack-notifications/892>\
**Category:** Features Requests\
**Created:** [January 30, 2020, 3:44pm UTC](https://forum.buildkite.community/t/more-robust-slack-notifications/892 "2020-01-30T15:44:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rludwick](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/rludwick/32/723_2.png) [@rludwick](https://forum.buildkite.community/u/rludwick)\
**Post date:** [January 30, 2020, 3:44pm UTC](https://forum.buildkite.community/t/more-robust-slack-notifications/892/1 "2020-01-30T15:44:29Z")

</div>

My team could really use more robust capabilities when it comes to the Slack notifications. Specifically:

- At the organizational settings level, it would be nice to be able to also include **tags** in the branch filtering scheme.
- The ability to define what your Slack username is per configured Slack workspace, such that Buildkite can DM you when your personal builds or starred branches succeed/fail according to normal notification selections (always, only for failed/fixed, etc).
- The ability to override the organizational Slack settings on a per-pipeline basis
  - I know this is generally possible through pipeline steps, but that’s a bit more cumbersome and requires collecting together all of the other build steps to determine failure - something that Buildkite already does itself; this kind of logic doesn’t belong in a pipeline