Better distinction of which backend changes cause notifications

Is your feature request related to a problem? Please describe.
As a space admin, not completely proficient in Decidim, it is hard for me to identify which changes cause a notification/e-mail to be sent. This can be problematic, as moments of communication are often carefully scheduled, and this can cause unwanted attention or confusion.

Describe the solution you'd like
We propose adding a symbol (i.e. a bell) in the backend next to the setting's title. Hovering on the bell would then display an infotext (i.e. "Changing this setting will cause notifications to be sent."). This way, I am made aware of what consequences the changes have.

Describe alternatives you've considered
We currently just add a remark in the field title. However, this is unnecessarily bulky.

Additional context
In a second step, the bell symbol could also be used as a trigger to enable/disable notifications.

Does this issue could impact on users private data?
–

Funded by
no funding available currently