You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CC @leahy268@christianmorfordwaitessw@adamcogan@bradystroud@wicksipedia
As per my conversation with Warwick, Christian and Brady on August 19th, when users make a change to their profile it is very unclear whether or not their changes should be live. From their perspective they get an email saying changes were made but it doesn't give them any indication on if the changes should already be live or not. To address this problem we should implement some kind of automated email notification to indicate that changes are deployed.
When a flow is triggered from people add the user who triggered it to a subscription list
When the next rolling build is triggered we send out an email to those on the subscription list to say the build has been triggered and should go live in 20 minutes and then clear the subscription list.
Investigate if we should extend this further by sending a notification when the deployment itself is complete and implement it if it makes sense.
See the below diagram for details of the process: Figure: The process for triggered people profile changes
The text was updated successfully, but these errors were encountered:
CC @leahy268 @christianmorfordwaitessw @adamcogan @bradystroud @wicksipedia
As per my conversation with Warwick, Christian and Brady on August 19th, when users make a change to their profile it is very unclear whether or not their changes should be live. From their perspective they get an email saying changes were made but it doesn't give them any indication on if the changes should already be live or not. To address this problem we should implement some kind of automated email notification to indicate that changes are deployed.
See the below diagram for details of the process:
Figure: The process for triggered people profile changes
The text was updated successfully, but these errors were encountered: