# 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:** 25

<div class="post-metadata">

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

</div>

> [@codinghorror](#):
>
> 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?”

Exactly, that is what I’m hearing and for us, we are getting “fluff” in there more than spam, and sometimes when we approve said fluff, Akismet then picks it up. So I really think Akismet is our preferred Spam solution and we really have zero use for the Post Approval process.

Their are plenty of “staff” on our instance that if there is a really poor quality post, we can handle it quickly or at least refute it publicly (if need be to provide the OP with better knowledge). We are just finding our work cumbersome now with Post Approval because Reject doesn’t unblock the user, so we manually have to do that, and/or, we have to go to the Post Approval area, read the post, go to the thread, re-read the thread, then act. Versus, if the post wasn’t picked up by Akismet, we see it in the thread and deal with it there (much easier workflow – for us).

Right now it is two systems that are not working with each other, and causing us more effort as a lot of New User posts get into that queue and then they have to wait for us to figure out what to do with it (which is proving to be difficult for us since we get a lot of “grey” related posts there).

---

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