# Needs Approved Reject doesn't Unblock or associated the rejected post with the user

**URL:** <https://meta.discourse.org/t/needs-approved-reject-doesnt-unblock-or-associated-the-rejected-post-with-the-user/33989>\
**Category:** Product Support\
**Tags:** approval\
**Created:** [October 1, 2015, 11:31am UTC](https://meta.discourse.org/t/needs-approved-reject-doesnt-unblock-or-associated-the-rejected-post-with-the-user/33989 "2015-10-01T11:31:20Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [October 20, 2015, 12:28am UTC](https://meta.discourse.org/t/needs-approved-reject-doesnt-unblock-or-associated-the-rejected-post-with-the-user/33989/24 "2015-10-20T00:28:10Z")

</div>

It depends, if you want to micromanage every new post by every new user, then it might be better to have someone in charge of simply reading every post that’s made every day?

In other words, read the posts in the topics with full context… and if you don’t like the post, edit it or delete it.

The goal of approval is to prevent **really bad** stuff like spam, super hateful content, etcetera from new users – where the difference is stark, black and white, good and evil, not the shades of grey of “is this good enough?” In other words, to prevent unspeakable evil from appearing on your site, ever, not just a mediocre or badly written post. The implied post approval queue question is, “how bad does this post hurt your site if it is allowed to appear there?”

Approval is not really meant as a general post quality check. if you are doing post quality checks, I suggest doing them by reading all new posts / topics every day.

---

_[View the full topic](https://meta.discourse.org/t/needs-approved-reject-doesnt-unblock-or-associated-the-rejected-post-with-the-user/33989)._