Using On Duty groups

The "On Duty" group represents a powerful addition to your Round Robin rotation. Through this feature, the user on duty is permanently assigned as a single (see notes at the end) member of a Slack user group of your choice, allowing you to notify the user of an assignment for a specific rotation without knowing who it is.

This feature, however, is bound to:

• The availability of user groups in your Slack
• The possibility of the bot manipulating user groups in your Slack workspace.

Prerequisites

If user groups are available in your subscription and you have the admin rights to do so, select "Everyone except guests" for both permissions inside the Workspace Settings & Permission section of your Slack Workspace Administration website.

If you cannot manage permissions by yourself, ask an Administrator to do it for you.

Create an "on duty" user group (if you have permission to create groups)

To create an on-duty user group, use the "Add on-duty group" from the rotation command bar.

You can choose the proposed on-duty handle (rotationame-operator) or create your own. The usual user group name limitations apply (max length, valid characters, etc.).

Create an "on duty" user group (if you DO NOT have permission to create groups)

To create an on-duty user group, use the "Add on-duty group" from the rotation command bar.

In this case, you can choose an existing group from the list. If you do not have enough permission, you will get an error while saving your changes.

Group Membership

By default, duty change will clean the group membership and replace it with the new user(s) on duty.

If you want the bot to only add and remove the user going on and off duty, and leave the other users is, remove the flag from "Clean on-duty group on duty change".

Another crucial aspect to understand is that a Slack user group requires at least one member. This is a Slack stuff, and you cannot control it. If, for any reason, the last member of an on duty group needs to go off-duty (for example if you're using business hours rotations) then you can decide how the system should behave using the second option.

If you chose "Leave the group active" the last member of the group will remain a group member and they will be removed once a new member will go on duty. Otherwise, if you select "Disable the user group", the system will try to disable the user group and enable it again once a new member is ready for duty.

Keep in mind this option requires the ability to manipulate user groups. If the bot doesn't have this right, the system will behave like "Leave the group active" is selected.