Goals/Scope
Ability to set users to be opted out of automated emails
Status in eLMIS: Implemented.
Status in OpenLMIS: Not Implemented
Priority: High priority for Tanzania, Zanzibar, Zambia
Background
Some users may not like too many automated emails
Assumptions
User is registered with the database and have roles assigned
User Stories
Diagrams
Affected screen in OpenLMIS: (Administration>Users>Edit User Roles)
Business Logic:
- If the user has a supervisory role, display a checkbox to opt-out of emails globally
Microservice Changes:
- We may need to add a check to the requisitions microservice that checks if the user has opted out of emails during the process of email generation
Dependencies
Description | Link |
---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
# | Question | Outcome | Status |
---|---|---|---|
1 | Is the need to turn all of them off globally or one by one? | ||
2 | Should this be something that the Administrator only has access to, or should the user also have the ability to do this on their own account? | ||
3 | Please validate this assumption: The opt out of email option is related to a user's role and should be implemented on the roles screen | ||
4 | Is there a specific subset of emails that need to be opted out of? For example, users should not be able to opt out of emails sent by administrators and critical notifications, but they may want to opt out of requisition approval notifications | ||
5 | There was a recent request on a product committe call to create a daily summary email of activity. Should this be included in the scope? | ||
6 | Ashraf, can you define the meaning of "supervisory emails" in the screenshot? |
Out of Scope
Notes from Gap Estimation 4/11/2018
- Attendees: Matt Berg, Josh Zamor, Ashraf Islam, Craig Appl
- Add a checkbox to the user's profile page that allows them to opt out of supervisory emails.
- Users must still receive emails for their facility
- We should consider allowing the notification service to choose this option for supervision
- Maybe we could have a list of your active subscriptions and then opt out of each subscription
- DECISION - We will opt out of all supervision notifications
- Don't take away the auditability of each notification that was generate
- Log all notifications in the system where they are generated and log where it was shutdown by the notification service
- We need to add an audit log for the notification service that logs if a user is muted (make sure this logs the content as well)
- Question: Does an admin need to view who is currently subscribed to notifications?