Skip to main content

Approving posts before they appear

On a Team plan, hold posts for review so nothing reaches your attendees until you have seen it.

Written by Cyril Fluck

On a Team plan you can hold posts for approval. Nothing anybody else posts appears on the page until an admin has seen it and said yes.

This applies to Social Feed, Announcements and Crowd Pics pages.

Turning it on

Click the gear icon next to the page in the Editor's page list and choose "Admin must approve".

Publish your app for the change to take effect. Until you publish, posts carry on appearing immediately.

The Editor's settings panel for a social feed page, showing the option to require admin approval for posts and comments.

Approving or rejecting a post

When somebody who is not an admin posts, you get a push notification. Open it and you can approve or reject.

Yapp on a phone showing what an admin sees for a post awaiting approval, with approve and reject options.

Once you approve it, it appears as a normal post and everybody gets the usual notification.

What the person who posted sees

They see their own post marked as pending. They know it went through and that it is waiting, so they are less likely to post again thinking it failed.

Yapp on a phone showing an author their own post marked as pending while it waits for approval.

While a post is pending, its author cannot edit it. Once it is approved, they can.

If you have several admins

Whoever acts first decides. If a team member approved something you would not have, you can still delete it. If one of them rejected a post before you saw it, it never appears.

With a team covering a live event, it is worth agreeing who is watching the feed and when, so posts do not sit pending for an hour.

Choosing how much to moderate

Most events need none of this. It is worth deciding in advance anyway, because the choice is much easier to make before the event than during it.

Deleting afterwards suits most apps. Posting stays immediate, which is what makes a feed feel alive, and you deal with the rare problem when it appears. The cost is that whatever went up was visible until you noticed, and notifications for it have already gone out.

Reviewing first suits an audience you do not know, a public event, or anything where a single bad post would be a real problem — sponsors in the room, press, students. The cost is that every post waits for an admin, so somebody has to be watching. A feed where posts take an hour to appear stops being used.

If you are unsure, start with deleting afterwards. Turning review on later takes one setting and a publish.

Reference

Did this answer your question?