Sub-dataverse that is visible to a select few

[Florio Orocio Arguillas]

 

Hello friends,

 

Is it possible to publish a sub-Dataverse that is visible only to selected account holders?  I don’t want to make it public.  I just want it to be seen, say, by two people with accounts in our Dataverse.  If yes, how do I set it up?

 

Thanks.

 

Best regards,

 

Florio

 

 

 

 

 

 

Florio O. Arguillas, Jr. Ph.D.

Research Associate

Cornell Center for Social Sciences

Cornell University

741 Rhodes Hall

Ithaca, New York 14853

 

 

[James Myers]

Florio,

 

You may want to look at the recently added support for Locally FAIR data – see https://guides.dataverse.org/en/latest/user/dataverse-management.html#locally-fair . In general, publishing a collection or dataset in Dataverse means they become public, with the exception that files in published datasets can be restricted/embargoed/etc. to limit their availability. The Locally FAIR functionality changes that, for collections that use it. Locally FAIR content is only visible to specified users/groups. Such collections and datasets won’t show up in search results, you can’t navigate to the collection/dataset page, etc. unless you are granted access. (Alternately, if you only need to assure that the datasets can only be added in the collection by certain users and files in those datasets are only accessible to certain users, you can use the standard roles/permissions to do so.)

 

Locally FAIR is something that has to be enabled by the site admins of a given Dataverse, and it is described as ‘experimental’/advanced in the guides to indicate that it may evolve and that it “generally may require more effort to configure and manage and/or more effort to support than more mature functionality”. In particular, for Locally FAIR, there is nothing but policy stopping you from using DOIs for dataset identifiers (which would expose them through the DOI resolver system) or linking datasets or collections into public collections, etc. There are also known limitations which may or may not be acceptable for your case – e.g. functionality related to quotas and metrics will still let people infer that hidden collections exist.

 

Hope that helps,

-- Jim

--
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/SJ0PR04MB82740B3FCAB285B7327B279E8FB62%40SJ0PR04MB8274.namprd04.prod.outlook.com.

[LeBeau, Renée]

Florio,

You can create a dataverse, then view it.  Now go to Edit on the upper right and select Permissions from the menu.  Click "Edit Access".  Make sure that the "Anyone adding to this dataverse needs to be given access" radio button is selected.

Now click "Assign Roles to Users/Groups".  Add the two people you want to have access, one at a time, with the Member radio button selected.  Now these two people plus the site admin (should be visible already in the Users/Groups grid) and any superusers can see the unpublished datasets in this unpublished dataverse.

Renée LeBeau

Indiana University

Library Technologies

Wells Library - W501

rdle...@iu.edu

 

---

From: 'Florio Orocio Arguillas' via Dataverse Users Community <dataverse...@googlegroups.com>

Sent: Thursday, September 3, 2026 11:33 AM
To: dataverse...@googlegroups.com <dataverse...@googlegroups.com>
Subject: [External] [Dataverse-Users] Sub-dataverse that is visible to a select few

 

This message was sent from a non-IU address. Please exercise caution when clicking links or opening attachments from external sources.

--