The app configuration defines the overall behavior of the app.

typeDecides who can use the app (custom: channel members, global: anyone)
nameApp name; lower case letters, numbers and underscores (just like Slack channels)
labelA short text to describe the app, used when sending alerts and more
descriptionA longer text that explains the purpose of the app
ownerDefault owner of an activity, see roles
membersList of participants to invite to an activity, see roles
reviewersReview an activity before sharing it internally, see roles
adminsUsed for managing Slack permissions, see roles
superusersUsed for restricting access to attributes, see roles
privateLimits access to the source code of an app, see roles
alertWhere to send alerts about an activity, see below
alert_reviewersWhere to send alerts about a pending activity, see below
notificationsWhen to send notification about changes in an activity, see below
channel_nameSets a custom activity channel name instead of #_myapp-*, see below
disable_deadlineSet this to true to remove the ability to set a deadline
disable_severitySet this to true to remove the ability to set a severity level
rate_limitLimits the maximum number of activities that can be created every minute
web_connectorAccept incoming activities from a web form using http POST


The app type specifies who should be the audience for the app. Set it to global to allow anyone in your Slack workspace, including guest users, to use the app, even if they are not a member of the channel where you installed the app. One common use case is to install global apps in a private channel. Anyone can create a new activity, for example report an incident, but only app members are able to follow the internal discussion.

Setting the type to custom will make the app available only to the members of the channel where the app is installed.

Go to Conclude Home > Apps or type /c to see which apps are available to you.


The app name is similar to a Slack channel name. Instead of launching an app from the Conclude Home > Apps you can type the command: /c <app-name>

Apps should have unique names (otherwise the /c command would not know which app to launch).


The app label is a short text describing the app, and used when presenting information about an app or an activity.


The description is a longer text that explains the purpose of the app. It’s used on the Apps page.

Owner, members, admins and superusers

These settings define user roles. You’ll find more information about roles here.


The private setting restricts access to the app’s source code, see roles.


An app sends out an alert whenever a new activity is created, concluded, or reopened. The alert setting specifies who the alert should be sent to.

  "alert": "#mychannel"

The installer sets the default alert value to the channel where you installed the app. If you leave out the alert setting then nobody will receive alerts about the activity.

Like for the member setting described in roles, there’s no limit to how many individual users, channels or user groups you can specify for the alert setting.

You may want to send alerts to a different channel than where you installed the app. For example, for an incident management app installed in the #incidents channel, you can do the following:

  "alert": "#incident-log"

Alert messages about the activity will be sent to the #incident-log channel instead of the #incidents channel where you installed the app. This is a good way to reduce noise.

Alert reviewers

This setting will only have an effect if you have reviewers. See roles for more information.

Set alert_reviewers to notify reviewers about incoming activities that need to be reviewed. This special alert message contains buttons that let reviewers view or accept a pending activity with a single click.

  "reviewers": "@paul, @sarah",
  "alert_reviewers": "#incoming-requests",


By default, Conclude apps send notifications to the activity channel when the owner, deadline or severity attribute change.

You can override this and instruct Conclude to send channel notifications when certain attributes change:

  • owner, deadline, severity: Send a notification if any of these attributes change.
  • attribute: Send a notification when any attribute changes.
  • none: Never send channel notifications.

You may also set notification for specific attributes. If want channel notification whenever the deadline or an attribute named ‘decision’ changes, you can set:

  "notifications": "deadline, decision"

Channel name

Conclude will create a channel with a unique channel name for every activity, based on the name of the channel where you installed the app.

If you install an app in #incidents, the activity channels will be named #_incidents-1, #_incidents-2 etc. If there is an existing channel with the name, Conclude will use a random suffix, for example #_incidents-2ba3.

Create a custom channel name by setting channel_name. You can even use macro substitution to create a channel name that includes the current date and the title attribute:

  "channel_name": "_bug-report_${YYYY}-${MM}-${DD}-${title}"

If somebody reports “Database error” on November 15, the channel name of the bug report will be “_bug-report_2020-11-15-database_error”. Conclude translates space to underscore.

Disable deadline and severity

If setting a deadline or severity is irrelevant you can turn them off by setting disable_deadline* and **disable_severity** to true.

  "disable_deadline": true,
  "disable_severity": true,

Note that we are using boolean values here and not strings.

Rate limit

You can limit the maximum number of new activities per minute setting rate_limit. The example below sets a limit of maximum 12 new activities per minute. The numeric value must be between 1 and 120.

  "rate_limit": "12/min"

Setting the rate limitation can be useful when accepting activities from external sources, for example, by using a web connector.

Web connector

Conclude apps live inside your team’s Slack workspace and may only be used by team members. The web connector opens your app to external users by connecting a web form directly to your app. This allows external users to create new activities.

The web connector is unidirectional. In order to respond to the external user, you will need an email address, or a phone number.

Read more about the web connector here.

Supercharge your team!

Bridge the collaboration gap with Conclude apps.