Incident Roles

Introduction

We’ve recently introduced new roles and enhanced existing ones as part of our continuous focus on ensuring Blameless is enterprise grade. Roles in Blameless, expressed as CRUD actions against specific resources, represent a set of permissions in the Blameless platform as well as Slack.

Incident roles

While there are a variety of platform roles, there are three key roles that have broader implications in the platform and Slack.

Let’s begin with describing these three roles in detail:

• Incident Reader: Minimum viable read and update access across an Incident.
• Incident Writer: Majority of read and update access across an Incident.
• Incident Admin: All read and update access across an Incident.

These roles are created automatically for the default incident type for each custom incident type, enabling users to effectively isolate access permissions by incident type. 

Slack command mapping

In addition to general platform access, each incident role is mapped to Slack commands that correlate to a range of rights based on role type. Users within incident roles have access to a specific set of Slack commands that they can execute, as conveyed in the table below.

New incident roles