Moderate content

Moderation gives your team a chance to review feedback before other people see it. You can require approval for new requests or comments, check for sensitive information, and review content flagged as possible spam or abuse.

Workspace admins and owners handle reviews in the dashboard. They can also review comments from the public request page.

Choose what needs review

Open Settings, then go to Privacy. Under Public board, you can turn on:

These settings are available on Starter and above. Turning off a setting does not approve content that is already waiting for review.

Admins and owners bypass the manual approval requirement. Sensitive-information checks still apply to their requests and public comments when enabled.

Automatic spam and abuse checks

UserJot checks requests and comments for possible spam and abuse. Flagged content can move into review even when you have not required manual approval for every post.

Abuse includes personal attacks, harassment, threats, and targeted slurs. Customers can still criticize your product or express frustration. A report that quotes an abusive message is different from directing abuse at someone.

Automatic checks can make mistakes. Your team decides whether flagged content should stay.

Check for sensitive information

With Detect sensitive information enabled, UserJot checks feedback text and uploaded JPEG, PNG, and WebP images for private details such as credentials, financial information, and personal disclosures. Feedback stays out of public view while the check runs.

An unsupported or unreadable image may need manual review. Other attachment types are not checked. Detection can miss sensitive information, so review the content yourself before publishing it.

Review a request

Open the request in the dashboard. The Needs review panel shows why it is waiting and the actions available.

For possible spam or abuse:

If another reason remains after you choose Keep, the request still needs review. For example, it may also contain sensitive information.

For manual review or sensitive information:

You can edit the title or description directly before making a decision. Wait for the changes to save and any new checks to finish. If someone changes the request while you are reviewing it, review the latest version before trying again.

A request's workflow status is separate from moderation. Accepting it, planning it, or closing it does not resolve a review. See triage requests for the workflow and make a request private for visibility.

Review a comment

Select the orange Review button beside Reply to see the reasons and actions. The dropdown works in the dashboard and on the public request page when you are signed in as an admin or owner.

Comments flagged as possible spam or abuse offer Keep and Delete. As with requests, Keep clears those findings while leaving any other review reasons in place. Delete asks for confirmation.

For other comment reviews, choose Approve to allow the comment, or Don't publish to leave it unapproved. Don't publish keeps the comment for your team to review later; it does not delete it.

Approving a comment does not make its request public. The request and any parent comment must also allow it to appear to other people. To keep the whole discussion private, change the request's visibility.

When a check cannot finish

If a check fails, the review control shows Check could not finish. Choose Retry check to try again. The content stays out of public view until the check or an admin review resolves it.

What the author sees

Authors may see Checking your feedback or Pending Review after submitting. Their feedback has been received, but it is not public yet. Detailed review reasons and moderation actions are visible only to admins and owners.

The widget also confirms receipt without promising that the feedback has been published. See guest feedback for how guests return to their own posts.