# 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:** 7
**Author:** ![clay](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/clay/32/102156_2.png) [@clay](https://meta.discourse.org/u/clay)\ **Post date:** [September 29, 2015, 3:03am UTC](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857/7 "2015-09-29T03:03:36Z")
That is precisely how we use it, intranet only. Our work is primarily project-based, sometimes with projects under NDA, so we have a Projects category and tend to create access-restricted subcategories of Project for individual project work. We also have broader topics that cover thematic issues that span projects, such as “Health Care,” “Criminal Justice,” etc. _Sometimes_ we use wiki posts at the top of topics. For instance, we have dozens of internal prototypes and tools running on various ports of a dev machine. We use a wiki post in a pinned topic to track which ports are in use for which project. In general, I find the wiki posts to be less useful for larger discussions. Overall, Discourse is a huge hit at my company. --- _[View the full topic](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857)._