Objective
...
Ensure only the right people can access
...
playbooks and workflows.
Figure out how to deploy to on-prem customers trying Cloud.
Assumptions
Only deploying to Cloud alpha customers.
Requirements
RequirementMust be able to… | 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|||||||
| 2 | Configure playbooks to create public/private incidents | As an incident participantmanager, I can make an incident and its channel public so that everyone in the Team can see and access its content. |
| 3 | Prioritize seeing incidents that the user is involved in | 4 | 5 | 6 | 7 | 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. | ||||||||
| 4 | Pre-install plugin for every Cloud alpha customer | As a Mattermost staff, I can ensure that beta customers in Cloud have access to this plugin so that they can explore it and give feedback with minimal barrier. |
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 |
Out of Scope
UX design revamp