-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMTP templates. Show activate provider as another optional step #7929
Comments
I think especially for self-hosters without a default smtp config this feature could help a lot to avoid confusion, as in the provider list it's not obvious that a provider is inactive after creation and where it can be activated. |
Hi @doncicuto I think this would be nice to have. I will assign you as you suggested. |
Hei @hifabienne I'm starting to work on this issue right now |
# Which Problems Are Solved - In #7929 it was detected that it would be better to show the activate/deactivate action for a SMTP configuration in the wizard as for some users it'd not be intuitive that the SMTP provider must be activated so Zitadel can use it to send notifications. # How the Problems Are Solved - When a new SMTP provider is added or updated, the wizard has a new step that allow us to activate or deactivate the provider configured in the previous step. The following video shows the new wizard: https://github.com/zitadel/zitadel/assets/30386061/178234d6-73dc-4719-af0b-1d6f19bf3f7d # Additional Context - Closes #7929
🎉 This issue has been resolved in version 2.53.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Preflight Checklist
Describe your problem
@eliobischof suggested in Discord that it'd good if you can activate the SMTP provider in a similar way as the new IDP wizard works.
Describe your ideal solution
Here's the screenshot for a new Google IDP
I'd add the 'active this SMTP provider' as an optional step once you create the provider (the dialog would not be closed and this step would be shown).
I agree and I missed that option when developing SMTP templates... so I open an issue to track this feature.
Of course, feel free to assign this issue to me.
Version
No response
Environment
Self-hosted
Additional Context
No response
The text was updated successfully, but these errors were encountered: