Enhance Env in Variable Selectors for Notifications - for default setup to support singular System Email vs both Split System Email plus Admin Email

[Mathew-WD]

What are you trying to do?

I am trying to set up default Forms and Notifications with frictionless change as needed.

Given Authenticated Sending Domains I almost always have a sending address from the domain of the site.
I'm seeing more real world cases where the site sending address must be different to the admin inbox(Sometimes a completely different domain or mail service).

Currently I use this to cover Sites that use singular System Email (reception@example.com)

• System Email in ENV (SYSTEM_EMAIL="reception@example.com") single point of change
• $SYSTEM_EMAIL in Settings > Email > System email
• User notification is From: System Email using Variable Pickers (reception@example.com)
• Admin Notification is From: system email using Variable Pickers (reception@example.com)
• Admin Notification is To: system email using Variable Pickers (reception@example.com)

Craft and Formie have this working fine, it makes sense when you set it up and revisit it in craftadmin. Admins understand it (as there are blue boxes around [System Email] which reenforces intent and validity.

What I am trying to do is introduce a new ENV variable and allow seamless switch back or forwards between:

1. Singular System Email (reception@example.com)

• System Email in ENV (SYSTEM_EMAIL="reception@example.com") single point of change
• Admin Email in ENV ADMIN_EMAIL="${SYSTEM_EMAIL}" single point of change default inherited from system
• $SYSTEM_EMAIL in Settings > Email > System email
• User notification is From: System Email using Variable Pickers (reception@example.com)
• Admin Notification is From: system email using Variable Pickers (reception@example.com)
• Admin Notification is To: $ADMIN_EMAIL (reception@example.com)

2. Sites that use both System Email (noreply@example.com) and an Admin Inbox (admin@example.com)

• System Email in ENV (SYSTEM_EMAIL="noreply@example.com") single point of change
• Admin Email in ENV ADMIN_EMAIL="admin@example.com" single point of change
• $SYSTEM_EMAIL in Settings > Email > System email
• User notification is From: System Email using Variable Pickers (noreply@example.com)
• Admin Notification is From: system email using Variable Pickers (noreply@example.com)
• Admin Notification is To: $ADMIN_EMAIL (admin@example.com)

This all technically works but feels a ENV handling feels a little less supported leading to confused admins
See proposed solution.

What's your proposed solution?

Maybe I am missing something do you have any ideas?

or

Formie support ENV selections in variable selectors
and display in Craft Admin with a blue box. To re-enforce the support of this feature.
This should lead to less confusion all round.

or

See if Craft are willing to support this separation in email settings by adding a n Admin_Email field that can support ENVs.
Formie can use it like System Email.

Additional context

No response

[engram-design]

I will say that the default "From" email uses the "System Email", so unless you need to change that, you can omit it.

.env variables are absolutely supported in all those settings; there's just the lack of UI polish/autocomplete that you see elsewhere in Craft. Just because we roll our own UI for the form builder. I'm actively working on that now with some other major UI changes.

[Mathew-WD]

Thanks for the suggestion, at the end of this venture I was going to omit back to default sender.

I look forward to more polished ENV support:
Being able to pick it from the variable selector and see it in a coloured box would be an amazing feature for wider use cases as well..