Objective
Enable users to control incident visibility so that 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
Assumptions
Requirements
Requirement | User Story | Jira Issue | |||||
|---|---|---|---|---|---|---|---|
| 1 | Limit incident visibility access to only participants | As an incident participant, I can make an incident and its channel private so that only non-participants don’t know it exists let alone access its content. | |||||
| 2 | Relax incident visibility to everyone on the team | As an incident participant, I can make an incident and its channel public so that everyone in the Team can see and access its content. |
| 3 | Prioritize seeing Configure playbooks to create public/private incidents | ||
| 3 | Prioritize incidents that the user is involved ina participant of | ||||||
| 4 | Limit the ability to create playbooks to Team Administrators | ||||||
| 5 | 6 | 7 | Limit playbook access to specific users |
User interaction and design
...
Question | Answer | Date Answered |
|---|---|---|
What does “access” entail? | Able to see that an object exists, view its detail, update its detail, as well as delete if applicable. | May 21, 2020 |
What’s the UX for making an (existing or new) incident private? | ||
What’s the new UX for RHS incident list? | ||
What’s the new UX for playbook configuration? |