# Using Discourse as a internal Knowledge Base / Intranet

**URL:** https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857
**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:** 29

<div class="post-metadata">

### Author: ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)
#### Post date: [October 7, 2020, 7:21pm UTC](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857/29 "2020-10-07T19:21:30Z")

</div>

> [@misterjtc](#):
>
> Version control with rollback

This is built into Discourse-core version edit history.

> [@misterjtc](#):
>
> Approval/pull request type pipeline for certain items

You can set topics to require moderator approval for new topics in a category. We do not have this feature in core, but there’s an open feature request for it.

> [@Require staff approval for wiki edits in selected categories](https://meta.discourse.org/t/require-staff-approval-for-wiki-edits-in-selected-categories/130222):
>
> I would like to see something to keep some category’s topic edits under control. In my community we have todo/guide category with staff “seal of approval”. We want to make all topic in this category wiki mode for community to be able to update guides but then we don’t have under control what changes are being made. Option in category settings to require staff or selected group approval would be much appreciated slight_smile

This would not be for the topic creator, however. Only staff could approve posts.

---

_[View the full topic](https://meta.discourse.org/t/using-discourse-as-a-internal-knowledge-base-intranet/33857)._