plorabunt:authentication
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| plorabunt:authentication [2026/01/15 16:37] – fincons | plorabunt:authentication [2026/01/15 16:44] (current) – [Navigation and breadcrumb] fincons | ||
|---|---|---|---|
| Line 82: | Line 82: | ||
| This structure ensures a consistent and simplified navigation experience across the entire application. | This structure ensures a consistent and simplified navigation experience across the entire application. | ||
| + | |||
| + | ---- | ||
| + | ==== User roles ==== | ||
| + | |||
| + | The platform defines three main user profiles, each with specific responsibilities and permissions. | ||
| + | |||
| + | ^ Role ^ Description ^ Main permissions ^ | ||
| + | | **Admin** | Technical user account employed by the management team for setup and maintenance operations. | Backend management, system maintenance, | ||
| + | | **WPLead** | User responsible for reviewing and validating requests submitted by Researchers. | Can approve, reject, delete, or view submitted requests. | | ||
| + | | **Researcher** | User enabled to create new resources (“items”) and manage their own submissions. | Can create, edit, submit, view, and delete their own requests. | | ||
| + | |||
| + | Requests submitted by Researchers are reviewed by the WPLead according to the following logic: | ||
| + | |||
| + | * If approved, the resource is published in the central database. | ||
| + | * If rejected, the resource is returned to Draft status, accompanied by a rejection motivation that allows the user to modify and resubmit the request. | ||
| + | |||
| + | This workflow ensures data quality and consistency before publication, | ||
| + | |||
plorabunt/authentication.1768491458.txt.gz · Last modified: by fincons
