User Tools

Site Tools


plorabunt:authentication

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
plorabunt:authentication [2026/01/15 09:19] finconsplorabunt:authentication [2026/01/15 16:44] (current) – [Navigation and breadcrumb] fincons
Line 11: Line 11:
  
 By clicking on the *Access* button (located in the top-right area of the navigation bar), the user is redirected to the Keycloak login page.  By clicking on the *Access* button (located in the top-right area of the navigation bar), the user is redirected to the Keycloak login page. 
 +----
 ==== Login page ==== ==== Login page ====
  
Line 39: Line 39:
  
 {{plorabunt:plorabunt_keycloak.png?650|Keycloak}} {{plorabunt:plorabunt_keycloak.png?650|Keycloak}}
 +----
 ==== Roles and permissions after login ==== ==== Roles and permissions after login ====
  
Line 53: Line 53:
 However, only users logged in with the **Researcher** or **WPLead** role are allowed to manage resources or export search results. However, only users logged in with the **Researcher** or **WPLead** role are allowed to manage resources or export search results.
  
 +----
 ==== Logout ==== ==== Logout ====
  
Line 59: Line 59:
  
 {{plorabunt:plorabunt_logout.png?300|Logout}} {{plorabunt:plorabunt_logout.png?300|Logout}}
 +----
 ==== Navigation and breadcrumb ==== ==== Navigation and breadcrumb ====
  
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, configuration of roles and permissions. |
 +| **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, while maintaining an efficient and collaborative validation process.
 +
  
plorabunt/authentication.1768465192.txt.gz · Last modified: by fincons