The Review Dashboard and Check My Dataset support role-based access control to ensure that users can only access datasets for which they have the appropriate permissions.
Rather than maintaining a separate permission model, both applications build on existing Dataverse roles and permissions. User access is determined through Dataverse role assignments and configurable role mappings.
Access to datasets is based on the permissions a user already has in Dataverse. As a general principle, users can only access datasets that they are permitted to view or manage in Dataverse itself.
Typical examples include:
The review dashboard provides two primary roles:
These roles correspond to existing Dataverse roles and can be mapped through the application configuration.
| Review dashboard role | Dataverse role |
|---|---|
| Reviewer | Curator |
| Administrator | Admin |
Actual mappings are configurable and may vary between installations.
The reviewer role corresponds to the Dataverse Curator role.
Reviewers perform the day-to-day review of datasets:
The administrator role corresponds to the Dataverse Admin role.
Administrators have all Reviewer capabilities and additional permissions required to manage and oversee the review process.
Typical administrator activities include:
Check My Dataset does not introduce additional application-specific roles. Users can access datasets in Check My Dataset when they have sufficient permissions on those datasets in Dataverse. In most cases, this includes:
The exact set of accessible datasets therefore depends on the permissions granted within Dataverse.
Neither the Review Dashboard nor Check My Dataset manage authentication themselves.
Authenticated user information is obtained from HTTP request headers provided by the surrounding authentication infrastructure.
Once authenticated, users are assigned permissions based on their Dataverse group membership and configured role mappings.
For more information, see: