Skip to content

Feature Request: Allow admins to suppress notifications to members of explicit groups when the group is granted a role on a dataset #12351

@chrisjcameron

Description

@chrisjcameron

Overview of the Feature Request

Allow admins to suppress notifications to members of explicit groups when the group is granted a role on a dataset.

What kind of user is the feature intended for?

  • Organizations that use explicit groups to manage users with access to a large and evolving set of datasets.
  • Users who want to receive notifications when they have personally been granted access to a dataset, but don't want to know about every dataset granted to every group of which they are a part.

What inspired the request?

We use an explicit group to manage access to datasets that are restricted to the current campus community. If we grant an explicit group a role on a dataset, everyone in the group is notified. This is potentially 100's of emails at a time.

What existing behavior do you want changed?

The current philosophy of "let the user decide" does not allow sufficient control to differentiate between role grant announcements that pertain to an individual user, a small group or a campus-wide group. Currently, they must accept all-or-nothing, and it must be configured on a per-user basis.

Dataverse admins are in a better position to decide if an announcement is helpful or spam.

Any brand new behavior do you want to add to Dataverse?

This could be addressed by adding a checkbox on the permission-granting UI about "send notifications about this change" or via an api endpoint with a no-notification option.

Any open or closed issues related to this feature request?

Numerous closed tickets about notification spam and need for more control. None with this specific issue.

Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
It is something I would look into after the single-page app front end is released. Part of the need to use explicit groups is the lack of support for filtering on specific OpenID keys that would let us differentiate between the current campus community and the alumni / retiree community.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions