# Feature Request - Content Moderation

**URL:** <https://discourse.getcockpit.com/t/feature-request-content-moderation/163>\
**Category:** General\
**Created:** [July 18, 2018, 8:36pm UTC](https://discourse.getcockpit.com/t/feature-request-content-moderation/163 "2018-07-18T20:36:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![waywardm](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/waywardm/32/59_2.png) [@waywardm](https://discourse.getcockpit.com/u/waywardm)\
**Post date:** [July 18, 2018, 8:36pm UTC](https://discourse.getcockpit.com/t/feature-request-content-moderation/163/1 "2018-07-18T20:36:52Z")

</div>

Would be nice to have the ability so set a piece of content to draft, published or archived without having to set up a field type to do the same job. Which then could be filtered on the api.

---

<div class="post-metadata">

**Author:** ![pauloamgomes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/pauloamgomes/32/48_2.png) [@pauloamgomes](https://discourse.getcockpit.com/u/pauloamgomes)\
**Post date:** [July 24, 2018, 8:19am UTC](https://discourse.getcockpit.com/t/feature-request-content-moderation/163/2 "2018-07-24T08:19:50Z")

</div>

That sounds interesting, mostly if we could have the following scenario:

1. User creates a new entry with published state
2. The entry is included when collections are fetched
3. User creates a new revision in draft state
4. The previously published revision of the entry is returned when collections are fetched
5. User creates a new revision in unpublished state
6. The entry is filtered out when collections are fetched