Is your feature request related to a problem? Please describe.
It is a minor annoyance to have to reactivate my account if I don't log into it every 90 days. Getting an email reminder (or two perhaps, with a second coming in within 72 hours of deactivation) would be useful as I can simply log into Sprout again to reset the 90 day clock.
Describe the solution you'd like
Some kind of email reminder letting me know when my account is nearing deactivation.
Additional context
It could be problematic, depending on how the logic to automate emailing is built, if too many users are getting "spammed" by Sprout. Ideally, either only one-a few people in an org should be getting notifications, or if it does not violate DCYF protocol/security requirements, the emails should only go to the impacted users.
Prioritization Process
[ ] Confirm the issue is a feature to which we want to devote resources.
[ ] Write user story in as a (role) I want (something) so that (benefit) format.
[ ] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.
Is your feature request related to a problem? Please describe. It is a minor annoyance to have to reactivate my account if I don't log into it every 90 days. Getting an email reminder (or two perhaps, with a second coming in within 72 hours of deactivation) would be useful as I can simply log into Sprout again to reset the 90 day clock.
Describe the solution you'd like Some kind of email reminder letting me know when my account is nearing deactivation.
Additional context It could be problematic, depending on how the logic to automate emailing is built, if too many users are getting "spammed" by Sprout. Ideally, either only one-a few people in an org should be getting notifications, or if it does not violate DCYF protocol/security requirements, the emails should only go to the impacted users.
Prioritization Process
[ ] Confirm the issue is a feature to which we want to devote resources.
[ ] Write user story in
as a (role) I want (something) so that (benefit)format.[ ] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.