===== Resource approval workflow ===== ==== Resource creation and management ==== After logging in, a **Researcher** can click on the **+ Add resource** button (located in the top-right area of the interface) to create a new resource of one of the following types: * **Foundation Legend** * **Ex-Voto** Once the resource form has been completed, the resource can be: * **saved as a draft** (*Save draft*) → the resource remains visible only in the user’s personal Dashboard; * **submitted for approval** (*Submit*) → the resource enters the review phase and is forwarded to the WPLead. {{sanctuaria:sanctuaria_dashboard_view.png?650|Dashboard View}} ---- ==== Dashboard and Contributions ==== From the user menu (profile icon located in the top-right corner), users can access the **Dashboard**, which includes the *Contributions* section. **Researcher role** Researchers can view and manage only their own resources, which may have the following statuses: * **Draft** → editable, deletable, or submittable for approval; * **Submitted** → pending review by the WPLead; * **Rejected** → returned to Draft status, accompanied by a rejection message explaining the motivation; * **Approved** → published resources, no longer editable by the Researcher. **Available actions for Researchers** ^ Action ^ Resource status ^ Description ^ | **Edit** | Draft / Rejected | Allows updating resource fields before resubmission. | | **Submit** | Draft | Sends the resource to the WPLead for approval. | | **Delete** | Draft / Rejected | Permanently removes the resource. | | **View** | All statuses | Displays the full content of the resource. | **WPLead role** WPLeads can view all resources submitted by Researchers and perform the following actions: ^ Action ^ Description ^ | **Approve** | Accepts the resource, which becomes published. | | **Reject** | Returns the resource to the Researcher with a textual motivation. | | **Delete** | Permanently removes the resource. | | **View** | Opens the resource for content verification. | ---- ==== Operational workflow ==== The standard lifecycle of a resource follows the workflow described below: **Draft → Submitted → In Review → [Approved | Rejected → Draft]** **Standard approval flow (Researcher → WPLead)** * The Researcher creates a resource and saves it as a Draft. * Once the compilation is completed, the Researcher selects *Submit* to send the resource for review. * The resource enters the *In Review* state and becomes visible to the WPLead. * The WPLead evaluates the resource and may: * **Approve** → the resource is published and becomes publicly visible in the database; * **Reject** → the resource is returned to the Researcher with a motivation and reverts to Draft status; * **Delete** → the resource is removed from the system. In the case of rejection, the Researcher can modify the resource and resubmit it for a new evaluation. **Direct workflow (WPLead)** WPLeads are also allowed to directly create new resources. In this case: * the resource bypasses the review process; * it is automatically assigned the **Approved** status; * it is immediately published on the SANCTUARIA platform. This functionality is reserved for WPLeads and is intended for the insertion of pre-validated content or materials originating from official project sources.