Mail recipient when request access to restricted file

21 views
Skip to first unread message

Michel Bamouni

unread,
Feb 7, 2018, 10:54:32 AM2/7/18
to Dataverse Users Community
Hi,

I use dataverse 4.5.1. In this dataverse, I have my root dataverse called "A". This dataverse contains another dataverse called "B".
In dataverse "B", I create a dataset which have files with restructed access. When a user sends 'request access" to the dataset in the dataverse "B", the mail is send to the root dataverse contact.
I want that the mail is sends to the contact of the dataset or at the to the contact of the dataverse "B".
How can I do it?

Best regards,


Philip Durbin

unread,
Feb 8, 2018, 9:29:57 AM2/8/18
to dataverse...@googlegroups.com
Hi Michel,

Thanks for bringing this up. We should probably define our terms a bit because it can get confusing. The "contact" for a dataset or dataverse is where email is sent when you click the "Contact" button. When access to restricted files is requested, email does not go to the "contact". Rather, email is sent* to the people who have the ability to grant access, which are the people who have a role that contains "ManageDatasetPermissions".

I'm not sure how well this is explained in the User Guide so at the very least you are welcome to create a GitHub issue at https://github.com/IQSS/dataverse/issues asking for clarification. You can also create an issue if you think there is a bug or if you'd like the behavior to change.

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-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/33093134-99ad-4f6d-8c18-9dffaa046dc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Reply all
Reply to author
Forward
0 new messages