Review Settings

Review incoming requests before an activity is created and shared in a channel

In some instances you may want to review an incoming request before creating an activity channel and inviting team members. For examples, if you receive bug reports you may want someone to look through the incoming report and make adjustments before sharing the bug report with the entire support team.

Another common use of reviewers is to perform a manual review of external webform inquiries (with or without a reCAPTCHA filter).


Conclude provides several review settings to create such a review process:

  • members: the members of the review team.
  • alert: where to send alerts about incoming requests that should be reviewed.
  • ignore: requests from these people should not go through a review process, but be sent directly to the team.
  • include: requests from these people should always be reviewed.
  • createChannel: set to true to always create a Slack channel for incoming activities.

Note: The review members list must not be confused with the members who are invited to the activity after it has been accepted by the review team.

Conclude lets you define one or more reviewers, who must first accept the activity before it is shared with the team. An incoming activity will be marked as pending until a reviewer has accepted (or rejected) it. A reviewer may also modify the incoming request before accepting it.

By default, Conclude does not create Slack channels for pending activities. You can set createChannel to true to always create a channel for pending activities. This lets the reviewers discuss the incoming activity in the channel before accepting or rejecting it.

Pending activities appear in the reviewers’ Conclude Home Dashboard and Activity pages, and in Conclude Dashboard.

  members: "@paul, @sarah"
  alert: "#incoming-bugs"

When one of review.members has approved the request, it is shared with the activity members (see roles).

You can specify any number of individual users, channels and user groups to be part of the review team.

We recommend that you also set review.alert to notify reviewers about incoming activities that need to be reviewed. This special alert message comes with buttons that let reviewers view, edit and accept (or reject) a pending activity with a single click.

You can also skip the review process when a request comes from certain people. For example:

  members: "@paul, @sarah"
  alert: "#incoming-bugs"
  ignore: "#dev, @management"

Here we let bug reports from members of the #dev channel and @management user group go directly to the team without a review process.

In other instances you may want to do a review if the initiator is outside your team:

  members: "@paul, @sarah"
  alert: "#incoming-bugs"
  include: "@contractors, external"

Incoming bug reports will be reviewed if they come from anyone who belongs to the @contractors user group, or from external sources (a webform or email).

The special keyword external means anyone outside your Slack workspace, and internal means anyone inside (including guests).

Connect. Collaborate. Conclude