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
Currently, the branding (logo, colors, and other design elements) in emails is hardcoded, instead of dynamically adjusting based on the app’s white-labeling settings. This results in email content that does not reflect the expected branding for different deployments.
Steps to Reproduce
Configure white-labeling settings (e.g., custom branding, logos, or colors).
Trigger an email (e.g., user invitation, password reset).
Observe that the email does not reflect the custom branding but instead uses a default or hardcoded style.
Expected Behavior
Emails should inherit the white-labeling settings from the app configuration to ensure branding consistency.
Update email templates to dynamically fetch and apply branding settings from the app configuration.
Ensure that elements such as logo, colors, and footers match the customized settings for each deployment.
The current email template is hard coded in the email_utils.py file.
The text was updated successfully, but these errors were encountered:
Description
Currently, the branding (logo, colors, and other design elements) in emails is hardcoded, instead of dynamically adjusting based on the app’s white-labeling settings. This results in email content that does not reflect the expected branding for different deployments.
Steps to Reproduce
Expected Behavior
Emails should inherit the white-labeling settings from the app configuration to ensure branding consistency.
Actual Behavior
Emails display hardcoded branding elements, ignoring custom settings.
Proposed Fix
Update email templates to dynamically fetch and apply branding settings from the app configuration.
Ensure that elements such as logo, colors, and footers match the customized settings for each deployment.
The current email template is hard coded in the email_utils.py file.
The text was updated successfully, but these errors were encountered: