# Staged users' posts stuck in queue

**URL:** https://meta.discourse.org/t/staged-users-posts-stuck-in-queue/412025
**Category:** Self-hosting
**Created:** [September 9, 2026, 6:37pm UTC](https://meta.discourse.org/t/staged-users-posts-stuck-in-queue/412025 "2026-09-09T18:37:04Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [September 11, 2026, 4:17pm UTC](https://meta.discourse.org/t/staged-users-posts-stuck-in-queue/412025/9 "2026-09-11T16:17:18Z")

</div>

I tested this on a current self-hosted instance.

Staged users are not members of `trust_level_0`, so having `trust_level_0` in `skip review media groups` does not exempt them.

However, adding `logged_in_users` to `skip review media groups` does.

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/4/e/94e6adde473938147d60bf780a411270a0591b02.png)

I tested this both directly against `NewPostManager` and through the real email-in path. An email from a newly-created staged user containing embedded media was posted immediately instead of going to the review queue.

So for a helpdesk-style setup where arbitrary new senders are created as staged users, adding `logged_in_users` appears to provide the intended behaviour without needing to activate the users or maintain a separate group.

One slightly surprising detail is that staged users match the `logged_in_users` pseudo-group for this check even though they are not activated/logged-in accounts in the usual sense.

---

_[View the full topic](https://meta.discourse.org/t/staged-users-posts-stuck-in-queue/412025)._
