Email stage

the email stage can be used for email verification, and the background worker will send an email using the specified connection details if an email cannot be delivered, the delivery is automatically retried periodically the default behavior is to send the email to the currently pending user, but this can be overridden by setting the email in the plan's context to another email address, see below request context\["flow plan"] context\["email"] = "foo\@bar baz" \# or get it from a prompt \# request context\["flow plan"] context\["email"] = request context\["prompt data"]\["email"] \# or another user attribute \# request context\["flow plan"] context\["email"] = request context\["pending user"] attributes get("otheremail") return true custom email templates can also be used, to leverage your own design or layout by placing templates in the custom templates folder and selecting the template when creating/editing an email stage if the template is not visible, the worker logs should be checked create a configmap with your email templates {% code overflow="wrap" %} apiversion v1 kind configmap metadata name authentik templates namespace authentik data my template html | \<tr> {% endcode %} then, in the helm chart add this to your values yaml file volumes \ name email templates configmap name authentik templates volumemounts \ name email templates mountpath /templates