How can Admins change Dataverse notification settings for everyone

56 views
Skip to first unread message

Florio Orocio Arguillas

unread,
May 8, 2026, 10:33:47 AMMay 8
to 'Julian Gautier' via Dataverse Users Community

Hi friends,

 

We noticed that email notification settings are all checked by default. 

 

As Administrators, we would like to uncheck some default settings and apply them universally to all users.

 

  1. Can we uncheck some default email notification settings, like the ones I randomly unchecked below?  This way, for example, our users will not receive email notifications when a role is assigned, revoked, a Dataverse collection is created, or publishing fails.

 

or

 

  1. Are there alternatives to not sending email notifications related to the ones I unchecked below?

 

What would be the steps to do that?

 

We are fine with having all the in-app notifications checked.

 

Let me know.

 

Thanks.

 

Best regards,

 

Florio

 

 

 

 

 

 

 

 

Philip Durbin

unread,
Jun 24, 2026, 4:51:11 PM (10 days ago) Jun 24
to dataverse...@googlegroups.com
Hi Florio,

I don't think there's an easy way to do this. Please feel free to create an issue at https://github.com/IQSS/dataverse/issues

A workaround could be to generate an API token for each of your users and write a script to the following API (as many times as necessary):


I hope this helps!

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/BL0PR04MB4482BA3EF8926ACB793489FE8F3D2%40BL0PR04MB4482.namprd04.prod.outlook.com.


--

Laura Huisintveld

unread,
Jun 26, 2026, 4:52:14 AM (8 days ago) Jun 26
to Dataverse Users Community
Hi Florio,

Does this setting maybe help you? 
https://guides.dataverse.org/en/6.10/installation/config.html#alwaysmuted
It will let you mute notifications for all users, and they can't undo it.

This setting will do the opposite: https://guides.dataverse.org/en/6.10/installation/config.html#nevermuted
It will set which notifications cannot be muted by users.

Kind regards,
Laura

Op woensdag 24 juni 2026 om 22:51:11 UTC+2 schreef pdu...@g.harvard.edu:

Eryk Kulikowski

unread,
Jul 3, 2026, 10:10:36 AM (yesterday) Jul 3
to Dataverse Users Community
Hi Florio,

Laura is right, those are the settings for this (I implemented them a while back, so I double-checked the code to be sure of the details). The exact setting names are :ShowMuteOptions, :AlwaysMuted and :NeverMuted, documented here: https://guides.dataverse.org/en/latest/admin/user-administration.html#letting-users-manage-notifications

For example, to mute role assignment and revocation notifications for the entire installation:

curl -X PUT -d 'ASSIGNROLE,REVOKEROLE' http://localhost:8080/api/admin/settings/:AlwaysMuted

One important caveat for your use case: :AlwaysMuted mutes both the email and the in-app notification — the notification is not created at all for the muted types. So if you want to turn off the emails but keep the in-app notifications, this setting is too coarse.

For email-only muting, the preference is per user. With :ShowMuteOptions enabled, each user can uncheck just the "email" column for a notification type in the Notifications tab of their account page while keeping the in-app notification. There is currently no installation-wide setting to change that default for everyone, so to do it in bulk for existing users you'd either use the mutedEmails API Phil mentioned (which requires each user's token), or update the mutedemails column of the authenticateduser table directly in the database (it's a comma-separated list of the same type names, e.g. 'ASSIGNROLE,REVOKEROLE'). Note that either way users can re-enable the emails afterwards, and new accounts will still start with everything enabled.

If a "muted by default, but user can opt back in" installation-level setting would be useful, that would be a reasonable feature request on GitHub.

Best,
Eryk

Op vrijdag 26 juni 2026 om 10:52:14 UTC+2 schreef Laura Huisintveld:
Reply all
Reply to author
Forward
0 new messages