# Configurar notificações do Slack usando o plugin discourse-chat-integration **URL:** \ **Category:** Integrations\ **Tags:** chat-integration, how-to\ **Created:** [24 Julho , 2017 16:45 UTC](https://meta.discourse.org/t/set-up-slack-notifications-using-the-discourse-chat-integration-plugin/66730 "2017-07-24T16:45:28Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\ **Post date:** [26 Setembro , 2017 23:52 UTC](https://meta.discourse.org/t/set-up-slack-notifications-using-the-discourse-chat-integration-plugin/66730/15 "2017-09-26T23:52:46Z")
> [@pfaffman](#): > > It still seems a bit wild that any slack user can change what Discourse stuff gets posted to a channel I think it depends what kind of community you have in Slack. In my mind there are three main scenarios: - If any member of the public can join your Slack organisation, Slash commands probably aren’t a good idea. In this case it’s probably easiest to just manage the rules from the discourse admin panel. - If you have a fairly open forum, but a closed slack organisation (like I believe the discourse team do), then having slash commands is a nice convenience without any real issue (everyone in slack is trusted). - If you have a roughly 1:1 mapping between forum members and slack members (e.g. a corporate environment), it can be useful to allow individuals to manage the rules in their own slack channel. For example, the dev team might want to watch #Development, and the support team #Support. Rather than forcing all this to be done by a discourse admin, they can do it themselves with slash commands. I think this is how @mcwumbly uses slack integration. --- _[View the full topic](https://meta.discourse.org/t/set-up-slack-notifications-using-the-discourse-chat-integration-plugin/66730)._