Support intro
Sorry to hear you’re facing problems 
help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
example
Or for longer, use three backticks above and below the code snippet:
longer
example
here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can 
Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server
Nextcloud version (eg, 24.0.1): 34.0.0.12
Custom TURN server configured: yes
Custom STUN server configured: yes
The issue you are facing:
I’m running a Nextcloud Docker installation on a virtual server, debian 12. The problem which I’m facing there in Talk is following: I’m in webbrowser in my admin profile, settings and talk. There I can change the “Default notification settings”, standard is “mention only”. I want to change it to “all news”. I can do it, but it doesn’t have any effect. And with every reload, it’s set back to “mention only”.
Please be kind that it’s not the perfect translation, I’m using german version.
We want to have a standard notification in Talk, that everybody will notified with all messages.
The problem occured a few months ago when installing Nextcloud, I hoped it’s just a bug and will be gone with one of the next updates, but it’s still there.
There is a oportunity to change the value from “mention only” to “all news”, I can change it and I have to verify it with my admin password, but it doesn’t have any effect.
Does anybody now what’s the problem here?
Installation is in docker container on a linux debian 12 server.
Is this the first time you’ve seen this error? (Y):
Thanks a lot for helping
best regards 