• All Files

Moderating (Approving/Rejecting) Posts

Moderating Posts

AVAILABLE TO: By default, this feature is initially available only to Administrators and Employees, because they have status as moderators. However, when configuring the privacy settings for the community (i.e., system), you can assign moderation rights to other groups as well. See Using the Systems Menu.

New Pulse communities will initially be set for moderation (i.e., requiring approval of new posts). If you have a community that does not have this option set, you can select it in the Pulse dashboard. Moderators will receive an email notification when there is a new post pending approval. You can then click the link to that topic and accept or reject the post.

ClosedModeration Actions by User Group

The moderation tasks that can be performed depend on the user group.

Moderation Actions

General Public

Customer

Employee

Administrator

Post Comments (must have approval)

Post Comments (without approval

See Pending Comments

See Rejected Comments

Approve Comments

Reject Comments

Delete Comments

Closedhow to moderate posts
  1. Log in to the Pulse dashboard.

  2. Select Systems > Find Systems. Then click the desired system link to configure it. The system page appears.

  3. In the system page, click Settings.The system's Feed Settings page opens.

  4. On the Basic tab, select the Moderation check box.

  5. Click Save.

  6. When a user posts to a topic, you will receive an email notification stating that the post is pending approval. Click the topic link in the email. You should see an icon indicating that the post has a pending status.

  7. Depending on what you want to do, click Approve or Reject.

  8. If you select "Reject," choose a reason from the drop-down that displays, and click Reject Activity. (Administrators can configure rejection reasons, adding as many as you need. See Configuring Moderation—Rejection Reasons.)
Closednotes

Note: All moderators will receive email notifications when new posts require approval. However, any moderator can update his or her email notifications to not receive those types of emails (e.g., one administrator might be in charge of post approvals, whereas a second administrator might be responsible for other tasks and doesn't need to be informed of new posts). See How to Sign Up for Notifications.

Note: If you opt to moderate all of your posts, there is no need to subscribe to them as well since you will automatically receive emails with the moderation feature. However, if you decide not to use the moderation feature, it is recommended that you subscribe to all of your topics globally so that you are informed whenever someone posts to that topic.

Keep in mind that, with the global subscription route, email notifications are tied to each community, whereas the moderation route sends email notifications to all moderators, regardless of the community where the post was made. For example, let's say you've got two documentation groups (Group A and Group B) producing different Flare outputs. Suppose someone in Group A creates a Pulse community associated with his Flare output and publishes it. In addition, that person chooses the option to moderate posts for that community. Whenever an end user posts a comment to that Flare output, all moderators in both Group A and Group B will receive a notification about that post. That might be fine for the moderators in Group A, but the moderators in Group B may not want to see those emails, because they have nothing to do with any of their outputs. There are two options to avoid this kind of situation. First, you can install Pulse on two different servers—one for Group A and the other for Group B. Second, you can make sure all communities are using the global subscription method instead of moderation; so you'd be giving up moderation, but you'd be able to work off the same server and you'd only receive email notifications for the communities to which you've subscribed.