-
Notifications
You must be signed in to change notification settings - Fork 2
Biocollect
This document gives an overview of Biocollect use, for instance explaining its user permissions system.
The user roles in BioCollect include:
- Administrator
- Moderator
- Editor
- Project Participant
Note: The role of CaseManager is used by another application that shares the ecodata server-side application and database.
Admin provides full administrator rights at the project level. Every project must have at least one admin, and the project creator is automatically associated with the project with the admin role. Admins can see and edit all configurations, artifacts, data records, etc.
Moderators have most admin rights. They can edit their own and others' records, verify records, as well as embargo and release records. However, moderators do not have access to the Admin tab and hence can't edit project and survey configurations.
Editors are specifically added as members of a project and can create and edit their own records. They can see and download embargoed data, and view all project artifacts. This role is particularly for non-public surveys.
Project Participant is a special role allocated to any public person who contributes data records to a survey which is configured to allow public data contributions.
These roles facilitate a wide range of configuration options which support most likely use cases - public/non-public, moderation, verification, etc.
Index
- Wiki home
- Community
- Getting Started
- Support
- Portals in production
- ALA modules
- Demonstration portal
- Data management in ALA Architecture
- DataHub
- Customization
- Internationalization (i18n)
- Administration system
- Contribution to main project
- Study case