🛠️Setup Team
This section covers how can you configure your team in Pagerly
Last updated
This section covers how can you configure your team in Pagerly
Last updated
Each Team has the following properties:
This is your team name and the slack command that would be used to mention the current oncall, fetch oncall schedule, etc. i.e. You can use
@Pagerly <team> : To mention the current oncall on any Slack Thread
/schedule <team> : To fetch the team's oncall schedule. You can then manage( view, override ) from Slack itself
There are some gotchas to keep in mind when selecting the team name :
Single word only: You can only put a single word while choosing the command name. You can combine long names with underscores, hyphens, etc
You can use names like : dev-on-call , dev, dev_on_call
You cannot use names like : dev on call, payments team 2
Cannot use the name help : This is due to slack limitation of keeping help as a reserved keyword . You can use ``@pagerly help`` for help needed in the command
With Pagerly you can sync the Oncall Schedule with Slack Usergroup
You can sync with External Schedule like Pagerduty, Opsgenie, Google Calendar etc
You can also sync with Pagerly Round-Robin Schedule
Pagerly would automatically fetch the latest oncall(s) and add the users in the usergroup and remove others
For Usergroup to work : Pagerly App uses Slack's User Group feature to create an @mention for every rotation. Please make sure you have it enabled for everyone in the workspace settings .
Usergroup: If you want to have a custom command like @dev-on-call instead of @Pagerly dev-on-call or If you already have a usergroup and you want the current oncall(s) to be automatically added to the usergroup, you can use this property.
Pagerly would automatically fetch the latest oncall(s) and add the users in the usergroup and remove others
Permanent Users in the user group (optional) : These are the members who you need as permanent members of the usergroup
Automated Reply: To add a fixed reply when your oncall is mentioned. Works only with @Pagerly commands. You can put SOPs, Troubleshooting docs, etc in automated replies. This would help in saving precious oncall time since some of the queries can be automatically taken care of 💰💰
The slack channel which would subscribe for any oncall handover / oncall rotation change. On any change in oncall rotation, you would receive 2 notifications on this slack channel
Channel Topic Update : Your slack channel topic would be automatically updated with the current oncall. It would look something like this 👇🏻
Channel Message : Your channel would receive a notification on the oncall change
(Customize Notification Here)👇🏻
You can choose to receive if you want to receive notifications on oncall/rotation change as well topic updates.
Update Channel with Topic Name -> If you want your channel topic to be updated with latest oncall
Show Change Notification on Channel -> If you want to receive the Notification whenever there is a change in oncall / rotation (Customize Notification Here)
This is only required for creating teams syncing schedule with External Sources
Schedule Id : This is the main property of the team which maps the oncall rotation schedule in your paging tool . (more discussed in detail in further sections)
You can input the schedule id from
Pagerduty -> Get Schedule Id from Pagerduty
Opsgenie -> Get Schedule Id from Opsgenie
JSM Operations -> Get Schedule Id from JSM Operations
Google Calendar -> Get Schedule Id from Google Calendar
Google Sheets -> Get Schedule Id from Google Sheets
