Feb 26 webinar: Using Permissions in Dataverse

[Philip Durbin]

Coming on Feb 26!

https://support.dataverse.harvard.edu/event/using-permissions-dataverse

Using Permissions in Dataverse

Learn how to manage permissions in a Dataverse repository to manage deposit workflows and access to your data. This webinar will provide an overview of the permissions framework, helping you understand roles, access levels, and how to customize permission at the collection, dataset, and file levels.

Key topics include:

- Overview of roles: Administrators, contributors, curators, data users
- Configuring dataset-level and collection-level permissions
- Managing guest access and link sharing
- Best practices for balancing openness and data protection

This session is designed for researchers, data managers, and repository administrators who want to maximize collaboration and manage data access. Whether you're new to Dataverse or looking to refine your repository practices, this webinar will equip you with the tools to navigate permissions effectively.

Presenters:
Sonia Barbosa (The Dataverse Project, IQSS)
Gustavo Durand (The Dataverse Project, IQSS)

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Philip Durbin]

The recording and slides are up!

- recording: https://www.youtube.com/watch?v=mx6zuOt-C2A

- slides: https://dataverse.org/presentations/permissions-dataverse-supported-repository

[Debora Pignatari Drucker]

Hey Philip

Thank you very much for sharing.

We have been experiencing a behaviour at our Dataverse instance that seems unexpected to me. We´ve created a custom role entitled "Editor" with the following permissions:

However, the users and groups with this role cannot edit datasets already submitted for revision. They can only edit draft datasets that were not submitted. Is it an expected behaviour?

Our dataverse instance is v5.12.1.

Thanks

Debora

--
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/CABbxx8Fe7krVzuLqR9bNoizZXE%3DxkJYikWHg85mVemN9%2BmzpGQ%40mail.gmail.com.

__________________________
Aviso de confidencialidade

Esta mensagem da Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), empresa publica federal  regida pelo disposto  na Lei Federal no. 5.851,  de 7 de dezembro de 1972,  e  enviada exclusivamente  a seu destinatario e pode conter informacoes  confidenciais, protegidas  por sigilo profissional.  Sua utilizacao desautorizada  e ilegal e  sujeita o infrator as penas da lei. Se voce  a recebeu indevidamente, queira, por gentileza, reenvia-la ao emitente, esclarecendo o equivoco.

Confidentiality note

This message from Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), a government company  established under  Brazilian law (5.851/72), is directed exclusively to  its addressee  and may contain confidential data,  protected under  professional secrecy  rules. Its unauthorized  use is illegal and  may subject the transgressor to the law's penalties. If you are not the addressee, please send it back, elucidating the failure.

[Laura Huisintveld]

Hi Deborah,

I think this is indeed expected behaviour.

Once a dataset is submitted for review, it is locked for users who are not able to publish the dataset. This is because otherwise the reviewer and in your case 'editor' can change the dataset at the same time, which makes reviewing a dataset difficult.

If you add the permission bit for publishing the dataset to the custom role, users with this role should be able to keep editing. However, this makes the 'submit for review' step not applicable any more.

Kind regards,

Laura

Op woensdag 17 september 2025 om 16:31:27 UTC+2 schreef debora....@embrapa.br:

[Philip Durbin]

Yes, I think Laura has it right. Datasets are locked to edits unless unless you have permission to publish. In theory, this "edit while in review" permission could be split off into its own permission. The most recent permission split was done in https://github.com/IQSS/dataverse/pull/11691 to make "link dataset" and "link collection" their own permissions.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/f91acdc0-fc88-40d6-b273-3f28b0f7ad5fn%40googlegroups.com.