When Okta users are re-activated after being suspended for inactivity, it's a silent process - they aren't notified that their status has changed. They'll be deactivated again at midnight EST unless they sign in the same day, so it's important to ask them to sign in promptly.
Action requested
There isn't a default Okta email for this status change, so we'll need to use an Okta Workflow instead. These workflows are created through a drag-and-drop editor in the Okta UI, and allow a finer degree of control over different events that happen within our Okta space. In particular, there's an Okta Workflow integration with SendGrid, which we already use to send non-Okta emails such as test result notifications to patients.
Acceptance Criteria
End users are emailed upon reactivation. This email language should also include a link to our instructions on password reset, as users frequently request a password reset after they've been reactivated. Other than that, we should be able to repurpose the text of the email that the support staff sends out manually today:
Thank you for contacting SimpleReport Support.
I just reactivated your account. You can use the email associated with your account and the password to login on simplereport.gov. Please do so before 6AM EST tomorrow to avoid the account being deactivated again. If that happens, just shoot us another email and we will reactivate again for you.
If you have any questions or further issues, please reach back out to our team.
Additional context
The support team will need to be notified once this is finished.
Background
When Okta users are re-activated after being suspended for inactivity, it's a silent process - they aren't notified that their status has changed. They'll be deactivated again at midnight EST unless they sign in the same day, so it's important to ask them to sign in promptly.
Action requested
There isn't a default Okta email for this status change, so we'll need to use an Okta Workflow instead. These workflows are created through a drag-and-drop editor in the Okta UI, and allow a finer degree of control over different events that happen within our Okta space. In particular, there's an Okta Workflow integration with SendGrid, which we already use to send non-Okta emails such as test result notifications to patients.
Acceptance Criteria
End users are emailed upon reactivation. This email language should also include a link to our instructions on password reset, as users frequently request a password reset after they've been reactivated. Other than that, we should be able to repurpose the text of the email that the support staff sends out manually today:
Additional context
The support team will need to be notified once this is finished.