Objective
Enable users to control incident visibility so that Ensure only the right people can access that information.
Support foreseeable granular configurations for user access based on beta feedback
Extend the existing Mattermost permission model
...
playbooks and workflows.
Figure out how to deploy to future Cloud customers.
Assumptions
Only deploying to Cloud alpha customers.
Requirements
Must be able to… | User Story | Jira Issue | |
|---|---|---|---|
| 1 | Limit incident access to only participants | As an incident participant, I can make an incident and its channel private so that non-participants don’t know it exists let alone access its content. | |
| 2 | Configure playbooks to create public/private incidents | As an incident manager, I can configure playbooks to create either public or private incidents so that it defaults to the correct permission when executed. | |
| 3 | Limit playbook access to members with permission | As a playbook creator, I can specify who else can view, edit, and use the playbook so that sensitive content wouldn’t be unintentionally revealed. |
...