Begin of the insertion##End of the insertion Question:

Should the values for a ENV variable configuration be read-only on the UI?

If not, how do we map one specific configuration that's stored in the database to the configuration from ENV variables? Begin of the deletion

**Thoughts**End of the deletion

Begin of the insertion#####################################

## Considerations:

After talking with Oliver here are some further considerations:

Our SaaS environment uses multi-tenancy and the specifics need to be considered:

End of the insertion * Begin of the insertionfor instances hosted on AWS

* we're using PostmarkEnd of the insertion Begin of the deletion There usedEnd of the deletion to Begin of the insertionreceive emails and use a webhook from Postmark with the email content to call the MailHandler, without the need to use IMAP to get the emails (thus no need to configure it). The inbound email feature works by default.

* for instances hosted on Scaleways

* the inbound email feature currently does not work. This shouldEnd of the insertion be Begin of the insertionokay. And by allowing the full configuration on the UI,End of the insertion Begin of the deletion env vars only, later (with File storages),End of the deletion we Begin of the insertioncan enable usersEnd of the insertion Begin of the deletion hadEnd of the deletion to Begin of the insertionset this up themselves and we don't needEnd of the insertion Begin of the deletion reference SSO setups. HadEnd of the deletion to Begin of the insertionworry about the multi-tenancy.

* In conclusion, we don't needEnd of the insertion Begin of the deletion create references between those two config objects. ChoseEnd of the deletion to Begin of the insertionkeep configurability via ENV vars for SaaS instances


Options going forward:

* migrate ENV var configuration intoEnd of the insertion Begin of the deletion take env variables, createEnd of the deletion a Begin of the insertiondatabase setting once (on upgrade)

End of the insertion Begin of the deletion real DB model, which was fairly easy.

End of the deletion * Begin of the insertionconfiguration via ENV var is no longer possible

* simple, after the migration

* continue reading ENV var configurations into database settings on starts (incl. upgrades)

* a value set via ENV var overwrites the setting (and makes it read-only in the UI)

* configuration via ENV is still possible

* since multiple configurations for inbound emails are possible, we'll needEnd of the insertion Begin of the deletion Please talkEnd of the deletion to Begin of the insertionidentify them to map between the ENV var configuration and a database setting

* even if we still only allow one configuration via ENV var - in this case it would get a default identifier in code.

* if we want to enable multiple configurations via ENV vars, we would need to add identifiers to the ENV vars keys (for example IMAP\_\_CONFIGURATION\_ID\_\_HOST)

* See \`Saml::SeedProvider\`End of the insertion Begin of the deletion WielandEnd of the deletion for Begin of the insertionan example


<br>End of the insertion Begin of the deletion more details.End of the deletion