# Discourse for Teams כאן!

**URL:** <https://meta.discourse.org/t/discourse-for-teams-is-here/168390>\
**Category:** Blog\
**Created:** [27 באוקטובר,‏ 2020,‏ 2:00pm UTC](https://meta.discourse.org/t/discourse-for-teams-is-here/168390 "2020-10-27T14:00:18Z")\
**Posts on this page:** 1\
**Showing post:** 52

<div class="post-metadata">

**Author:** ![Holger\_Winkelmann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/holger_winkelmann/32/210442_2.png) [@Holger\_Winkelmann](https://meta.discourse.org/u/Holger_Winkelmann)\
**Post date:** [20 בפברואר,‏ 2021,‏ 4:55pm UTC](https://meta.discourse.org/t/discourse-for-teams-is-here/168390/52 "2021-02-20T16:55:51Z")

</div>

HI, we are currently a Slack user for all internal Communication suffering the Slack disease, means instead of slack is used as notification and “quick Chat” channel people tent to use slack for everything which wold be better and more durable be documented in Documents, wikis or other place like issues. For me a forum style communication would be a good middle ground wich gives a more persisted information by maintaining an open discussion. Discourse Teams seems even more to bridge both.

Why I’m asking about the API or Integration aspects, Despite the typical Ticket Systems we must operate for our Enterprise Customers for formal SLA aware Support I would also like to have a more informal way of communication and engagement. Something a Discourse Instance could deliver us IMHO, We still would need to set up some permission system for Topics or so, but in general this could work.  
For more informal Conversations we cold also think about Chat based conversational support, But our discussion might outrun what fits in chat window and scrolls out and get forgotten. We tested to give Customers Guest access to slack channels, but after length over chat time, the content get rottet and is hard to back reference qualified follow up.

Now I’m wondering how a Tandem of Discourse Teams, replacing the Internal Slack Hell, and a External assessable Community Platform can work together, and may even a tool like [fibery.io](http://fibery.io) could cross connect all this things together by using API access to discourse which is already directly supported.

hope the use case is somehow understandable?

BR,Holger

---

_[View the full topic](https://meta.discourse.org/t/discourse-for-teams-is-here/168390)._
