Some actions require human approval — e.g. image uploads for a UGC campaign, free-text answers for quality control, or achievement claims with verifiable evidence. Nudj has a dedicated review flow (#1195) for admins to work through these submissions.
Where to find it
Admin panel -> Engagement -> Review Queue (or via individual action analytics).
Queue view
Pending submissions show up as rows with:
- Member (username + profile link)
- Action (which challenge, which action)
- Submission preview (thumbnail for images, excerpt for text)
- Submitted at timestamp
Approve / reject
Click a row to open the full submission:
Marks the submission valid. Member’s action counts as complete; any attached reward distributes.
Member’s action fails. They can retry (if the challenge allows) or the challenge fails for them.
Send a short message to the member with the decision — useful for explaining rejections.
Bulk review
Select multiple rows and bulk-approve / bulk-reject. Useful for clearing out a backlog after a big UGC campaign.
Bulk reject is permanent per-member. Make sure you’re actually rejecting, not just batch-clearing stale data. Use archive for the latter.
Configuring review-required actions
Moderation on an action is a config flag in the action editor. See Rich Media Actions for image moderation, and question-actions for free-text moderation settings.
Best practices
Set an SLA internally — e.g. “we’ll review submissions within 24 hours”. Tell members in the challenge description. They expect feedback.
Use the message action for rejections — a one-line explanation beats a silent no. Members who understand “why” are more likely to try again.
For high-volume UGC, use object detection (automated) instead of manual review — faster, cheaper, and scales.