# Using Discourse as a internal Knowledge Base / Intranet **URL:** \ **Category:** Feature\ **Created:** [September 28, 2015, 9:01pm UTC](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857 "2015-09-28T21:01:47Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![jaevanryssel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jaevanryssel/32/86830_2.png) [@jaevanryssel](https://meta.discourse.org/u/jaevanryssel)\ **Post date:** [January 25, 2018, 9:00pm UTC](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857/20 "2018-01-25T21:00:00Z")
> [@Ryan\_Nix](#): > > One of the concerns against using Discourse is that there aren’t a lot of examples of Discourse being used internally. I recommend to check out this topic thread if you haven’t already: > [@Discourse and Slack (or other group chat apps like IRC, HipChat, Gitter, etc)](https://meta.discourse.org/t/discourse-and-slack-or-other-group-chat-apps-like-irc-hipchat-gitter-etc/39630): > > Discourse vs. Slack Finding the right place for a discussion On Slack, discussions are separated into different channels. This shares many of the same problems as groups in email - it’s not clear which channels exist, which ones are still active, and where a particular discussion should take place. On Discourse, discussions will be visible to everyone so it doesn’t matter as much which category you choose when a topic is created. And if it seems like a topic should later be moved to another cat… --- _[View the full topic](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857)._