The full documentation of 4HSE # Guides --- # Action forms --- # Forms Linked to Actions > How to create and complete operational forms associated with an action. **Forms linked to actions** are a key tool for operational safety management in 4HSE. This feature allows you to integrate checklists, attendance registers, or custom forms directly into the workflow of preventive actions. Planned activities are enhanced with structured documents: in addition to attaching external files, the system allows you to complete and attach predefined templates. ## Why Use Linked Forms [Section titled “Why Use Linked Forms”](#why-use-linked-forms) Associating forms with actions helps structure and improve data collection during activities, making the process more consistent, traceable, and efficient. * **Standardization of information** Forms define preconfigured checklists and fields, ensuring that each activity is documented in a uniform and comparable way over time. * **Activity traceability** Forms are automatically linked to the items generated during the activity (for example, certificates or individual sessions), keeping all relevant information connected. * **Real-time data collection** Forms can be completed directly during the execution of the activity, **also from mobile devices**, reducing errors, omissions, and subsequent transcription tasks. ## Configuration and Completion [Section titled “Configuration and Completion”](#configuration-and-completion) To use this feature correctly, it is important to distinguish between two phases: 1. **Configuration:** Define the structure and contents of the form. This operation is performed only once at the **Action** level. 2. **Completion:** Enter the data required by the form during the activity. Each save generates a static document linked to the performed activity. ## Form Configuration [Section titled “Form Configuration”](#form-configuration) Forms are defined at the **action** level. In this phase, you determine which “template” will be used each time the action is executed. Within the action detail view, there is a **Linked Forms** tab. In this section, you can view the list of already active forms, create new ones, or remove those no longer needed. ### Creating a New Form [Section titled “Creating a New Form”](#creating-a-new-form) To create a new form, click the **New** button. A guided wizard will open to assist you with the configuration. In the first step, you must define the main information of the form.  #### 1. General Information [Section titled “1. General Information”](#1-general-information) ##### Name [Section titled “Name”](#name) Identifies the form within the system. It is recommended to use a clear and descriptive name that makes its purpose and context of use easy to understand. ##### Type [Section titled “Type”](#type) The **Type** defines the type of form you want to configure. The availability of form types depends on the nature of the selected action: there are universal templates applicable to any preventive activity, and specific templates dedicated to particular operational workflows. Below is a detailed list of the available types: | Form Type | Applicability | Description | | ------------------------------ | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Simple Checklist** | All actions | Customizable form composed of different field types: checkboxes, text inputs, text areas, dropdown menus, radio buttons, selection groups, and signature. Includes completion date. | | **Advanced Checklist** | All actions | More comprehensive form that allows adding extra fields and setting custom completion rules. | | **Course Attendance Register** | “Training” actions | Specific form for recording participant attendance during training sessions. | | **Evacuation Drill** | “Procedure” actions | Structured form for recording and evaluating emergency and evacuation drills. | | **DPI delivery form** | “Personal protection” actions | A form with pre-filled data and checkpoints for DPI delivery. | Note The choice of **Type** determines the available fields and the completion logic that will be provided to the operator during field activity execution. #### 2. Content Definition [Section titled “2. Content Definition”](#2-content-definition) In the final step of the wizard, you can define the content of the form. ### Simple Checklist [Section titled “Simple Checklist”](#simple-checklist) This tool is ideal for creating custom operational forms, where the operator can confirm the completion of activities, enter textual information, make selections from predefined lists, or provide a signature. Once this type has been selected and the general information has been saved, the system enables an intuitive editor that allows you to configure the form by defining the fields associated with the action. #### Available field types [Section titled “Available field types”](#available-field-types) The editor provides the following field types, which can be added using the dedicated buttons at the bottom of the editor: | Field type | Description | | ------------------- | --------------------------------------------------------------- | | **Checkbox** | Single checkbox to confirm the completion of an activity. | | **Text input** | Single-line field for entering short text. | | **Text area** | Multi-line field for entering longer text. | | **Dropdown menu** | Single selection from a list of predefined options. | | **Radio buttons** | Single selection from a set of options displayed as buttons. | | **Selection group** | Multiple selection from a set of options (multiple checkboxes). | | **Signature** | Dedicated field for applying a digital signature. | For **dropdown menu**, **radio buttons**, and **selection group** fields, you need to define the available options directly in the editor. Each option can be added or removed individually. #### Field configuration [Section titled “Field configuration”](#field-configuration) For each field, you can specify: * **Question or label:** the text that will be shown to the operator during completion. * **Description (optional):** an additional note or instruction to guide the operator. #### Available editor operations [Section titled “Available editor operations”](#available-editor-operations) Using the editor, you can: * **Add new fields:** select the desired field type using the buttons at the bottom. * **Reorder fields:** drag items to define the logical sequence the operator should follow. * **Delete fields:** remove fields that are no longer needed.  *simple checklist editor* Once you have completed the form definition, click **Save** to activate it. From that moment on, the form will be available and ready to be completed each time the action is executed (for example, during an inspection or maintenance activity).  *simple checklist completion screen* ##### Where the Simple Checklist Is Completed [Section titled “Where the Simple Checklist Is Completed”](#where-the-simple-checklist-is-completed) The simple checklist completion will be prompted when creating a new certificate related to the action to which the checklist has been associated. ### Advanced Checklist [Section titled “Advanced Checklist”](#advanced-checklist) By selecting the **Advanced Checklist** type, the 4HSE Designer opens—a flexible tool that allows you to go beyond a simple task list. When opened, the system provides a predefined checklist template as a starting point. The Designer adapts to the user’s experience and needs: you can drag elements one below the other, duplicate them, or create actual layouts and configure dynamic behaviors to be applied during form completion. Despite its advanced features, it remains intuitive: simply drag & drop elements into the workspace to configure the form and select an element to open its customization panel.  *advanced checklist editor* ##### Where the Advanced Checklist Is Completed [Section titled “Where the Advanced Checklist Is Completed”](#where-the-advanced-checklist-is-completed) The advanced checklist completion will be prompted when creating a new certificate related to the action to which the checklist has been associated. ### Course Attendance Register [Section titled “Course Attendance Register”](#course-attendance-register) The **Course Attendance Register** type is specific and exclusive to **Training** actions. Unlike checklists, this form does not require manual configuration of content: the system automatically generates the register structure. To activate it, simply create the form by selecting **Course Attendance Register** as the type and save. From that moment on, the form will be associated with all course sessions linked to the training, automatically importing the list of workers enrolled in each session. ##### Where the Attendance Register Is Completed [Section titled “Where the Attendance Register Is Completed”](#where-the-attendance-register-is-completed) 1. Access the **Sessions** section of the training courses; 2. Locate the course session to which the attendance register has been associated; 3. Select the relevant session date (DATE tab); 4. Click the **Run** button.  Tip Make sure to enroll participants in the session before completing the attendance register. The system will open the register with preloaded names, allowing the assigned person to record attendance in real time, including entry and exit times along with participant signatures.  Note Since the form is dynamic, any changes to the session’s enrollment list will automatically be reflected when opening the attendance register, without needing to reconfigure the form. ### 4HSE Predefined Templates [Section titled “4HSE Predefined Templates”](#4hse-predefined-templates) In addition to generic checklists, 4HSE provides **predefined templates** designed to meet specific regulatory and operational requirements. The system displays templates in the **Type** dropdown menu only when they are consistent with the category of the action you are configuring. For example: * The **Evacuation Drill** template can only be selected for **Procedure** actions. * The **Fire Extinguisher Maintenance** template is available exclusively for **Maintenance** actions. #### Advantages of Predefined Templates [Section titled “Advantages of Predefined Templates”](#advantages-of-predefined-templates) * **Ready-to-use structure:** the form is already configured with the necessary fields (e.g., evacuation times, inspection outcomes), allowing you to be operational within seconds. * **Full flexibility:** even though the form is ready, the system still opens the 4HSE Designer. You can use the form as is or modify it by adding or removing fields to adapt it to your company standards. * **Standardization:** ensures that all technicians or safety managers collect the same information in a uniform way. Note The predefined template library is continuously updated. ##### Where Predefined Templates Are Completed [Section titled “Where Predefined Templates Are Completed”](#where-predefined-templates-are-completed) The completion of predefined templates will be prompted when creating a new certificate related to the action to which the template has been associated. *** ## Executing Forms in the Operational Workflow [Section titled “Executing Forms in the Operational Workflow”](#executing-forms-in-the-operational-workflow) Forms are integrated into the operational workflow of activities. There is no need to search for them in a separate archive: the system automatically prompts them when needed. Currently, there are two main access points for completion, depending on the type of activity. ### 1. Completion via Toolbar [Section titled “1. Completion via Toolbar”](#1-completion-via-toolbar) This is the case, for example, for a course attendance register. The usage mode of this type of form has already been described in the dedicated section; a brief summary is provided below. In the **Sessions** sections, by clicking on a session date, the system activates the **“Form Completion”** button in the toolbar. By clicking the icon: * the list of forms associated with that context opens; * you can select, open, and complete the desired form. This is the operational path intended for those responsible for tracking attendance. Note During attendance form completion, it is possible to retain entered data over time (for example, between participant entry and exit, which may occur hours apart). If the form is closed using the “X” and later reopened, the previously entered data will still be available. #### Where to View the Saved Form [Section titled “Where to View the Saved Form”](#where-to-view-the-saved-form) Once saved, the register becomes a document attached to the session date. To view it: * Open the session date detail (double click); * Click on the **Attachments** section, where the generated `.html` file will be available. ### 2. Completion During Certificate Issuance [Section titled “2. Completion During Certificate Issuance”](#2-completion-during-certificate-issuance) For all other types of forms, completion is linked to the generation of documentary evidence. When issuing a new certificate related to an Action that has linked forms, the system intervenes in the workflow: * **Automatic prompt:** before finalizing the certificate, 4HSE displays the associated form completion screen. * **Data integration:** the data collected in the form (e.g., checklist results) becomes an attachment to the certificate being issued.  By clicking the **“Complete”** button, you access the form completion screen, where you can enter the required data and provide a signature where applicable. By clicking **“Save”**, the form is saved and attached to the certificate and is no longer editable. Note As a rule, completing forms associated with the session is not mandatory in order to proceed with certificate issuance. The exception is forms marked as **required**: when an action includes one, the certificate cannot be finalized until those forms have been completed. See [Permit to Work](/guides/permit-to-work/permit-to-work/). ### Form Completion States [Section titled “Form Completion States”](#form-completion-states) During completion, the form can have two main states: **Draft** Allows you to retain entered data without completing the form. In this state, the form remains editable and can be reopened temporarily to complete or update information. Caution Drafts are temporary and are not available in case of device or browser change. It is recommended to perform the final save once completion is finished. **Final Save** Confirms form completion and concludes the process. After final saving, the content is no longer editable.  *** ## Example: PPE Delivery Checklist Attached to the Certificate [Section titled “Example: PPE Delivery Checklist Attached to the Certificate”](#example-ppe-delivery-checklist-attached-to-the-certificate) A company must manage the delivery of personal protective equipment (PPE) to its employees, ensuring that each delivery is carried out correctly and fully documented. To support this process, a form **linked to the PPE delivery certificate** is created using the **Checklist** style. ### Creating the Form [Section titled “Creating the Form”](#creating-the-form) The safety manager creates a new form named: **Safety Helmet Delivery Verification** The form includes the following checks: * Verification of PPE and packaging integrity; * Shell integrity (absence of cracks or dents); * Proper functioning of the adjustment system (headband); * Verification of correct employee identification; * Employee signature for receipt; This checklist allows the assigned person to follow a standardized procedure during each delivery. ### Completion During Delivery [Section titled “Completion During Delivery”](#completion-during-delivery) When a delivery is made and the certificate is being issued, the system makes the associated checklist available. The delivery officer: * opens the form via the “Complete” button; * fills in the required checks; * signs the form; * performs the final save.  Once the completion of the necessary forms is finished, the assigned person proceeds with certificate issuance by clicking **Create Certificate**.  ### Final Result [Section titled “Final Result”](#final-result) Upon final saving: * the checklist is generated as a document; * the system prompts the user to select the destination folder where the file will be saved; * the document is archived in the filesystem; * the file is automatically **attached to the PPE delivery certificate**; * the checklist becomes an integral part of the delivery documentation. In this way, the document is archived within the project folders and directly accessible from the certificate, ensuring traceability and ease of consultation. Note The system generates attached files in html format.  --- # AI --- # MCP Server > Integrate 4HSE with AI tools like Claude, ChatGPT and other clients compatible with the MCP (Model Context Protocol) The **MCP (Model Context Protocol)** server of 4HSE allows external AI tools, consumer AI clients, agentic systems and enterprise automation platforms to interact with the 4HSE instance. Through MCP it is possible to manage 4HSE system data using the preferred AI client, without needing to access the web interface. Common use cases: * **Consumer AI clients**: Claude.ai, ChatGPT and other MCP-compatible clients * **Automation systems**: Workflow orchestration, business process automation * **Enterprise integrations**: API platforms, middleware, custom agentic frameworks The server provides access to the tools for managing data and projects in 4HSE with the same operations available from the web interface. Note The MCP service is free for all 4HSE users. No additional costs apply beyond your 4HSE subscription. ## How to Connect [Section titled “How to Connect”](#how-to-connect) Connecting to the 4HSE MCP server requires entering the correct URL in the AI client. The URL identifies the 4HSE instance and allows the client to access the user’s data. The base URL is: `https://mcp.4hse.com/4hse` Caution If your 4HSE user account is associated with a specific tenant, replace `4hse` with the tenant name. Example: if the tenant is “acme”, the URL will be `https://mcp.4hse.com/acme` For more information on the tenant name, contact support: Authentication takes place via 4HSE’s Single Sign On (SSO), the same system used by other 4HSE applications. Anyone with access to 4HSE automatically has access to the MCP server with the same permissions. ### Claude.ai [Section titled “Claude.ai”](#claudeai) 1. Go to [claude.ai](https://claude.ai) 2. Open settings (account settings) 3. Find the “Connected Apps” or “Integrations” section 4. Select “Add MCP Server” 5. Enter the MCP server URL and 4HSE credentials 6. After connecting, you can manage 4HSE data through the AI client For detailed instructions, consult the [official Claude documentation](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp#h_3d1a65aded). ### ChatGPT [Section titled “ChatGPT”](#chatgpt) 1. Go to [chat.openai.com](https://chat.openai.com) 2. Open settings (settings) 3. Navigate to the “Integrations” or “Connected Services” section 4. Select “Add Custom Integration” 5. Enter the MCP server URL 6. Complete authentication via 4HSE SSO For detailed instructions, consult the [official OpenAI documentation](https://platform.openai.com/docs/mcp#connect-in-chatgpt). ### Other Clients and Integrations [Section titled “Other Clients and Integrations”](#other-clients-and-integrations) For agentic systems, enterprise automation platforms and other MCP-compatible clients, the connection procedure varies depending on the specific system. Consult the system’s documentation for MCP integration instructions, then provide the 4HSE MCP server URL and complete authentication via SSO. ## Capabilities [Section titled “Capabilities”](#capabilities) The MCP server exposes the same operations available through the [Operations Assistant](/guides/ai/overview/#operations-assistant) of the integrated AI. The difference is that these operations are performed by the external AI client (Claude, ChatGPT, etc.) instead of the 4HSE integrated chat. The exposed tools are grouped by area: | Area | Operations | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Search** | Search people, resources (equipment, PPE, substances, work environments), actions, projects, offices, job positions/homogeneous groups, and incidents | | **Compliance** | Review the compliance schedule and view upcoming scheduled sessions | | **Organization** | Create and manage safety roles, job positions, work phases, and homogeneous groups, assigning people and resources | | **Profiling** | Profile new people and resources and subscribe them to the relevant actions | | **Actions & sessions** | Create preventive actions, schedule sessions, and create certificates and proofs of compliance | | **Incidents** | Report incidents and link corrective actions to them | | **Documents** | Attach files to 4HSE entities | For practical request examples, see the [Operations Assistant](/guides/ai/overview/#operations-assistant) section. ## Limitations [Section titled “Limitations”](#limitations) The MCP server: * Does not provide commercial information or regulatory advice * Does not access data of other users * Cannot access local computer files * Follows the same permissions as the 4HSE user account For technical issues: --- # Artificial Intelligence > Learn what 4HSE AI is, how it works, and what it can do to support you in managing occupational safety The artificial intelligence integrated into 4HSE is an **intelligent virtual assistant** available 24/7 that operates in the management of occupational safety. Through natural conversation, you can ask the AI to retrieve information, perform operations in the system, and obtain consultation on regulatory and technical aspects. Beta feature The integrated AI is currently in **beta** and available only to selected customers. To request activation, write to . ## Availability [Section titled “Availability”](#availability) The integrated AI feature is available to all users with **admin** or **manager** role in a corporate project or multi-company account. AI usage is based on a **credit system**. Each organization receives **100 free credits** that renew monthly. Each interaction with the AI consumes a small amount of credits based on the complexity of the request. Caution Free credits are a promotional offer. 4HSE reserves the right to modify or discontinue this offer at any time. To purchase additional credits, contact . 4HSE integration with external AI tools such as **Claude**, **ChatGPT** or other **MCP** clients is also available to everyone. Consult the dedicated documentation on [4HSE’s MCP server](/guides/ai/mcp-server). ## Integrated Desktop Chat [Section titled “Integrated Desktop Chat”](#integrated-desktop-chat) The 4HSE AI is easily accessible directly from the desktop application. In the main 4HSE bar, at the bottom right, you will find a chat icon. Clicking it will open the AI assistant window where you can start conversing immediately. The chat window shows the list of previous conversations on the left and the active chat on the right. You can start new conversations and delete previous ones. At the bottom left, the bar showing credit usage and remaining credits is visible.  *** ## Specialized Agents [Section titled “Specialized Agents”](#specialized-agents) The 4HSE AI uses a system of **specialized agents** that are automatically activated based on the type of request. There is no need to manually choose which agent to use: the AI analyzes the question and routes it to the most appropriate agent. ### Operations Assistant [Section titled “Operations Assistant”](#operations-assistant) The main agent that performs concrete operations in the 4HSE system. Through natural language, you can request searches, creation, and data management without manually navigating the interface. The Operations Assistant runs on the [4HSE MCP server](/guides/ai/mcp-server): see the [Capabilities](/guides/ai/mcp-server/#capabilities) section for the full list of available operations (search, compliance, safety organization, profiling, actions and sessions, incidents, documents). You can also attach files (PDF, images, Office documents, CSV) to the conversation: the AI automatically extracts the useful information to perform the operations. Examples * *“What projects do I have?”* * *“Search for Mario Rossi in the MyCompany project”* * *“Show me the expiring items for the Milan site”* * *“Give me an overview of the safety status of the MyCompany project”* * *“Create the Fire Safety course at the Workshop site of the MyCompany project”* * *“Create the Electrician job position at the Workshop site with required action Fire Safety Course”* * *“Profile Giovanni Bianchi at the Milan site, job position Warehouse Worker, role RSPP, must attend the Fire Safety Course”* * *“Schedule the First Aid Course for Luca Verdi on May 15, 2026 at 9:00 AM”* * *“Report an accident: fall from ladder in the warehouse, involving Mario Rossi”* * Attach a scan of a certificate and ask *“Register this certificate”* ### User Guide [Section titled “User Guide”](#user-guide) Provides practical, step-by-step instructions on how to use the 4HSE interface. Explains where to click, which menus to open, and how to complete operations manually. Examples * *“How do I add a person to a project?”* * *“How do I configure email notifications?”* * *“What is the difference between an action and a certificate?”* * *“How do I delete expired sessions?”* ### Developer [Section titled “Developer”](#developer) Provides technical assistance on APIs, endpoints, authentication, webhooks, integrations, and configurations for developers who want to integrate or customize the 4HSE platform. Examples * *“How do the 4HSE APIs work?”* * *“How can I integrate 4HSE with my management system?”* * *“What is the API authentication format?”* ### Regulatory Consultant [Section titled “Regulatory Consultant”](#regulatory-consultant) Provides consultation on occupational safety regulations, legal obligations, and industry best practices, integrating the information with 4HSE features. Examples * *“What are the mandatory courses for the construction sector?”* * *“How does Italian Legislative Decree 81/08 apply in our context?”* * *“What PPE is mandatory for working at height?”* ### Commercial Advisor [Section titled “Commercial Advisor”](#commercial-advisor) Functions as a commercial consultant that understands the organization’s needs and illustrates how 4HSE can support compliance and safety requirements. Examples * *“How can I manage regulatory compliance for my sector with 4HSE?”* * *“What features are available to automate training management?”* * *“How can I request a demo?”* *** ## Limitations [Section titled “Limitations”](#limitations) * **Operations not yet supported**: The AI cannot delete data, create or modify projects and sites, manage users and permissions, or modify existing sessions and certificates. For these operations, use the 4HSE interface (the guide agent can explain how) * **Does not provide official legal advice**: The AI provides general guidance on regulations, not binding legal advice. For critical legal matters, consult a qualified professional (RSPP, consultant, lawyer) * **Does not replace emergency procedures**: The AI is not a tool for emergency situations or critical safety. In case of danger, always follow company protocols and contact the competent authorities * **Memory limited to the current conversation**: The AI only remembers what has been said in the current conversation. Each new conversation starts from scratch Caution Always verify the information provided by the AI, especially for critical issues of compliance, safety, and regulatory conformity. The AI is a support tool, not a source of definitive authority. *** ## Best Practices [Section titled “Best Practices”](#best-practices) * **Use natural language**: The AI understands names of people, projects, sites, and resources. Write *“Search for Mario Rossi in the MyCompany project”* * **Be specific when necessary**: Providing details narrows results. *“Show me certificates expired in the last 30 days at the Milan site”* is more useful than *“Show me the certificates”* * **Leverage the conversation context**: The AI maintains context, so after a first question you can say *“List them by name only”* without repeating the context * **Follow the correct workflow**: For complex operations, follow the logical order. For example, first create roles and job positions with the respective commands, then profile people by assigning them to existing roles and job positions * **Verify important information**: For critical decisions, verify the results directly in the 4HSE interface --- # Configurations --- # Default Roles > Guide to configuring default roles in 4HSE The **Default Roles** configuration allows you to define the roles of *Responsible*, *Observer*, and *Assignee*, which will be automatically assigned to all new prevention actions (and their sessions) created within the project. This feature is available in the project menu under: **Administration > Configuration > Default Roles**.  ## Overview of Operational Levels [Section titled “Overview of Operational Levels”](#overview-of-operational-levels) 4HSE distinguishes two operational levels for prevention actions: * **Action Definition** — e.g., Course, Equipment, Plan * **Action Planning/Execution** — e.g., Edition, Delivery, Order Default roles can be defined for both levels in all prevention areas: | Prevention Area | Action (Definition) | Session (Planning) | | ------------------- | ------------------- | ------------------ | | Training | Courses | Editions | | Personal Protection | PPE Equipment | PPE Deliveries | | Maintenance | Maintenance Plans | Orders | | Procedures | Procedures | Reports | | Health Surveillance | Prescriptions | Visits | ## Assigning Roles [Section titled “Assigning Roles”](#assigning-roles) To assign a default role to an action or session: 1. Open the **Default Roles** panel. 2. Locate the section for the action type (e.g., Training). 3. Click the **+** button next to the role to assign (*Responsible*, *Observer*, *Assignee*). 4. In the selector, you can choose between: * People registered in the project * Project users (email) Caution Roles configured in this section are automatically inherited by **all** corresponding actions and sessions created afterwards.  ## Receiving Notifications [Section titled “Receiving Notifications”](#receiving-notifications) For the selected people to receive role-related notifications (email or digest), they must **be associated with an active account within the project**. Alternatively, you can assign a user/email directly to the role. ## Modifying Inherited Roles [Section titled “Modifying Inherited Roles”](#modifying-inherited-roles) Roles configured in **Default Roles** act as *default values*. To modify the roles for a single action or session: 1. Select the specific action (e.g., a course, a maintenance plan). 2. Open the **Details** panel. 3. Modify the *Responsible*, *Observer*, or *Assignee* fields as needed. Changes made here override the default value **only for that specific item**.  *Action details in the office menu* --- # Notifications and Digest > Guide to configuring and managing notifications and digest summaries in 4HSE: how to set notification preferences, recipients, timing, and automatic activity overviews. In 4HSE, **notifications** and **digests** play complementary roles in keeping users informed about tasks and deadlines. **Notifications** are real-time alerts triggered by specific events, such as upcoming deadlines or status changes. **Digests**, on the other hand, are periodic email summaries—sent daily, weekly, or monthly—that collect all upcoming or overdue and new activities, providing a comprehensive overview for better planning and strategy. This guide explains how to configure both communication methods to fit individual and project needs, optimizing information flow and coordination. ## Notification Settings [Section titled “Notification Settings”](#notification-settings) Within the platform, **notifications** can be managed flexibly by defining: * **Notification preferences** at the project and office level, for the following areas: PPE, training, appointments, maintenance, procedures, and health surveillance; * **Who should receive the notifications** (specific recipients); * The **time interval** for notification delivery. ### Notification Overview [Section titled “Notification Overview”](#notification-overview) **Sending**: * Notifications are triggered automatically when a **user is assigned a role in an action** (Recipient, Assignee, Observer, Manager). **Receiving**: * Occurs according to **default parameters**, visible under: *Administration → Configuration → Notifications*; * No customization is required to enable notification delivery; * Users can customize how they receive notifications via **notification preferences** (Administration → Configuration → Notifications). **Customization**: * Customization is **optional**; * It is a **project-specific setting**, meaning each project can define its own rules; * It only affects **how notifications are received** (not the sending mechanism). Caution Notifications are based on the user’s functional role in a specific action (e.g., Training Observer) and **not** on their general user role in the project (e.g., Office Manager). **All users assigned as Recipients, Managers, Assignees, or Observers of a specific action will automatically receive notifications according to the default settings.** ### How to Enable Notifications [Section titled “How to Enable Notifications”](#how-to-enable-notifications) 1. **Add the user profile** under the *People* menu of a project (e.g., John Doe). 2. **Assign the user a project permission and a non-”na” role** in the *Permissions* menu. *(e.g., Figure 1: John Doe as project admin.)*  3. **Associate the user or an HSE role with specific actions** as Manager, Observer, or Assignee. All registered users are considered Recipients. (e.g., John Doe as Manager and Observer for all Maintenance actions in the project).  You can also assign roles to **specific actions**: For example, user Emily Carter is the Manager only for the “Emergency Plans” procedure action at the Los Angeles office. After adding him to the project, the role is assigned in the *Action details* area.  ### Notification Preferences [Section titled “Notification Preferences”](#notification-preferences) Notifications are received based on: * **Section**: The action or management context (e.g., Training, Appointments); * **Event**: Based on the expiration date of the latest valid record or the date of the upcoming scheduled event; * **Role**: The user’s role in the action (Manager, Observer, Assignee, Recipient). All registered users are considered Recipients; * **Interval**: The time range used for calculation; * **New**: includes registrations with status “New” in the notification, treating them as activities to be regularized (option available only when the “Expiration” event is selected); * **When**: Option to define a lead or delay time (in days) relative to the interval.  Note Notification preferences can be configured from the project’s administration menu, under “Configuration” → “Notifications”. ## Digest Configuration [Section titled “Digest Configuration”](#digest-configuration) The digest is a periodic email summary of upcoming or overdue activities. ### What Can Be Configured in the Digest [Section titled “What Can Be Configured in the Digest”](#what-can-be-configured-in-the-digest)  In the **Digest Preferences** section of the user menu, you can: * Set digest preferences for each section: PPE, training, appointments, maintenance, procedures, and health surveillance; * Define the **time interval** for receiving digests; * Choose the digest frequency (daily, weekly, monthly) and the exact day of delivery. ### Simple Configuration [Section titled “Simple Configuration”](#simple-configuration)  The simple mode allows you to receive a weekly or monthly summary of activities that are due, overdue, or newly created (status “new”), choosing your preferred day of delivery. For more advanced settings, use the advanced configuration. ### Advanced Configuration [Section titled “Advanced Configuration”](#advanced-configuration)  The advanced configuration lets you define: * **Frequency**: daily, weekly, or monthly; * **Specific day** of the month or week for delivery; * **Event type**: upcoming or scheduled activities; * **New**: includes registrations with status “New” in the digest; * **Action type**: select which actions to monitor; * **When**: the time window in which to search for deadlines or scheduled activities to include in the digest; **Example**: You want to receive a monthly digest on the 10th of each month with deadlines for training actions expiring in the next 60 days. Here is how to fill out the form:  --- # Risk Assessment > How to configure risk assessment in a project, choose the most suitable risk aggregator, and understand its impact on the safety management process. The **Risk Assessment** section, available in the project configuration, allows you to select the risk aggregator that will be used as the basis for the project’s risk analysis. This configuration can be accessed from the project menu by navigating to: **Administration > Configuration > Risk Assessment**  ## Choosing the risk aggregator [Section titled “Choosing the risk aggregator”](#choosing-the-risk-aggregator) The risk aggregator defines which structure is used to identify hazards, assess risks, and organize safety-related information. In **4HSE**, the following risk aggregators are available: ### Work phase [Section titled “Work phase”](#work-phase) Allows risks to be assessed based on specific operational activities carried out within the organization. This is the most common approach and is recommended when risk assessment is structured around actual work activities. ### Job [Section titled “Job”](#job) The assessment focuses on risks associated with a specific job role. This option is suitable for organizations with clearly defined and stable roles. ### Homogeneous group [Section titled “Homogeneous group”](#homogeneous-group) Allows workers exposed to similar risks to be grouped together, focusing the assessment on the group as a whole. This is useful when multiple workers share the same exposures regardless of individual activities or roles. ## When to choose one aggregator over another [Section titled “When to choose one aggregator over another”](#when-to-choose-one-aggregator-over-another) The choice of aggregator depends on how the organization structures its safety management system: * choose **Work phase** if risk assessment is centered on operational activities and processes; * choose **Job** if risks are mainly associated with professional roles; * choose **Homogeneous group** if the assessment is based on groups of workers with similar exposures. There is no universally “correct” choice: the key point is that the selected aggregator reflects the organizational model and the adopted safety management approach. ## Practical consequences of the choice [Section titled “Practical consequences of the choice”](#practical-consequences-of-the-choice) Once the risk aggregator has been selected and saved, the corresponding aggregator detail view is extended with dedicated sections for risk management. Specifically, the structure is expanded to allow you to: * identify hazards and risks; * define prevention and protection actions; * manage the information required for risk assessment.  *Dedicated risk management sections, shown here within the work phase details* --- # Copy --- # Copying Elements > How the copy tool works in 4HSE: logic, element types, and guided procedure. Detailed example: copying a work phase. The **Copy from** feature allows you to replicate existing elements from a **source office** to a **destination office**, preserving linked relationships and simplifying the creation of similar structures across multiple contexts. *** ## Copy Logic and Process [Section titled “Copy Logic and Process”](#copy-logic-and-process) The copy process is based on the ability to replicate an element from a source office to a destination office. This functionality is not limited to user-created elements, but also extends to predefined content available in 4HSE. **All elements that can be copied follow the same three-step guided procedure:** 1. **Select** 2. **Filter** 3. **Copy** *** ## Distinction Between Offices and Elements [Section titled “Distinction Between Offices and Elements”](#distinction-between-offices-and-elements) The copy system distinguishes elements based on the type of office in which they were created: * **Template Elements** created in *template* offices, designed as reference models with standardized and pre-filled data. * **Non-Template Elements** created in “real” offices within the user’s project. * **Partner Templates** Template offices created by a partner, visible only to that partner’s clients. *** ## Interface and Available Options [Section titled “Interface and Available Options”](#interface-and-available-options) When you want to create a new element, the **toolbar** in the section includes the **New** button. Clicking this button reveals three menu options: * **New** * **Copy from…** * **Create from template** ### Copy from… [Section titled “Copy from…”](#copy-from) This option allows copying existing elements from offices of projects you have access to. In the toolbar of the element list, a filter is available: * **This project**: shows only elements from the current project * **This office**: shows only elements from the current office ### Create from Template [Section titled “Create from Template”](#create-from-template) This option allows creating elements by copying them from *template* projects. Two additional filters are available in the element list toolbar: #### Source Filter [Section titled “Source Filter”](#source-filter) * **Partner**: shows only partner templates * **4HSE**: shows only 4HSE global templates #### Country Filter [Section titled “Country Filter”](#country-filter) * **France** * **Germany** * **Italy** * **Spain** * **United Kingdom** * **USA** *** ## Guided Procedure (Common Steps) [Section titled “Guided Procedure (Common Steps)”](#guided-procedure-common-steps) All elements follow this three-step guided procedure. Below is a general description of each step. ### 1. Select [Section titled “1. Select”](#1-select) This step displays a table containing all copyable entities of the projects/offices you have access to, depending on the option selected (Copy from… or Create from Template). The user selects one or more elements to copy to the destination office. ### 2. Filter [Section titled “2. Filter”](#2-filter) The screen is divided into two main areas: 1. **Navigation Tree**: list of elements selected in the previous step with their relationships and hierarchy. 2. **Detail View**: right panel showing the details of the selected element in the tree. The detail panel indicates the status of each sub-element relative to the destination office (e.g., `already present` → will be linked, `not present` → will be created). The user can choose for each sub-element whether to link it, create a copy, or exclude it. ### 3. Copy [Section titled “3. Copy”](#3-copy) In this step, the operation is executed, and the copy outcome is displayed: created elements, linked elements, and any errors or conflicts encountered. *** ## Detailed Example: Copying a Work Phase [Section titled “Detailed Example: Copying a Work Phase”](#detailed-example-copying-a-work-phase) To illustrate the process, let’s consider the **work phases** section of two different offices, which we will use as an example. We have a project called **Acme Inc.**, in which we created two offices: * **London** * **Manchester** Now, let’s assume we want to copy the work phases: * **Cleaning** * **School management and administration** from the *Manchester* office to the *London* office. Each of these phases has associated: * material resources * actions * hazards To start the copy procedure for work phases, go to the **work phases** section of the destination office, in this case **London**. Expand the **New** button and select **Copy from…** to access the copy flow from a real office.  ## Guided Procedure [Section titled “Guided Procedure”](#guided-procedure) The copy procedure consists of three steps: 1. **Select** 2. **Filter** 3. **Copy** ## Step 1 - Select [Section titled “Step 1 - Select”](#step-1---select) This step displays a table containing all work phases of the projects/offices you have access to. To view only the work phases of this project, activate the **This Project** filter.  Select the work phases: * **School management and administration** * **Cleaning** and click **Next**. ## Step 2 - Filter [Section titled “Step 2 - Filter”](#step-2---filter) This step shows a screen divided into two sections: 1. **Navigation Tree**: list of work phases with their related elements, selected in the previous step. 2. **Detail View** of the element selected in the navigation tree. From the navigation tree, select and expand the **School management and administration** work phase. The **New** form on the right and the icon next to the work phase name indicate that this phase is not present in the destination office (**London**) and will therefore be created. Expanding the **Actions** section below, you can see the actions linked to the phase: * **General Training**: theicon indicates that this action already exists in the destination office. By default, the system proposes to link the work phase to the existing action. * **Other Actions**: theicon indicates that the remaining actions are not present in the destination office and will therefore be created and linked to the work phase. Now select the elements you want to copy and click **Confirm**.  ## Step 3 - Copy [Section titled “Step 3 - Copy”](#step-3---copy) In this step, the copy result will be displayed.  *** --- # Events registry --- # Registering Injuries, Incidents, Near Misses, and Non-Conformities > How to register and manage events such as injuries, incidents, near misses, and non-conformities in 4HSE. The **Event Registry** is the section where you can enter: * injuries * non-conformities * incidents * near misses In addition to the **event type**, you can also enter information such as: * *date* * *event description* * *corrective actions* You can also define the people associated with the event in the roles of: * *responsible person* * *assignee* * *observer* * *recipient* ### Example: How to Register an Injury [Section titled “Example: How to Register an Injury”](#example-how-to-register-an-injury) As an example, let’s assume we need to register an **injury**. After clicking **New**, adding the new entry, and filling in all the details related to the injury, the event will appear in the registry list with its code, date, category, and injury name.  By selecting the injury from the list, the **detail view** below will display: * the **details** of the entry * the **people involved** * the **resources** (in this case, the source and resources associated with the incident — for example, a malfunctioning piece of equipment, the presence of a substance, etc.) * the **corrective actions** to be taken * any **documents and/or photos** that can be attached to complete the report  Please note that **there are no limits** to the number of events you can add, nor to the number of photos and documents you can attach. --- # File management --- # Add a New File > How to add, upload, and organize files and folders in the 4HSE archive. Users can add or upload documents within the software’s **file archive**, either at the **project level** or within a **specific office**. The archive functions as a complete file system where uploaded documents can be organized into **folders** and **subfolders**. Documents uploaded at the **project level** are also accessible from the archives of all offices added to the platform. These are considered general-purpose documents, **valid for all included offices**. On the other hand, documents added through the **office menu** are only relevant to the specific office they belong to. ## Uploading a File at the Project Level [Section titled “Uploading a File at the Project Level”](#uploading-a-file-at-the-project-level) 1. Open the project menu and select the **Files** section. 2. Select the target folder and upload the file by clicking **New** and choosing **New File**, or alternatively by dragging it into the desired folder. If you need to create a new folder, you can do so directly from the toolbar by clicking the **New Folder** button.  ## Uploading a File Within an Office [Section titled “Uploading a File Within an Office”](#uploading-a-file-within-an-office) 1. Open the **office menu** and select **Files**.  2. Select the target folder and upload the file by clicking **New** and choosing **New File**, or alternatively by dragging it into the desired folder. If you need to create a new folder, you can do so directly from the toolbar by clicking the **New Folder** button. ## Renaming Files [Section titled “Renaming Files”](#renaming-files) Once a file has been uploaded, you can rename it by right-clicking on the file and selecting **“Rename”**. --- # Download ZIP Files > How to download files and folders as ZIP archives from the 4HSE platform. ## Downloading a Single File [Section titled “Downloading a Single File”](#downloading-a-single-file) By selecting a single file in the file system and clicking the **Download** button, the file will be immediately downloaded to the user’s device. ## Downloading a Folder [Section titled “Downloading a Folder”](#downloading-a-folder) By selecting a folder and clicking **Download**, the system will start creating a ZIP archive containing all files within that folder. ## Monitoring Download Progress [Section titled “Monitoring Download Progress”](#monitoring-download-progress) The creation of the ZIP archive may take some time, depending on the size and number of files in the folder. You can monitor the progress of this process by accessing the **Tasks** section, located in the user menu at the bottom-right corner of the interface. ## Completion Notification and ZIP Download [Section titled “Completion Notification and ZIP Download”](#completion-notification-and-zip-download) Once the ZIP archive has been generated, the user will receive an email containing a download link. The link will remain active for 48 hours from the time of generation. After that, the file will no longer be available for download. Note * If the ZIP file is not downloaded within 48 hours, the process must be repeated to generate a new archive. * ZIP generation time may vary based on the number and size of the files contained in the selected folder. --- # Printing and Exporting > How to print and export documents and certificates in 4HSE in various formats. The **print function** for a document is available next to each item where the icon is displayed. As an **alternative to direct printing**, all templates within the platform can be **exported** in three different formats: * PDF * HTML5 * Microsoft Word ### Template selection [Section titled “Template selection”](#template-selection) When opening the print menu, the system displays a dropdown with the **recently used templates** (up to 5). If this is the first time printing for that context, the field will be empty.  To search for a different template, click the **Search** button. An advanced selection window will open with three selectable filters via the toolbar buttons: * **Current project** (active by default) — shows templates associated with the current project. * **Partner** — shows templates provided by the partner, with the option to filter by country. * **4HSE** — shows templates provided by 4HSE, with the option to filter by country. When selecting the **Partner** or **4HSE** source, a country filter becomes available on the toolbar to narrow down the results. A text search field is also available to quickly find the desired template. Once a template is selected from the window, it will be automatically added to the recent templates list for quicker access in future sessions. ### Template editing [Section titled “Template editing”](#template-editing) You can edit the selected template, including its HTML code, by clicking the **Edit** button . The HTML editing window will open, with a live preview on the left. Once you’ve made your changes, you can save your custom version using the icon and selecting the desired location within the file system of the relevant “Archive” section. Then click **Save**again to confirm.  The modified file will be automatically used for the first export of the document and will then remain available in the recent templates list.  After selecting a template, click **Next** to preview it. By clicking the **print** icon in the upper-left corner, you can use your browser’s print function to **save a .pdf** or **send the document** to a local printer.  Alternatively, by clicking the **Next** button, you’ll proceed to the *Export* section, where you can choose the file format and destination.  When selecting the **Save in documents** option, you’ll be prompted to choose the destination path for the file within the relevant Archive section of the software. If the destination folder does not exist yet, you can create a new one directly from the toolbar by clicking the **New Folder** button. In the following step, you’ll be able to define the **document name**, add a **description**, and **select the people** (or organizational roles) to whom you wish to **send a notification** about the document’s creation.  Clicking **Confirm** will start the export process. You can track its progress in the completion screen that follows. --- # Customizing Templates > How to upload and edit custom or default templates in 4HSE. Users can **upload custom templates** or make **modifications** to the templates already available, directly from the platform, using both the visual editor and the HTML editor. ## Uploading a Template [Section titled “Uploading a Template”](#uploading-a-template) There are several ways to **upload a custom template**, but we recommend doing it via the document archive of the relevant office or project: 1. Open the target office and select **Documents**. 2. Choose the desired **folder** from the tree view, or create a new one. 3. Click on the dropdown menu (new document) and select **New Template**. 4. Here you can upload your custom template (*we recommend some familiarity with HTML and programming languages in general*).  ## Customizing a Default Template [Section titled “Customizing a Default Template”](#customizing-a-default-template) There are also several ways to customize one of the **default templates**. For example, you can modify it directly from the document archive by selecting the relevant folder and template—let’s say a DVR template (see image below).  Click the **edit** button and, in the new window, you’ll be able to modify the existing template. Alternatively, you can edit the template **before printing**. Suppose you need to print a **PPE delivery certificate**. By clicking the **edit** button , the template editor page will open (again, some knowledge of HTML and basic programming is recommended). --- # First steps --- # Account Management Panel > Guide to using the 4HSE account panel to update personal information, change your password, and enable two-factor authentication. The **Account Management Panel** is your personal area where you can view and update your personal information, change your login credentials, and configure your profile’s security settings. You can access it by clicking on your email address in the menu at the bottom-right corner of the main 4HSE interface.  ## Personal Information [Section titled “Personal Information”](#personal-information) In the *Personal Information* section, you can view and update your main account details.  From the side menu, you can: * View the **email address** linked to your account. * Check your **username**. * Change the **interface language**. * Update other personal details, such as first and last name, if available. Note Some fields may be locked for editing, depending on your account permissions or system configuration. After making changes, click **Save** to confirm. ## Access Settings [Section titled “Access Settings”](#access-settings) The *Access Settings* section, available under **Account Security > Access Settings**, allows you to configure authentication options and improve your account security.  ### Password [Section titled “Password”](#password) The password is the primary method for accessing the platform. To change it: 1. Click **Update** in the password section. 2. Enter your current password to verify your identity. 3. Type a new password following the indicated security requirements. 4. Confirm the new password by entering it again. 5. Click **Save** to apply the changes. > **Tip**: Use a strong password with at least 8 characters, including numbers, uppercase and lowercase letters, and special symbols. ### Multi-Factor Authentication (MFA) [Section titled “Multi-Factor Authentication (MFA)”](#multi-factor-authentication-mfa) To increase your account security, you can enable **two-factor authentication** (2FA).\ There are several options for configuring this feature, and you can choose your preferred method. Note If you do not set up two-factor authentication, access will be possible using only your password. #### MFA with Email [Section titled “MFA with Email”](#mfa-with-email) Two-factor authentication via **Email** sends a temporary verification code to the email address associated with your account each time you log in. To enable this option: 1. Go to the *Personal Information* section. 2. Click on **Email OTP**. 3. Select “on” to enable code delivery via email. 4. Click **Save** to confirm.  #### MFA with Authenticator [Section titled “MFA with Authenticator”](#mfa-with-authenticator) Two-factor authentication with an **Authenticator** app requires using a mobile application to generate temporary codes. Some common Authenticator apps are **Google Authenticator**, **Microsoft Authenticator**, **FreeOTP**, or **Bitwarden**. To set up two-factor authentication with an Authenticator app: 1. Go to the *Account Security > Access Settings* section. 2. Click on **Set up Authenticator app**. 3. Scan the QR code displayed on the screen using the Authenticator app installed on your smartphone. 4. Enter the temporary code generated by the app to complete the activation. Once enabled, logging into the system will require entering the code generated by the app, in addition to your password.  --- # Getting Started with 4HSE > Introductory guide to the first login, setup wizard, and 4HSE interface. In this guide, we will see how to perform your first login to 4HSE, how to use the initial setup wizard, and how the 4HSE interface is structured. ## First Login Wizard [Section titled “First Login Wizard”](#first-login-wizard) After entering your username and password, you’ll land on the 4HSE desktop. Here, a guided setup will walk you through the service configuration in two steps: First, you’ll define the project settings for your company. Then, you’ll go through three introductory screens that explain the core elements of 4HSE: project, site, and people.  Caution When we talk about a “project” in 4HSE, we’re referring to a corporate safety management project for a single organization. Each project can include multiple sites, such as a logistics hub or a production unit, for example. ## Interface Overview [Section titled “Interface Overview”](#interface-overview) The 4HSE desktop is divided into two main sections: the **working area (desktop)** (highlighted in red) and the **toolbar** at the bottom (highlighted in blue).  ## Desktop Area [Section titled “Desktop Area”](#desktop-area) On the desktop, there are three service icons: the icon for the 4HSE Docs portal, which is the site you are currently visiting. It contains operational guides and API documentation for continuous integration. The calendar icon provides access to a complete overview of all upcoming and scheduled activities related to all projects and accessible locations. This powerful tool allows you to filter the entered data to view and export only the information relevant to you. The Suppliers icon allows you to view suppliers, giving you the ability to view associated entities and manage their deadlines. All other icons represent the projects you’ve created. Double-clicking a project icon opens that specific project, where you can perform related tasks like [adding sites and people](/guides/first-steps/insert-offices-and-people). ## Toolbar [Section titled “Toolbar”](#toolbar) At the bottom of the screen is the **toolbar**, divided into two main areas: * **Start Menu** (bottom left): Provides access to multi-project management features. * **User Menu** (bottom right): Opens settings for your account and other options: * Account security settings: Clicking on the email opens the account management panel, where you can: * Edit personal information * Configure security settings, such as password and two-factor authentication * Create new projects * [Customize notification and digest settings](/guides/configurations/notifications-and-digest) * Customize layout preferences * Monitor tasks * Log out of the application * **Language Menu**: Allows you to change the language of the 4HSE interface. --- # Importing and Exporting Lists > Guide to importing and exporting lists in CSV format on 4HSE. You can import and export `.csv` files for quick and automated population of various sections. Here’s how: ## Exporting [Section titled “Exporting”](#exporting) By clicking the **CSV export** icon in the grid toolbar, an options dialog will open allowing you to choose the export mode.  ### Export options [Section titled “Export options”](#export-options) The dialog offers two modes: * **Export visible columns only** (default) — the `.csv` file will include only the columns currently visible on screen, preserving the sort order applied to the grid. * **Export all columns** — the `.csv` file will include all available columns. In this mode, sorting is not applied. Note When exporting all columns, the sort order applied to the grid will not be available in the exported file. ## Importing [Section titled “Importing”](#importing) You can import data in `.csv` format by clicking the corresponding icon in the grid toolbar.  A guided import wizard will then start. Here are the steps to follow to import a `.csv` list into the platform. ### Step 1: Select the .csv file [Section titled “Step 1: Select the .csv file”](#step-1-select-the-csv-file) After clicking the “Import” button under the **Select file** tab, drag and drop or manually upload the `.csv` file to import.  Once the file is selected, it will be uploaded to the system and you’ll proceed to the next step. ### Step 2: Choose delimiters and data format [Section titled “Step 2: Choose delimiters and data format”](#step-2-choose-delimiters-and-data-format) Set the file reading parameters: * The **Delimiter** field lets you choose the character used to separate columns. * The **Skip first row** checkbox should be selected if the first row in the `.csv` file contains column headers.  Once you’re done, click **Next**. ### Step 3: Preview [Section titled “Step 3: Preview”](#step-3-preview) In the **Preview** tab, you can choose which columns to import and assign the corresponding values.  After reviewing the data, click **Confirm** to complete the import. --- # Adding Offices and People > Guide to adding operational offices and people to a 4HSE project, with attributes and details. The Offices section of your project lists all the operational **offices** you’ve added. To **add a new office**, simply click the “New” button and fill in the required fields.  By right-clicking on the **grid header**, you can select **additional information** to display in the list of offices. This feature is crucial for effective data export and import via .csv files (only displayed data is exported). From the **toolbar above**, in addition to creating, modifying, and deleting an office, you can also **import/export data in CSV format**.  Selecting a single office from the list opens a detail area for that office, containing the following sections: * **Details**: Contains the detailed fields for the office, the option to view its history , and the ability to initiate project-level prints. * **Attributes**: (see Attributes section) ## Attribute Management [Section titled “Attribute Management”](#attribute-management) The **Attributes** area allows you to enrich resources with specific information by associating customized details. Each attribute is defined by: * **Name:** The identifier of the attribute. * **Unit of Measure:** If applicable, the unit in which the value is expressed. * **Value:** The actual data of the attribute. ### Add an Attribute [Section titled “Add an Attribute”](#add-an-attribute) To add a new attribute, select the **New** icon in the toolbar. At this point, two options are available: * **Standard Attribute:** Selecting this option will open a dialog box with a list of predefined attributes. This allows you to quickly associate common and structured information.  * **Custom Attribute:** If the desired information is not available among the standard attributes, you can create a custom attribute. Simply select **Add custom attribute** and freely define the name, unit of measure, and value.  ### Edit and Delete [Section titled “Edit and Delete”](#edit-and-delete) You can **edit** any attribute (standard or custom) by simply double-clicking on the desired field. To **delete** an attribute, select it and click the **Delete** icon in the toolbar. ### Practical Example [Section titled “Practical Example”](#practical-example) Consider the “Turin Office” resource. You can associate attributes such as: * **Name:** Square Meters * **Unit of measure:** sqm * **Value:** 1500 * **Name:** Wall Height * **Unit of measure:** m * **Value:** 3.2 ## Person [Section titled “Person”](#person) The **Person** section collects the **personal data** of all personnel involved in the project, whether internal or external. From the **toolbar above**, you can: * **Add** a new employee or external person by selecting. * **Quickly search** for a person by first or last name. * **Import/export** user lists in .csv format using theandicons. * **View** inactive person by clicking on. By selecting a person, you can view their **details**, organized into different tabs. Each tab displays specific elements related to the selected person, if present: * **Details:** Shows personal data and basic information. For more on “Associated user” and “User permissions,” refer to the [Related User](/guides/permissions/related-user) and [Permissions System](/guides/configurations/permission-system) sections. * **Contacts**, which allows you to enter various contact channels. Note Emails entered in contacts are for informational purposes only and do not enable automatic notification receipt for the employee. To configure notifications, please refer to the [Adding and Managing Users](/guides/configurations/add-managing-users) section. * **Work Phases:** Displays the work phases associated with the person. * **Duties:** Lists the duties held. * **Homogeneous Groups:** Shows the homogeneous groups they belong to. * **Organizational Units:** Indicates the relevant organizational units. * **Safety Organizational Chart:** Details the specific roles assumed in the context of safety. * **Actions:** Lists assigned preventive actions. * **Events:** Contains a list of accidents, near misses, or non-conformities in which the person was involved. * **Attachments:** Displays documents attached to the person. In addition to modifying personal data, you can **view the history** of changes by clicking the icon and **print the summary sheet** for the person via theicon.  --- # Login and Password Reset > Guide to logging into the 4HSE system and resetting the password in case of loss. Managing access credentials is a key element for ensuring data security in 4HSE. This guide describes the authentication process, how to update a password, and solutions for the most common access issues. ## 1. Login Page and Access [Section titled “1. Login Page and Access”](#1-login-page-and-access) Access to 4HSE is provided through a dedicated authentication page.  ### 1.1 Login Page Elements [Section titled “1.1 Login Page Elements”](#11-login-page-elements) The login screen includes the following fields and options: * **Email:** Field for the email address registered on the platform. * **Password:** Field for entering the account password. * **Remember me:** Option to keep the session active on the current device. * **Login:** Button to start the authentication process. * **Or login with… Google:** Option to sign in using a Google account. * **Forgot password?:** Link to initiate the password recovery process. * **New user? Register:** Link to create a new account. * **Language selector:** Tool to choose the interface language. ### 1.2 Password Reset [Section titled “1.2 Password Reset”](#12-password-reset) If the password is forgotten, the reset can be initiated: 1. On the login screen, select the **Forgot password?** link. 2. A form appears where the associated **Email** must be entered. 3. Select **Send**. 4. The system sends an email containing the password reset link. The link is valid for 30 minutes. Once opened, a guided procedure allows setting a new password using two fields (new password and confirmation). At the end, select **Submit** to complete the operation.  ## 2. Password Management [Section titled “2. Password Management”](#2-password-management) The password can be changed at any time through the **account management panel**. The [Account Management](/guides/first-steps/account-console) guide provides instructions for: * accessing the account management panel, * configuring access settings, * changing the password, * enabling multi-factor authentication (MFA). ## 3. Common Access Issues [Section titled “3. Common Access Issues”](#3-common-access-issues) This section describes the main types of errors related to login and password management, along with recommended solutions. ### 3.1 Password or Incorrect Email Issues [Section titled “3.1 Password or Incorrect Email Issues”](#31-password-or-incorrect-email-issues) | Issue | Common Cause | Recommended Solution | | :---------------------------------------------- | :----------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------- | | **Login failed** | Entering an email different from the registered one or a typing error. | Verify the accuracy of the email address. **The email is the exact identifier** used to register the user in 4HSE. | | **Password reset not received – wrong email** | Entering an email different from the registered one or a typing error. | Verify the accuracy of the email address. **The email is the exact identifier** used to register the user in 4HSE. | | **Password reset not received – email in spam** | The email ended up in the spam/junk folder. | Check the **spam** or junk folder. If the problem persists, contact the administrator. | | **Password reset link not working** | The password reset link is valid for a limited period of **30 minutes**. | Restart the “Forgot password” procedure and use the new link. | ### 3.2 Registration and Whitelabel Issues [Section titled “3.2 Registration and Whitelabel Issues”](#32-registration-and-whitelabel-issues) | Issue | Common Cause | Recommended Solution | | :------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- | | **Newly created user** | The user has not completed the first login. | Check the invitation email and click the link to set the final password. Until then, the user is not registered on the platform. | | **Login failed – wrong domain** | The user is trying to log in from a domain different from the one used for registration. **(Occurs only in projects with a custom domain / whitelabel)**. | Log in from the correct domain. If the registration occurred on the wrong domain, the user must be recreated. | Tip To ensure the security of your account, always protect your credentials and consider enabling multi-factor authentication (MFA). --- # Basic Menus and Navigation > A guide to navigating and using the main menus and toolbars in 4HSE. Navigation in 4HSE projects is based on a system of **interactive windows**. Each window is designed to be uniform and intuitive, offering various management options: * **Minimize** * **Maximize to full screen** * **Move** * **Close** * **Manual resizing** All these functions are easily accessible via the **buttons located in the top right** of the window. On the left side of each window, you’ll find the **main menu**. This menu lists all **available functions**, which will open in the right-hand area. For example, when you open a project, the left menu will display project-specific options, including: * Dashboard * Office Management * People Management * Organizational Chart Management * Supplier Management * File Management * Administration Panel * Technical Support, where you can open tickets for our development team (Below we see the **Project Menu** and the **Office Menu**)  The right area of the screen is primarily dedicated to displaying **lists of items**. You can select each item to view its details. If the  icon is present, you can open the item in a new window, making navigation more flexible. Two **toolbars** are essential for managing information within windows, simplifying your operations. ### Main Toolbar [Section titled “Main Toolbar”](#main-toolbar) Located at the top, the **main toolbar** offers essential functions for data management. Key functionalities include: * **Create/Add/Associate** a new item * **Delete** selected items * **Reload** the page * **Search** for information * **Show/Hide history** of changes * **Export** data * **Import** data ### Detail Toolbar [Section titled “Detail Toolbar”](#detail-toolbar) The second bar, the **detail toolbar**, is more specific, and its functionalities vary based on the area or context you are navigating. This toolbar can offer additional options such as: * Access to the **print tool** for generating documents and certificates. * **Wizards** and tools to record action outcomes. * **Certificate generation**. * Management of **existence periods** or import of **attachments**.  --- # Transferring a Worker Between Offices > Guide to moving a worker between different offices in 4HSE using the step-by-step wizard. It is common in a company for a worker to move from one workplace to another within the same project. Therefore, it becomes necessary to update the worker’s safety status in the new office as well. 4HSE provides a guided procedure (wizard) to facilitate this process. You can start the wizard from the worker detail toolbar by opening the **Wizards** menu and selecting **Move**.  ## How the Wizard Works [Section titled “How the Wizard Works”](#how-the-wizard-works) ### Step 1: Select Source and Destination Offices [Section titled “Step 1: Select Source and Destination Offices”](#step-1-select-source-and-destination-offices) 1. When the tool starts, you’ll see a screen for selecting the source and destination offices. 2. On the left side, you’ll find a list of offices where the person is currently assigned. Select one or more source offices by clicking on them. 3. On the right side, you’ll find a list of available destination offices. Select only one destination office, ensuring it is not among the selected source offices. 4. Click the “Next” button to proceed to Step 2, or “Cancel” to exit the wizard. ### Step 2: Enter Transfer Information [Section titled “Step 2: Enter Transfer Information”](#step-2-enter-transfer-information) 1. Enter the **Transfer Date**, which will be the start date at the destination office. 2. Select the option **Record end dates in source offices** to indicate when the person will stop working at the source offices. * If selected, the **Transfer Date minus one day** will be the end date in the source offices, and the person will no longer be assigned to them. * If not selected, the **Transfer Date** will be used only as the start date in the destination office, with no change to the source office assignments. 3. Click “Next” to proceed to Step 3 or “Back” to return to Step 1. ### Step 3: Confirm Links and Operations [Section titled “Step 3: Confirm Links and Operations”](#step-3-confirm-links-and-operations) 1. The next screen displays a table with the following columns: **Resource Code**, **Resource Name**, **Status**, and **Action Available**. 2. The **Action Available** column is interactive. If the value is **Link**, you can click it to change the action to **None** if you do not want to create the link. If the value is already **None**, it cannot be modified. 3. Carefully review the table to see what already exists in the destination office and which resources can be linked to the person. 4. Click “Confirm” to execute the linking operations and proceed to Step 4, or “Back” to return to Step 2. ### Step 4: Perform Operations [Section titled “Step 4: Perform Operations”](#step-4-perform-operations) 1. In the final screen, the system will execute the operations listed in Step 3. 2. A progress bar will be shown to provide visual feedback on the status of the linking operations. 3. Wait until the progress bar reaches 100% to ensure the operations are completed successfully. 4. Once complete, the “Finish” button will be enabled. 5. Click the “Finish” button to close the wizard and complete the person’s office transfer. By following this guide, you will be able to use the transfer tool effectively and accurately. Be sure to double-check the entered information and the planned operations before finalizing the transfer. ## Examples [Section titled “Examples”](#examples) ### Example 1 [Section titled “Example 1”](#example-1) A person is transferred to a destination office with no linked resources Let’s say: The person *Marco Rossi* is currently assigned to the offices *Milan* and *Turin*. The destination office is *Rome*. The transfer date is *2023-07-21*. We want to record end dates for the source offices. #### Step 1: Select source and destination offices [Section titled “Step 1: Select source and destination offices”](#step-1-select-source-and-destination-offices-1) Source offices: *Milan, Turin* Destination office: *Rome* #### Step 2: Enter transfer information [Section titled “Step 2: Enter transfer information”](#step-2-enter-transfer-information-1) Transfer date: *2023-07-21* **Record end dates in source offices**: yes #### Step 3: Resource table is populated as follows: [Section titled “Step 3: Resource table is populated as follows:”](#step-3-resource-table-is-populated-as-follows) | Resource Code | Resource Name | Status | Action Available | | ------------- | ------------------- | ----------- | ---------------- | | R001 | Safety Training | Present | Link | | R002 | Health Surveillance | Not present | None | | R003 | Area A | Not present | None | | R004 | Equipment XYZ | Not present | None | *Marco Rossi* will be unassigned from *Milan* and *Turin* as of *2023-07-21*. A link will be created for *Marco Rossi* to the *Safety Training* resource in the destination office *Rome*. ### Example 2 [Section titled “Example 2”](#example-2) A person is transferred to a destination office with existing resources and history Let’s say: The person *Anna Verdi* is currently assigned to the *Florence* office. The destination office is *Milan*. The transfer date is *2023-07-21*. We want to record end dates for the source office. #### Step 1: Select source and destination offices [Section titled “Step 1: Select source and destination offices”](#step-1-select-source-and-destination-offices-2) Source office: *Florence* Destination office: *Milan* #### Step 2: Enter transfer information [Section titled “Step 2: Enter transfer information”](#step-2-enter-transfer-information-2) Transfer date: *2023-07-21* **Record end dates in source offices**: yes #### Step 3: Resource table is populated as follows: [Section titled “Step 3: Resource table is populated as follows:”](#step-3-resource-table-is-populated-as-follows-1) | Resource Code | Resource Name | Status | Action Available | | ------------- | ------------------- | ----------- | ---------------- | | R001 | Safety Training | Present | Link | | R002 | Health Surveillance | Linked | None | | R003 | Area A | Not present | None | | R004 | Equipment XYZ | Not present | None | *Anna Verdi* will be unassigned from *Florence* as of *2023-07-21*. A link will be created for *Anna Verdi* to the *Safety Training* resource in the destination office *Milan*. **Note**: *Anna Verdi* already has a work history in *Milan*, as shown by the *Linked* status of the *Health Surveillance* resource. Only new resources will be linked during the transfer process. --- # Existence Periods > Managing the existence periods of elements in 4HSE and their inheritance. In 4HSE, many elements can have their respective *existence periods* defined. These periods are extremely useful as they indicate when (for how long and how often) an element was part of your safety project. ## When Periods of Existence Are Not Applicable [Section titled “When Periods of Existence Are Not Applicable”](#when-periods-of-existence-are-not-applicable) Not all elements require a period of existence to be specified. Some are intrinsically tied to a specific date or fixed interval. Examples include: * The edition of a course * A medical examination * A certificate ## Practical Example [Section titled “Practical Example”](#practical-example) A typical application of periods of existence is in managing **seasonal workers**. Imagine an employee, **Mario Rossi**, who worked during two distinct periods: * **First Period:** Worked from **2019-10-01 to 2019-12-01**. * **Second Period:** Was subsequently hired indefinitely starting from **2020-01-01**. The resulting periods of existence are: | | Start Date | End Date | | -------- | ---------- | ---------- | | Period 1 | 01/10/2019 | 01/12/2019 | | Period 2 | 01/01/2020 | +infinite | Let’s assume that during his employment, the worker: * was assigned to the **Warehouse Management** work phase * attended a **Forklift Operator Training** course * attended a **General Training (4 hours)** course * was subject to an individual prescription protocol requiring the **distribution of a high-visibility vest** These elements are considered child elements of the **person** element, which in turn acts as the parent. This creates a hierarchy: * Mario Rossi\ |\_ Warehouse Management\ |\_ Forklift Operator Training\ |\_ General Training (4 hours)\ |\_ High-Visibility Vest\\ This is a recurring concept in 4HSE and applies to many system elements. ## Inheritance of Periods of Existence [Section titled “Inheritance of Periods of Existence”](#inheritance-of-periods-of-existence) By default, elements in 4HSE have an **infinite lifespan**, ranging from minus infinity to plus infinity. However, it’s important to note that all elements with an unspecified period of existence **implicitly inherit those of their parent elements**, if the latter have been defined. With this in mind, let’s assume the periods for the child entities are as follows: | Element | Start Date | End Date | | -------------------------- | -------------------------- | -------------------------- | | Warehouse Management | 15/10/2019 | 30/11/2019 | | Forklift Operator Training | 05/10/2019 | 15/11/2019 | | General Training (4 hours) | inherited from Mario Rossi | inherited from Mario Rossi | | High-Visibility Vest | 10/10/2019 | 30/11/2019 | As shown in the table, all elements except **General Training (4 hours)** have a specific existence period and will be displayed on the chart. In contrast, **General Training (4 hours)** inherits the existence periods from the parent Mario Rossi and therefore will not be displayed on the chart. Any new child elements will inherit the periods from the person element. Similarly, although the person element may have parent elements, these are not displayed on the chart because they all have an **infinite lifespan**.  As you can see from the chart, all child element periods (in purple) fall within **Period 1**. When adding or editing periods, the system assists in maintaining consistency with the periods of parent/child elements, ensuring that: * for each period of the current element, there is at least one parent period that contains it * for each child period, there is at least one period of the current element that contains it Parent and child periods are **not directly editable** from this screen and must be modified via the period window of their respective element. For example, if you want to modify the existence period of the **Forklift Operator Training** for Mario Rossi, you must navigate to its detail form (*Project/Office/Actions/Training/Courses/Forklift Operator Training/People/Mario Rossi*) and click the icon. This will open the following dialog window:  --- # Partner panel --- # Creating Projects and Operational Functions > Guide to creating and managing projects in the 4HSE Multi Company Panel. The **Multi Company Panel** allows centralized management of all companies and associated projects, providing dedicated tools to administer clients, users, and subscription data. ## Accessing the Panel [Section titled “Accessing the Panel”](#accessing-the-panel) The Multi Company Panel is directly accessible from the **Start menu** of the 4HSE platform. Access is restricted to authorized users with appropriate permissions, according to the profiling rules defined within the panel.  ## Managing Clients and Projects [Section titled “Managing Clients and Projects”](#managing-clients-and-projects) Within the panel, it is possible to: * **Add new projects**, automatically linked to the Multi Company plan, * **Monitor project status**, including activation and the number of employees for each project. Note Project creation is reserved for users with the **Admin** role in the Multi Company Panel. ## Managing Users and Roles [Section titled “Managing Users and Roles”](#managing-users-and-roles) The panel allows you to: * **Add users** who can access all projects, * **Assign permissions** to define responsibilities and access limits. Tip For more information on managing permissions in the Multi Company Panel, see [Managing Multi Company Permissions](/guides/permissions/partner-permissions) ## Managing Billing and Subscription Data [Section titled “Managing Billing and Subscription Data”](#managing-billing-and-subscription-data) Through the Multi Company Panel, you can: * **Enter and update billing and payment information**. *After entering, it may take a few minutes for changes to take effect.* * **View invoice reminders**, while electronic invoices remain available in the tax drawer. * **Consult subscription data** and open **support tickets** directly with the 4HSE technical team.  ### Creating Multi Company Projects [Section titled “Creating Multi Company Projects”](#creating-multi-company-projects) **Creating new projects** in the Multi Company Panel is a function reserved for users with the *Admin* role. The first user with this role is enabled directly by the **4HSE technical support** at the time of Multi Company Panel activation. Users with the **Manager** role can operate on all existing projects, but **do not have the privilege to create new ones**. To enable additional users as Admins, there must already be at least one administrator in the panel. If the first Admin is not present or the Multi Company Panel is not yet active, you must contact **technical support** to request activation.  #### WARNING [Section titled “WARNING”](#warning) Projects created outside the Multi Company Panel — via the **desktop tool** or the **“Try Now”** link on [www.4hse.com](https://www.4hse.com) — **will not be linked to the Multi Company plan**.  These projects are **Corporate**, valid for a single VAT number corresponding to the invoice holder. Corporate projects open in **TRIAL status** and, if not activated properly, **will be suspended after 15 days and deleted after 90 days**, according to the Terms of Service. Furthermore, **access to these projects is not shared** with users authorized in the Multi Company Panel, making manual addition necessary. #### Access to Multi Company Project Templates [Section titled “Access to Multi Company Project Templates”](#access-to-multi-company-project-templates) Multi Company projects also include a **template project**, designed as a **reference model with pre-filled data**. The template allows users to create new elements within the project by copying existing information using the **Copy** tool (see [Copy Elements](/guides/copy/copy-element)). Users assigned to projects linked to the Multi Company Panel **can access the content of the templates**. Note The Multi Company Panel is **activated upon request** by the 4HSE technical team, usually during subscription activation for clients who meet the requirements. --- # Introduction to the Multi Company Panel > Overview of the features and management of the Multi Company Panel in 4HSE. The **Multi Company Panel** is a 4HSE feature designed for **consultants** and **organizations** managing occupational safety for **multiple companies or legal entities**. It is a centralized tool that allows you to **administer and monitor** all 4HSE projects associated with your clients from a single interface. Through the Multi Company Panel, it is possible to get an **overview** of the managed companies, checking for each the **activation status**, the **number of employees**, and the main information. The goal is to simplify the work of those coordinating multiple companies, ensuring fast and structured access to all projects. The Multi Company Panel is **activated upon request** by the 4HSE technical team, usually at the start of the subscription, for clients who meet the requirements. Once enabled, it becomes the reference point for managing multiple projects simultaneously, allowing clear and consistent governance across all projects. Tip For more details on how the Multi Company panel works, see [Creating Projects and Operational Functions](/guides/partner-panel/creation-of-the-partner-projects) and [Managing Multi-Company Permissions](/guides/permissions/partner-permissions) --- # Permissions --- # Office Permissions > Guide to managing permissions at the Office level in 4HSE, including generic roles and area-specific permissions. In 4HSE, the **Office** is a fundamental operational entity. Managing permissions at this level gives you the flexibility to delegate specific responsibilities to teams or individual employees operating in different locations. An Office permission is the “pass” that allows a user to act within that defined corporate space. ## Permission Groups for the Office [Section titled “Permission Groups for the Office”](#permission-groups-for-the-office) To better organize roles, 4HSE provides several permission groups, divided into two categories. ### Generic Roles [Section titled “Generic Roles”](#generic-roles) Define access to the entire Office. Available groups are: * **Manager**: for those responsible for overseeing Office operations. * **User**: for those who need to view Office data without modifying it. * **Guest**: for limited access to certain sections. * **NA (No Access)**: for those who should have no access to Office data. ### Area Roles [Section titled “Area Roles”](#area-roles) These specific roles apply only to certain functional areas, such as training or maintenance. They allow you to create true specialists with targeted permissions. * **Training Manager**, **Training User**, **Training NA** * **Health Surveillance Manager**, **Health Surveillance User**, **Health Surveillance NA** * **Personal Protection Manager**, **Personal Protection User**, **Personal Protection NA** * **Procedure Manager**, **Procedure User**, **Procedure NA** * **Maintenance Manager**, **Maintenance User**, **Maintenance NA** ## Overview of Permissions [Section titled “Overview of Permissions”](#overview-of-permissions) ### Generic Office Permissions [Section titled “Generic Office Permissions”](#generic-office-permissions) | Group | Office Permissions | | :---------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Manager** | Read and write permissions Can modify data, add/remove users, and view reports **NOTE:** Adding/removing users is only possible if also a **Project Admin**. | | **User** | Read-only permissions on Office data | | **Guest** | Limited access to certain sections: Human Resources, Material Resources, Work Phases, Safety Organization Chart, and Actions | | **NA** | No access to Office data | ### Permissions for the “Training” Area [Section titled “Permissions for the “Training” Area”](#permissions-for-the-training-area) | Group | Training Area Permissions | | :------------------- | :---------------------------------------------------------------------------------------------------------------------- | | **Training Manager** | Full control over training actions: can create, modify, and delete Has access to related data (e.g., associated people) | | **Training User** | Can view training data and related entities | | **Training NA** | No access to the training area | ### Permissions for the “Health Surveillance” Area [Section titled “Permissions for the “Health Surveillance” Area”](#permissions-for-the-health-surveillance-area) | Group | Health Surveillance Area Permissions | | :------------------------------ | :------------------------------------------------------------------------------------------------- | | **Health Surveillance Manager** | Full control over health surveillance actions Has access to related data (e.g., associated people) | | **Health Surveillance User** | Can view health surveillance data and related entities | | **Health Surveillance NA** | No access to the health surveillance area | ### Permissions for the “Personal Protection” Area [Section titled “Permissions for the “Personal Protection” Area”](#permissions-for-the-personal-protection-area) | Group | Personal Protection Area Permissions | | :------------------------------ | :------------------------------------------------------------------------------------------------------ | | **Personal Protection Manager** | Full control over personal protection actions. Has access to related data (e.g., associated people/PPE) | | **Personal Protection User** | Can view personal protection data and related entities | | **Personal Protection NA** | No access to the personal protection area | ### Permissions for the “Procedures” Area [Section titled “Permissions for the “Procedures” Area”](#permissions-for-the-procedures-area) | Group | Procedure Area Permissions | | :-------------------- | :-------------------------------------------------------------------------------------------------------- | | **Procedure Manager** | Full control over procedure actions. Has access to related data (e.g., people/offices/material resources) | | **Procedure User** | Can view procedure data and related entities | | **Procedure NA** | No access to the procedure area | ### Permissions for the “Maintenance” Area [Section titled “Permissions for the “Maintenance” Area”](#permissions-for-the-maintenance-area) | Group | Maintenance Area Permissions | | :---------------------- | :----------------------------------------------------------------------------------------------------------------------------------- | | **Maintenance Manager** | Full control over maintenance actions: can create, modify, and delete. Has access to related data (e.g., offices/material resources) | | **Maintenance User** | Can view maintenance data and related entities | | **Maintenance NA** | No access to the maintenance area | ## Inheritance and Flexibility [Section titled “Inheritance and Flexibility”](#inheritance-and-flexibility) As with Project permissions, Office permissions propagate to entities linked to it. An **Office Manager** inherits **Manager** permissions on People and Actions linked to that Office. An **Office User** inherits **User** permissions on People and Actions linked to it. Office permissions are an intelligent extension of Project permissions. A user with a **User** role at the Project level, which grants visibility on everything, can have a higher role (e.g., **Manager**) on a specific functional area of the Office, such as training. This allows them to view all corporate data but have write permissions only in the training area, a perfect model for sector managers. ### Permission Propagation [Section titled “Permission Propagation”](#permission-propagation) | Office Role | Action Role | Person Role | | :---------- | :---------- | :---------- | | **Manager** | Manager | Manager | | **User** | User | User | | **Guest** | User | User | | **NA** | NA | NA | ### Permission Propagation from Functional Area [Section titled “Permission Propagation from Functional Area”](#permission-propagation-from-functional-area) | Action Role | Person Role | | :---------- | :---------- | | **Manager** | Manager | | **User** | User | | **NA** | NA | ## How to Set Office Permissions [Section titled “How to Set Office Permissions”](#how-to-set-office-permissions) Note Remember that you can only set permissions if you have the **Admin** role at the project level. To configure permissions for an office in 4HSE, you can act on two levels. ### 1. Manage Permission Groups [Section titled “1. Manage Permission Groups”](#1-manage-permission-groups) 1. Open the office of interest, navigate to **Administration** in the menu, and select **Permissions**. 2. In the **Groups** section, you will see the list of generic roles (**Manager**, **User**, **Guest**, **NA**) that apply to the entire office. 3. Select the role you want to manage. 4. The **Details** section shows users already assigned to that group. 5. To add or remove users, click the “new” button and enter their email.  ### 2. Configure Area Permissions [Section titled “2. Configure Area Permissions”](#2-configure-area-permissions) For more granular management, you can combine Project and Office permissions to limit access and write permissions to specific functional areas. Here’s how to assign permissions to a user for the Maintenance Area while limiting access to other entities: 1. Open the Office of interest, navigate to **Administration** in the menu, and select **Permissions**, then **Groups**. 2. Select the **Maintenance Manager** permission group. 3. The **Details** section shows users already assigned to that group. 4. To add a new user, click the “new” button and enter their email. --- # Multi Company Permissions Management > Guide to managing users and projects through the Multi Company Panel, with specific permissions for each role. Multi Company management is a key tool for consultants and anyone who needs to handle multiple projects simultaneously. It provides a comprehensive overview and simplifies the management of users and projects from a single interface. Note Activation of Multi Company management is handled exclusively by our technical support and requires a specific subscription plan. ## Permission Groups for Multi Company Projects [Section titled “Permission Groups for Multi Company Projects”](#permission-groups-for-multi-company-projects) The Multi Company management system offers dedicated permission groups that allow controlling access to all projects directly from the main project. The available groups are: * **Admin** * **Manager** * **User** * **Guest** Caution Users enabled in a Multi Company project share access to all linked projects. ## Permissions Overview by Role [Section titled “Permissions Overview by Role”](#permissions-overview-by-role) The table below summarizes the capabilities of each permission group. | Group | Permissions on Multi Company Project | Permissions on Linked Projects and Offices | | :---------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------- | | **Admin** | Read and write access Full user management within the panel Creation and management of projects and offices Access to full reporting. | Full management of linked projects and offices. | | **Manager** | Read and write access User and project management (cannot manage Admin users) Cannot view Permissions, User Logs, Contract, and Configuration sections | Can operate in all linked projects. | | **User** | View data and reports. | View linked projects and offices. | | **Guest** | Limited data and report viewing. | Limited view of linked projects and offices. | ## How to Set Permissions [Section titled “How to Set Permissions”](#how-to-set-permissions) To modify permissions for a specific project within the Multi Company tool: 1. From the 4HSE **Start** menu, click **Multi Company** and select the desired project.  2. In the project menu, go to **Administration** and select **Permissions**; 3. The section includes two submenus: **Groups** and **Users**; 4. Selecting **Groups** displays the list of predefined project roles (*Admin*, *Manager*, *User*, *na*); 5. From here, you can see the users associated with each group and add or remove them by entering their email address;  6. Selecting **Users** provides an overview of all users with direct access to the project. --- # 4HSE Permission System: A Hybrid and Granular Approach > Guide to 4HSE's hybrid permission system. Security is a top priority for 4HSE, and a robust access control system has been developed accordingly. The goal is to enable precise permission management, ensuring that each user can access only the information and functionalities relevant to them. The 4HSE permission system supports complex scenarios. For example: * A **Project User** can automatically view all offices, suppliers, and people linked to that project without manually assigning permissions to each entity. * If the same user is later added to the office permission group **Health Surveillance Manager**, they automatically gain write permissions in the health surveillance functional area of that office. This approach simplifies access management while maintaining consistency and flexibility. This document explains the fundamental concepts of the permission system, how to manage permissions, and the entities on which permissions can be applied. ## Managing Permissions in 4HSE [Section titled “Managing Permissions in 4HSE”](#managing-permissions-in-4hse) Permissions are managed directly within the platform through the **Administration** section, under the **Permissions** menu. This section is divided into two submenus: * **Groups**: In 4HSE, a group represents a predefined role that includes a set of specific permissions. **Assigning a user to a group automatically grants them the permissions associated with that role**. In this section, you can see the list of predefined groups for the selected entity (e.g., project groups). Selecting a group allows you to view the users it includes and add or remove users by their email address. This is the most direct tool for managing permissions.  * **Users**: lists all users who have access to the entity through a direct assignment.  Note The **Administration** section is accessible only to users with the **Project Admin** role. Entities for which permissions can be managed are: Project, Office, Person, Supplier, and Multi Company Project. ## Direct and Indirect Access [Section titled “Direct and Indirect Access”](#direct-and-indirect-access) As mentioned earlier, in 4HSE a user can obtain permissions in two ways: ### 1. Direct Access [Section titled “1. Direct Access”](#1-direct-access) This is the most straightforward method: a user is explicitly assigned to one of the groups of an entity (e.g., a project, office, or person). This manual assignment grants specific permissions on the selected entity and all entities directly linked to it. ### 2. Indirect Access (Inheritance) [Section titled “2. Indirect Access (Inheritance)”](#2-indirect-access-inheritance) Indirect access uses permission inheritance. Rights propagate consistently from higher-level entities to lower-level ones. For example, a user assigned as a Project Manager automatically obtains permissions to manage the offices, people, and suppliers linked to that project. ## Entities with Configurable Permissions [Section titled “Entities with Configurable Permissions”](#entities-with-configurable-permissions) The 4HSE permission system applies to several key entities: * **Project** – Represents the main management level; permissions set here propagate to linked entities. → See [Project Permissions](/guides/permissions/project-permissions). * **Office** – Part of the project, representing a physical workplace. Allows assigning specific permissions to the office itself and to individual functional areas. → See [Office Permissions](/guides/permissions/office-permissions). * **Person** – Represents an individual registered in 4HSE with their personal information. Permissions on this entity regulate access to personal data and linked items, with the option to use the *Related User* feature for profile access. → See [Person Permissions](/guides/permissions/person-permissions) and [Related User](/guides/permissions/related-user). * **Supplier** – Permissions control access for external suppliers. → See [Supplier Permissions](/guides/permissions/supplier-permissions). * **Multi Company Project (available with the PRO plan)** – Manages access for users working across multiple projects. → See [Multi Company Permissions](/guides/permissions/partner-permissions). --- # Person Permissions > Guide to managing permissions for the Person entity in 4HSE, controlling access to collaborators' data and deadlines. In 4HSE, the **Person** entity represents a real individual registered in the system with their personal information. ## Permission Groups for Person [Section titled “Permission Groups for Person”](#permission-groups-for-person) Permissions for the “Person” entity are managed by assigning users to predefined groups. Available roles include: * **Manager** * **User** * **Guest** 4HSE also features the **Related User**: a user directly linked to a specific person. This functionality complements standard permission assignment through groups. Tip Learn more in the article: [Related User](/guides/permissions/related-user). ## Permission Overview by Role [Section titled “Permission Overview by Role”](#permission-overview-by-role) The following table summarizes the capabilities of each permission group. | Group | Person Permissions | | :---------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Manager** | Read and write permissions Can link entities to the person (work phases, equipment, etc.) Can manage the person’s permissions and groups (only if also a **Project Admin**) | | **User** | Read-only permissions Can view entities associated with the person | | **Guest** | Read-only permissions on a limited set of data Can view only certain sections (**cannot** access **Administration**, **Attachments**, and **Events** sections). | ## How to Set Person Permissions [Section titled “How to Set Person Permissions”](#how-to-set-person-permissions) Note Only users who are part of the **Project Admin** group can set permissions. To configure permissions for a Person: 1. Open the Person’s detail page; 2. Select **Administration** from the menu, then the **Permissions** submenu; 3. The section has two tabs: **Groups** and **Users**; 4. Selecting **Groups** shows the predefined groups for the person and the users in each group; 5. In the **Details -> Users** section, you can view the users in each group; 6. To add a user, click “New” and enter their email address.  To see the users who have been granted direct access to the Person, select the **Users** tab. --- # Project Permissions > Guide to managing permissions at the project level in 4HSE and their impact on related entities. ## The Core of Management: Project Permissions [Section titled “The Core of Management: Project Permissions”](#the-core-of-management-project-permissions) In 4HSE, the **project** is the heart of your company’s safety management. This is where overall user access is defined, ensuring that everyone has the right responsibilities and visibility. Managing permissions at this level is essential for maintaining order and security across the system. *** ## Permission Groups for the Project [Section titled “Permission Groups for the Project”](#permission-groups-for-the-project) To simplify management, 4HSE provides four predefined permission groups for each project: * **Admin**: Full control, for those who need to manage every aspect of the project. * **Manager**: For supervisors who need to actively operate but without the ability to manage advanced permissions and configurations. * **User**: For users who need to view data without modifying it. * **NA (No Access)**: For users who require extremely limited or no access to the project. Assigning a user to one of these groups impacts not only the project itself but also their permissions on related entities like offices and suppliers, thanks to an inheritance system that saves time and effort. ## Permission Overview by Role [Section titled “Permission Overview by Role”](#permission-overview-by-role) The following table provides a clear overview of what each group can do at the project level. | Group | Project Permissions | | :---------- | :--------------------------------------------------------------------------------------------------------------------------------- | | **Admin** | Full project management Read and write permissions Role assignment Access to configuration and contract menus | | **Manager** | Partial project management Read and write permissions Cannot view the Permissions, User Logs, Contract, and Configuration sections | | **User** | Read-only permissions | | **NA** | Very limited access, without the ability to manage or view data | ## Inheritance: A Cascade of Permissions [Section titled “Inheritance: A Cascade of Permissions”](#inheritance-a-cascade-of-permissions) Permissions set at the project level are not isolated—they cascade to related entities. Once a user’s role on a project is defined, there is no need to configure each individual office or supplier. The following table summarizes how project roles automatically propagate to other entities. | Project Role | Office Role | Person Role | Supplier Role | | :----------- | :---------- | :---------- | :------------ | | **Admin** | Manager | Manager | Admin | | **Manager** | Manager | Manager | Admin | | **User** | User | User | User | | **NA** | NA | NA | NA | Note For a detailed explanation of permissions at the Office, Supplier, and Person levels, see the dedicated sections: * [Office Permissions](/guides/permissions/office-permissions) * [Supplier Permissions](/guides/permissions/supplier-permissions) * [Person Permissions](/guides/permissions/person-permissions) ## How to Set Project Permissions [Section titled “How to Set Project Permissions”](#how-to-set-project-permissions) Assigning permissions at the project level is done via the **Permissions** menu. 1. Open the **Project** detail page; 2. Select **Administration** from the menu, then the **Permissions** submenu; 3. The section has two tabs: **Groups** and **Users**; 4. Selecting **Groups** shows the predefined roles for the project (**Admin**, **Manager**, **User**, **NA**); 5. In the **Details → Users** section, you can see the users in each group; 6. To add a user, select **New** and enter their email address;  7. Selecting **Users** shows an overview of all users who have direct access to the project.  --- # Related User > Guide to the concept of Related User in 4HSE and the management of its permissions. ## What is a Related User [Section titled “What is a Related User”](#what-is-a-related-user) The **Related User** is a key concept in 4HSE that allows you to link a **User** to a specific **Person**. This association connects the data of a real individual registered in the system (the Person) with the account that authenticates and interacts with the software (the User). To establish the link, you enter the user’s email address in the “Related User” field of the Person’s form. The email acts as the key for this association. Example: If the person named Sara Martini is registered in the system, you can associate the email of the user who represents her. The association allows the user to access and view their safety-related information with specific permissions. Note The **User** is the entity that authenticates in the software and to which permissions are assigned, while the **Person** is the representation of the real individual registered in the system with their personal and role-related information. ## Permissions for the Related User [Section titled “Permissions for the Related User”](#permissions-for-the-related-user) Assigning permissions is essential to define what the related user can do. There are different levels of permissions that can be configured: * **None**: The related user has no access to the person they are linked to. * **Manager/Read-Write**: The user has both read and write permissions and can edit the person’s information. * **User/Read**: The user can view the person’s information but cannot make changes. This is a read-only permission. * **Project Default**: The user inherits the permissions defined at the project level. (In the next section, we explain how to set the default permission). ## How to assign the Related User and its permissions [Section titled “How to assign the Related User and its permissions”](#how-to-assign-the-related-user-and-its-permissions) The association and permission management can be carried out in different ways. ### 1. From the Person’s page [Section titled “1. From the Person’s page”](#1-from-the-persons-page) You can associate a user with a person and configure their permissions directly from the person’s record. To do this: 1. Open the person’s record. 2. Go to the **Administration** menu and select **Related User**. 3. Enter the user’s email address. 4. Choose the desired permission level from the available options. 5. Save to confirm the association and permissions.  ### 2. From the Project settings [Section titled “2. From the Project settings”](#2-from-the-project-settings) The project administrator can set a default permission for all new related users. This feature is useful for bulk imports or for those using the APIs. 1. Go to **Project Menu** -> **Administration** -> **Configuration** -> **User-Person**. 2. Use the selector to define the default permission.  Caution This setting only applies to new persons and does not change the permissions of existing users. ### 3. Using the permission management wizard [Section titled “3. Using the permission management wizard”](#3-using-the-permission-management-wizard) To quickly change the permissions of a group of already associated persons, you can use the **“Related Users Permissions” wizard**. 1. Access the wizard from the people list;  2. Select the persons whose permissions you want to modify. Only those who already have a related user will be displayed;  3. Choose the permission to assign from the available options;  4. Confirm to apply the permission to all selected persons. ## Practical example: a worker with minimal permissions [Section titled “Practical example: a worker with minimal permissions”](#practical-example-a-worker-with-minimal-permissions) An administrator needs to give a worker, Mario Rossi, access to the platform so he can view his safety situation without being able to see other data. Here’s how the administrator configures the permissions: 1. **Project-level permission**: The administrator assigns Mario Rossi the “na” (no access) permission at the project level. This ensures that the user cannot view or manage the company’s general data. 2. **Person-level permission**: The administrator associates the user “” with the person “Mario Rossi” and sets the permission to “**User/Read**”. In this way, Mario Rossi will not have access to the project in general, but he will be able to view in read-only mode the information related to his person and the entities associated with him (courses, PPE, deadlines, etc.), without being able to modify them. --- # Supplier Permissions > Guide to managing permissions for the Supplier entity in 4HSE. 4HSE provides four predefined permission groups for each supplier: * **Admin**: Has full read and write permissions on the supplier. * **Manager**: Can view and edit supplier data but cannot manage administrative settings. * **User**: Can only view supplier data. * **NA (No Access)**: For users who should have no access to supplier data. ## Permission Overview by Role [Section titled “Permission Overview by Role”](#permission-overview-by-role) The table below summarizes the capabilities of each permission group. | Group | Supplier Permissions | | :---------- | :------------------------------------------------------------------------------------------------------ | | **Admin** | Full management of supplier data Add/remove users and manage groups (only if also a **Project Admin**). | | **Manager** | Read and write access to supplier data Cannot access administrative settings. | | **User** | View supplier data and associated entities. | | **NA** | No access to supplier data. | ## How to Set Supplier Permissions [Section titled “How to Set Supplier Permissions”](#how-to-set-supplier-permissions) Note Permissions can only be modified by users with the **Project Admin** role. To set the permissions for a Supplier, follow these steps: 1. In the supplier window menu, go to **Administration** and select **Permissions**. 2. The **Permissions** section has two submenus: **Groups** and **Users**. 3. Open **Groups** to view the supplier’s predefined groups (**Admin**, **Manager**, **User**, **NA**). 4. Select the desired group and, in the **Details** section, click “new” to add the user’s email address.  5. To get a complete view of all users with access to the supplier, select the **Users** submenu. This shows only the users who have been assigned direct permissions on that Supplier. --- # Users in 4HSE > What Users are and how to manage their permissions in the 4HSE platform. ## What Users are in 4HSE [Section titled “What Users are in 4HSE”](#what-users-are-in-4hse) A **4HSE User** is an individual account that allows a person to access and use the platform. Each user is identified by a unique email address, which serves both as the login username and the main contact. Through their account, a user can: * view information * enter data * edit records * use platform functionalities Their actions are determined by the specific permissions assigned to them. Note Each user can be associated with projects, offices, and a person within the system. For more details about the association between user and person, see the document **“Related User”**. *** ## Relationship Between Users and Permissions [Section titled “Relationship Between Users and Permissions”](#relationship-between-users-and-permissions) Every user in 4HSE is linked to a set of permissions that define their access level and the actions they can perform. This permission system is based on a complex model that includes role-based, attribute-based, and relationship-based management. Tip For a complete understanding of how permissions work in 4HSE, we recommend consulting the document **“The 4HSE Permission System”**. *** ## Creating and Managing Users [Section titled “Creating and Managing Users”](#creating-and-managing-users) The process of creating and managing users is a key function for administrators. ### How to Create a New User [Section titled “How to Create a New User”](#how-to-create-a-new-user) To register a new user and assign permissions, follow these steps within one of the following entities: **Project**, **Office**, **Person**, **Supplier**, **Multi Company Panel**. The permissions will have different meanings depending on where they are managed. 1. Go to the **Administration** menu and select **Permissions**. 2. Choose the **Groups** submenu. Here you will find the list of groups available for the entity you are working on (e.g. at project or office level). 3. Select the group where you want to add the user (e.g. `admin`, `manager`, `user`). 4. In the **Details** section, use the “new” function to enter the new user’s email address. Note If the user is not yet registered in 4HSE, once added, the system will send an invitation email to the specified address. *** ## User Status [Section titled “User Status”](#user-status) The system tracks each user’s status with a colored badge. There are three main statuses: * **Unknown**: Initial state. Indicates that the email has not yet been registered in the system. * **Pending**: Applies to new users invited to collaborate on a project. The user remains in this state until their first login. * **Active**: The user enters this state after their first login. At this point, they can fully use the system. *** ## Permissions: Direct and Indirect Access [Section titled “Permissions: Direct and Indirect Access”](#permissions-direct-and-indirect-access) A user can obtain permissions in two ways: * **Direct Access**: A user gains direct access when explicitly assigned to a permission group of a specific entity. If a user is added to the “manager” group of a **Project**, they will have direct access to that Project. * **Indirect Access**: This type of access is more subtle. It works through the relationships between different parts of the system. A user does not receive permissions for a resource explicitly but inherits them because they are related to another resource already connected to the first. Tip Think of it as a hierarchy or a network of relationships: a user is assigned to a “child” entity (e.g. an **Office**). That “child” entity is linked to a “parent” entity (e.g. a **Project**). As a result, the user will also have access to the “parent” entity, but indirectly. If a user is added to a permission group of an **Office**, their email will also appear in the list of users of the **Project** that office belongs to. In this case, the user has **direct access** to the office and **indirect access** to the project. Note This mechanism is a key concept to understand how permissions propagate throughout the 4HSE system. For a detailed explanation, refer to the document **“The 4HSE Permission System”**. --- # Permit to Work --- # Permit to Work > How to manage a digital Permit to Work in 4HSE: from the procedure with mandatory forms to the time-bound certificate, all the way to on-site verification via QR code. A **Permit to Work (PTW)** is a formal, temporary and tracked authorization that allows a person or a team to carry out a **specific activity**, in a given **location** and for a precise **time window**. It is a central tool in operational safety management, in particular for: * high-risk work (hot work, confined spaces, electrical work, work at height); * complex industrial environments; * sites and yards with multiple contractors. In these scenarios safety is not just *“being compliant”*, but **being authorized right now**: the permit to work answers exactly this need. ## PTW in 4HSE [Section titled “PTW in 4HSE”](#ptw-in-4hse) In 4HSE the permit to work is **not a separate object**: it is a **certificate** issued at the end of a **procedure**, enriched with the characteristics typical of an operational authorization. In this way 4HSE builds on the procedures, forms and certificates you already use, without introducing a separate flow. A certificate that acts as a permit to work carries: * the **type of activity** authorized; * the **location / site / area**; * the **worker or team** authorized; * the **start and end date and time** of validity; * a **status** (draft, valid, expired, revoked, rejected); * the **completed forms** (checklists, authorizations, assessments) that become an integral part of the certificate. The permit is therefore a **cross-cutting procedure** that runs through features you probably already know: the [prevention action](/guides/prevention-actions/procedure-management/) that defines what to authorize, the [linked forms](/guides/action-forms/action-forms/) to be completed, the **certificate** that attests the authorization, the [scheduler](/guides/scheduler-and-planner/scheduler/) from which it is issued and monitored, and the **public verification page** that anyone can open by scanning a QR code. ### The permit life cycle [Section titled “The permit life cycle”](#the-permit-life-cycle) Every certificate-permit has a **status** that describes where it is in its life cycle. The status is visible in the certificate detail, in the scheduler, and on the public verification page. | Status | Meaning | | ------------ | --------------------------------------------------------------------------------------------------------------- | | **Draft** | The permit is being prepared: it is not yet authorized and does not grant the right to operate. | | **Valid** | The permit is authorized and effective within its validity dates. | | **Expired** | The permit has passed its end date/time and must be renewed. *Expired is derived automatically from the dates.* | | **Revoked** | The permit was withdrawn before its natural expiry (for example because conditions on site changed). | | **Rejected** | The permit was not approved. | Note When you create a new certificate, 4HSE sets its status to **Valid** by default, so ordinary certificates keep working as before. In the [scheduler](/guides/scheduler-and-planner/scheduler/) the **revoked** and **rejected** statuses appear with a red badge, and a valid permit becomes **expiring** as it approaches its end of validity. ### Time-bound validity: date, or date and time [Section titled “Time-bound validity: date, or date and time”](#time-bound-validity-date-or-date-and-time) A permit is effective between the **Date release** and the **Date expire**. When you issue the certificate, the **Time precision** checkbox determines the precision of these dates: * **Time precision off** (date only) — the permit is valid for the whole day and expires at the **end of the expiry day**. Suitable for authorizations measured in days, months or years. * **Time precision on** (date and time) — an **Hour** field appears next to each date and the permit expires at the **exact moment** chosen. This is the right choice for short-lived permits: hot work, an access lasting a few hours, a single shift. Tip For an operational permit to work (hot work, confined spaces, single shift) turn on **Time precision**: being valid “until the end of the day” would be too broad. Expiry is then applied automatically by 4HSE, with no manual action. *** ## Full example: hot work permit [Section titled “Full example: hot work permit”](#full-example-hot-work-permit) Let’s walk through the whole flow with a concrete case. A **worker** must carry out a **welding** job (hot work) in an area of the plant. The activity must be authorized only after the due checks, must last **a few hours** and be **verifiable on site** by a supervisor or an inspector. The same flow applies to the other high-risk permits (confined spaces, electrical work, work at height) and, in its simplest form, to authorizing a person’s **site access**. ### 1. Create the procedure [Section titled “1. Create the procedure”](#1-create-the-procedure) The permit is issued through an action of type **Procedure**. 1. Open the project and go to the relevant **office**. 2. Go to **Actions → Procedures** and create a new procedure, for example **“Permit to Work – Hot work”**. 3. Set the **validity** and the other parameters of the procedure.  ### 2. Add the PTW linked forms [Section titled “2. Add the PTW linked forms”](#2-add-the-ptw-linked-forms) In the **Related Forms** tab of the procedure, add the forms that must be completed to authorize the permit. 4HSE provides predefined, regulation-compliant PTW forms, including: * **General work permit** * **Hot work permit** * **Confined Space Entry Permit** * **Electrical work permit** * **Work at height permit** For our case we add the **Hot work permit** form, which gathers all the necessary information: performing company and contract coordination, location, fire-risk classification of the area, fire prevention measures, and start and end time of the work. We mark this form as **Required**: this way the permit cannot be issued until the form has been completed.  Note Forms created without the **Required** flag remain optional. See [Forms Linked to Actions](/guides/action-forms/action-forms/) for details on configuring and completing forms. ### 3. Associate the worker [Section titled “3. Associate the worker”](#3-associate-the-worker) Associate the **person** to be authorized with the procedure: in our case the welder who will carry out the job. This way the permit is issued to a specific named person, exactly like a nominal authorization.  ### 4. Issue the certificate from the scheduler with the required forms [Section titled “4. Issue the certificate from the scheduler with the required forms”](#4-issue-the-certificate-from-the-scheduler-with-the-required-forms) From the [scheduler](/guides/scheduler-and-planner/scheduler/), locate the deadline related to the person associated with the procedure and start the **certificate creation**. Since the procedure includes a **required** form, 4HSE opens the **“Forms linked to certificate”** window: * the associated forms are listed, with the **Required** column indicating which ones are mandatory (in our case, “Yes” for the Hot work permit); * each form has a **Fill** link: the operator opens the checklist, completes it, applies signatures where required, and saves; * the **Create certificate** button stays **disabled** until the required form has been completed.  Clicking **Fill** opens the form — in our case the **Hot work permit** — with all its fields: performing company and contract coordination, location, fire-risk classification of the area, fire prevention measures, work times, authorizations and signatures. Once completed, the form is saved and you return to the linked-forms window.  Once the required forms are completed, the **Create certificate** button becomes enabled and you can proceed with the issuance. In the **New certificate** window, turn on the **Time precision** checkbox and set the **Date release** and **Date expire** with their respective **Hour**: for example release at 13:00 and expiry at 15:00, for a **2-hour** duration. The permit will then be valid only for the hot-work window and will expire automatically at the end.  Caution The required-forms check is enforced **at the moment the certificate is created**, together with its forms. Complete the required forms during issuance to guarantee the permit is fully documented. The certificate is now **valid**: the completed form is attached to the certificate and becomes an integral part of it. ### 5. Generate the verification QR code [Section titled “5. Generate the verification QR code”](#5-generate-the-verification-qr-code) From the **certificate detail**, click the **Verification QR** button in the toolbar. 4HSE generates a **secure, temporary verification link** and shows the corresponding **QR code** together with its expiry. The QR code **contains no data** and does not expose internal identifiers: it only points to a temporary public page. You can display it on screen, print it, or embed it in the permit document.  ### 6. On-site verification and public page [Section titled “6. On-site verification and public page”](#6-on-site-verification-and-public-page) A third party — inspector, supervisor, client, contractor’s supervisor — **scans the QR** with their phone. The browser opens the **public verification page**, read-only and **without needing a 4HSE account**, which recalculates and shows the **up-to-date status** of the permit.  The page shows a concise view of the permit: * the **header** with the permit name and the **activity type** (in our case, Procedure), next to the QR; * the **status** highlighted with a colored badge: **Valid** (green), **Expired** (red), **Revoked** / **Rejected**, or **Draft**; * the **Permit details**: the **Worker or team** and the **Valid from** and **Valid until** validity; * any **Attachments** (for example the completed hot-work form), which can be opened from the page; * the **Verified on** line, i.e. the date and time the page was consulted. Because the status is **recalculated in real time**, if the permit has expired (past the 2 hours) or has been revoked, the page shows it immediately on the next scan. This is the difference from a paper permit: the QR always answers the question *“is this permit valid right now?”*. Note The verification page is shown automatically in the **browser language** of whoever consults it, with **English** as the fallback language (available languages: Italian, English, German, Spanish, French). No sensitive data is shown on the page. *** ## Security and privacy [Section titled “Security and privacy”](#security-and-privacy) The verification model is designed to be secure and privacy-respecting: * the verification link is **signed** and has a **limited lifetime**: it is not a guessable address and stops working when it expires; * the QR **does not expose** internal identifiers or sensitive data; * when you need to share the permit again after the link has expired, you **generate a new QR** from the certificate detail. This approach is consistent with the GDPR principles of data minimization, purpose limitation and security. --- # Prevention actions --- # Attaching Files to Training Actions > How to attach files and documents to training actions and employees in 4HSE. You can always attach files to safety-related actions: storage space is unlimited (both per site and per project) and there are no restrictions on file types or extensions. Specifically, regarding training, several types of files can be attached functionally. If you need to attach course-related documents, such as **a test to be administered** or **a course presentation file**, go to the course’s “Attachments” tab.  If instead you need to associate a **certification** obtained by a specific employee, we recommend attaching the document directly to the employee’s profile under the relevant site, as shown here:  --- # Health Surveillance > Management of prescriptions, medical examinations, and health surveillance certificates in 4HSE. The Health Surveillance section is located within the **Prevention Actions** area of each project **office**. From the **Actions** module, select the **Health Surveillance** menu, structured into two levels: * **Prescriptions**: define the health surveillance requirements for company personnel * **Medical Examinations**: set the **scheduling** for the execution of the prescriptions Within the **Health Surveillance** section, you can also: * **Register an existing certificate** (e.g., for past medical exams) * **Schedule a medical exam** * **Register the outcome** of a scheduled exam * **Generate a certificate** or upload an external one ## Add a New Prescription [Section titled “Add a New Prescription”](#add-a-new-prescription) You can create two types of prescriptions: * **New**: create a prescription from scratch * **Copy from**: duplicate an existing prescription Click **New**, fill in the required fields, and then click **Save** to confirm. Alternatively, you can use the **bulk import** function via the **Import** button in the toolbar.  A **new row** will now appear in the table with all indicators set to **zero**. (If no change is visible, click **Refresh** in the toolbar.) Tip **By selecting a prescription row**, a tabbed view appears at the bottom of the screen: **Details, Recipients, Editions, Resources, Events, and Attachments** for viewing or editing data. You can also **double-click the row or the “link” icon** to access the **prescription details page**, where you can manage all relevant information. ## Manage a Prescription [Section titled “Manage a Prescription”](#manage-a-prescription) You can manage a prescription either through the **Details tab** or the **prescription page**. * The **Details** tab includes the main prescription fields: * **Name** * **Description** * **Validity**: time interval between certifications * **Expiring**: number of days before expiry for status “expiring” * **Responsible**, **Assigned**, and **Observer** fields Click the **”+” button** to choose from **People**, **Office Users**, or **Roles** defined in the office’s **Safety Org Chart**. Multiple subjects can be assigned to the same role. These assignments are **automatically inherited** by all future editions of the same prescription. Caution Only **project users** can receive **notifications** when assigned as **Responsible, Assigned, or Observer**. Each user can customize notification settings in the **Preferences** menu. * **Recipients**: list of people registered for the prescription * **Examinations**: list of medical exams associated with the prescription * **Requested by**: elements whose risks are mitigated by the exam * **Attachments**: associate documents via file link or upload ## Add Recipients to a Prescription [Section titled “Add Recipients to a Prescription”](#add-recipients-to-a-prescription) Recipients are workers who require health surveillance due to risks related to their job, which may be tied to tasks, areas, equipment, or work phases. 1. Click **Recipients** 2. Click **New** 3. Select the employees and click **Save** Recipients are listed with a **Status**: * **“New”** until managed * **“Valid”** or **“Expired”** according to existing certificates * **“Expiring”** if the certificate is near expiry (based on the **Expiring** setting)  ### Associate Resources [Section titled “Associate Resources”](#associate-resources) From the **Requested by** menu, you can link **company resources** that require this prescription. This helps trace the prescription’s origin (tasks, roles, environments, etc.). 1. Select resources such as: * Job Task * Role * Equipment * Environment * Substance * Work Phase * PPE 2. Click **Next** 3. Select from the listed resources, click **Confirm**, then **Finish** Tip Linking a prescription to a **Work Phase** allows for a risk impact analysis.  ## Schedule a Medical Exam [Section titled “Schedule a Medical Exam”](#schedule-a-medical-exam) After adding recipients, you can schedule a medical exam. 1. From **Examinations**, click **New** 2. Click **Select** to choose the associated prescription 3. Verify the **validity** of the prescription 4. Complete the required fields and assign responsible roles 5. Click **Save**  ### Enroll People to an Exam [Section titled “Enroll People to an Exam”](#enroll-people-to-an-exam) 1. Select the exam 2. Click **Recipients**, then **New** 3. Only people already enrolled in the prescription will be shown 4. Select individuals and click **Save** The **exam status** will initially be **To Complete** ### Register Exam Outcome [Section titled “Register Exam Outcome”](#register-exam-outcome) You can register outcomes **individually** or in **bulk**. #### Single Entry [Section titled “Single Entry”](#single-entry) 1. Open the detail page of the exam with a **double click** 2. Select the **outcome**: `Passed` or `Failed` 3. Click **Save** #### Bulk Entry [Section titled “Bulk Entry”](#bulk-entry) 1. In the exam toolbar, click **Guided Procedures > Bulk Edit** 2. The list of registered participants appears 3. Click the **status badge** to change the result 4. (Optional) Tick the **“W” (warning)** box to flag the record 5. Click **Confirm** Caution Outcomes can only be edited until the certificate is issued.  ### Generate a Certificate [Section titled “Generate a Certificate”](#generate-a-certificate) Once the outcome is **“Passed”**, you can issue certificates. #### 1. Mass Creation Wizard [Section titled “1. Mass Creation Wizard”](#1-mass-creation-wizard) * Click **Guided Procedures** > **Mass Certificate Creation** * A list of recipients with outcome **“Passed”** appears * Select recipients and click **Confirm** #### 2. From the Detail Page [Section titled “2. From the Detail Page”](#2-from-the-detail-page) * Open the exam details * Review **start** and **end** validity dates * Click the **medal icon** to issue a certificate The certificate is now **valid** and visible in the **due date report**. ### Register an Existing Certificate (Past Surveillance) [Section titled “Register an Existing Certificate (Past Surveillance)”](#register-an-existing-certificate-past-surveillance) If you do not plan to schedule an exam, or need to record past health surveillance, you can register a certificate directly. 1. Go to the **Prescriptions** list 2. **Select** the desired prescription 3. From the **Recipients** tab toolbar, assign the people 4. Click **Guided Procedures > Mass Certificate Creation** 5. Select the recipients 6. Fill in certificate details and click **Confirm**, then **Finish** ### Link External Certificates to Company Prescriptions [Section titled “Link External Certificates to Company Prescriptions”](#link-external-certificates-to-company-prescriptions) If an employee has valid certificates issued by third parties, they can be linked to internal prescriptions. Tip You must ensure: * The **prescription exists** in the office * The **worker is registered** for the prescription To link: 1. Open **People** 2. Select the employee and open their **profile** 3. Go to the **Certificates** menu, click **New**, and enter data 4. Select the new certificate 5. In the **Actions** tab, click **New** 6. Select the company prescription and click **Save** The **expiration date** is inherited by default. To override: * Double-click the row * Uncheck “Inherit expiry date from certificate” * Set a new date and **Save** Tip If no expiry date is set, the certificate is considered always valid. ### Manage a Certificate [Section titled “Manage a Certificate”](#manage-a-certificate) In the **Recipients** tab, a certificate icon provides access to the **certificate page**, where you can: * **Print** * **Download** * **Attach files** 1. Click the icon to open the **certificate page** 2. View all info related to the **exam** and **result**, plus optional notes 3. **Editable dates** include **issue date** and **expiration** 4. Click the **Print** icon to export the document 5. Use the **”…”** button to choose from available templates 6. Click on the **Print** icon to print locally, or click **Next** to **export** or **save** the certificate in **Files**. Tip 4HSE provides some editable templates. Clicking on the **pencil icon** opens the editing tool. Once the changes are complete, you can save the new template so it’s available for future use.  --- # Maintenance > Management of maintenance plans, orders, and certificates in 4HSE for each office. The **Maintenance** section is located in the **Actions** area of each project **office** and is structured on two main levels: * **Plans**: define the **maintenance needs** for material resources and PPE within the office. * **Orders**: represent the **scheduling** of maintenance interventions. This section also allows you to: * **Record the outcome** of a maintenance task and certify its completion. * **Generate a maintenance certificate**, which can be saved, edited, exported, or printed in various formats using the **“Print”** button. ## Add a Maintenance Plan [Section titled “Add a Maintenance Plan”](#add-a-maintenance-plan) 1. Click **New** and select **New** to open the plan creation window. 2. The plan may concern a **single equipment item** (e.g., overhead crane) or a **homogeneous group** (e.g., elevators). You can later link equipment registered in the **Material Resources** section. 3. Set the **validity** of the maintenance, i.e., the interval between one order and the next. 4. Assign the roles of **Manager**, **Assignee**, and **Watcher**, choosing from **people**, **roles**, or **users** of the office. These roles will be **automatically inherited** in the planned orders for that plan. 5. Save the plan. Caution Notifications will only be sent if the assigned individuals are also **project users**.  After saving, the plan will appear in the list with all indicators set to zero. If you don’t see it immediately, click **Refresh** in the toolbar. **By selecting the plan row**, the tabs **Details**, **Recipients**, **Orders**, **Required by**, **Events** and **Attachments** will be activated below, useful for quickly reviewing or editing data.  A double click opens the **plan sheet**, allowing full management of the plan data and its associated orders.  ## Associate Equipment to be Maintained [Section titled “Associate Equipment to be Maintained”](#associate-equipment-to-be-maintained) You can associate equipment intended for maintenance as follows: 1. Go to the **Recipients** tab. 2. Click **New** and choose among the available options: * Equipment * Work Environments * PPE * Offices > **Example**: by selecting **Equipment**, you’ll access the list of registered resources. 3. Select the equipment to include and press **Save**. They will be listed as **Recipients** of the plan, with their corresponding **Status**: * **New**: not yet managed * **Valid / Expired**: based on whether a valid or expired maintenance certificate is present  ### Associate Resources [Section titled “Associate Resources”](#associate-resources) From the plan’s **“Requested by”** menu entry, you can specify which **company resources** require maintenance. This allows you to keep track of the link between maintenance and the specific needs arising from equipment, environments, etc. 1. Select the resources to associate from: * Equipment * Environment * Substance * PPE * Work Phase * Task * Homogeneous Group 2. Click **Next** to select from registered elements 3. Select the resources and click **Confirm**, then **Finish**  ### Schedule an Order [Section titled “Schedule an Order”](#schedule-an-order) Once the maintenance recipients are associated, you can schedule an order. 1. From the **Orders** menu, click **New** 2. Select the **Maintenance Plan** using **“Select”** All available maintenance plans for the office will be shown. If the desired plan is not listed, it needs to be created in the “Plans” section. 3. Check the **validity** of the plan 4. The roles of **Manager**, **Assignee**, and **Observer** are inherited, but can be edited for the specific order. If they are users, they will also be **recipients of notifications** for this task. 5. Click **Save**  ### Register Recipients for an Order [Section titled “Register Recipients for an Order”](#register-recipients-for-an-order) 1. Select the maintenance order 2. Click **Recipients**, then **New**. Only resources already linked to the maintenance plan will be available. If no recipients are associated with the plan, no resources will be shown for order enrollment. 3. Select the resources to register for the order and click **Save** The initial **status** of the order will be **To be filled**.  ## Linked Modules Management [Section titled “Linked Modules Management”](#linked-modules-management) The **Linked Modules** tab allows you to create and manage structured modules associated with maintenance actions. This feature enables the integration of technical checklists or operational reports directly into the maintenance workflow, automatically attaching the generated documentation to the issued certificate. Through this section, it is possible to define which data templates must be completed during the execution of a maintenance order. The complete guide for configuring and filling out modules is available in the [Linked Modules to Actions](/guides/action-forms/action-forms) section. ### Register the Outcome of a Maintenance Order [Section titled “Register the Outcome of a Maintenance Order”](#register-the-outcome-of-a-maintenance-order) You can record the outcome of an order in two ways: **individually** or using **bulk mode**. #### Single Mode [Section titled “Single Mode”](#single-mode) 1. Open the order detail by **double-clicking the enrollment row**. 2. Fill in the form by selecting the **outcome**: `Passed` or `Failed`. 3. Save. #### Bulk Mode [Section titled “Bulk Mode”](#bulk-mode) 1. From the edition toolbar, click **Wizards**, then select **Bulk Edit**. 2. The list of resources linked to the order will open. 3. Click the **status badge** to change it. 4. (Optional) Check the **“W” (warning)** box to visually flag a record that needs attention: an icon will appear next to the corresponding row. 5. Press **Confirm** to save all changes. Caution The evaluation can only be changed until the certificate is issued.  ### Generate a Certificate [Section titled “Generate a Certificate”](#generate-a-certificate) After recording the outcome of the order as **“passed”**, you can issue certificates: #### 1. Wizard for Bulk Certificate Creation [Section titled “1. Wizard for Bulk Certificate Creation”](#1-wizard-for-bulk-certificate-creation) * Click **Wizards** in the toolbar * Select **Bulk Certificate Creation** * A list of enrolled resources will be shown * Select the resources for which you want to issue certificates * Click **Confirm** #### 2. Issuance from Enrollment Details [Section titled “2. Issuance from Enrollment Details”](#2-issuance-from-enrollment-details) * Open the enrollment details (double-click the row or click theicon) * Check the **start and end validity dates** * Click the **badge icon**, which will automatically issue a certificate for the selected resource. Once done, the certificate is **valid** and visible in the **expiration schedule**.  ### Manage a Certificate [Section titled “Manage a Certificate”](#manage-a-certificate) In the **Certificate** column of the “Recipients” tab, the certificate icon is now visible. It gives access to the **certificate sheet**, where you can: * **Print** * **Download** * **Attach a document**. 1. Click to open the **certificate sheet**. 2. All information related to the **order** and the **result** is shown here, along with optional notes and fields. The editable dates relate to the **issue** and **expiration** of the certificate. 3. To export the document, click the **Print** icon 4. Click **”…​”** to access the list of available templates. 5. Select the **desired template** from the list and click **Save**, then **Next** to access the document preview. 6. Click the “Print” icon for local printing, or click **Next** to **export** or **archive** it in “Files”. Tip 4HSE provides some editable templates. By clicking the **pencil icon**, you can access the editing tool. Once modifications are done, the new template can be saved for future use.  ### Attachments [Section titled “Attachments”](#attachments) In “Attachments” you can link files related to the maintenance plan: * by adding links to **existing files** in **“Files”** * by uploading a **new file** --- # Personal Protective Equipment > Management, inventory, and delivery of PPE in 4HSE, including equipment and recipients. The following instructions refer to adding a single PPE item. If you need to upload multiple devices at once, you can use the **bulk import** feature via `.csv` (Excel) file by clicking the “Import” button. ## How to Add a Single PPE Item [Section titled “How to Add a Single PPE Item”](#how-to-add-a-single-ppe-item) 1. From the office menu, select **PPE**. 2. Click the **New** button at the top left. You will then be asked to choose the **insertion type** for the PPE: * **Copy:** Select this option to duplicate an existing PPE and modify it. * **New PPE:** Choose this option to configure a PPE from scratch. In this example, we will proceed by adding a **New PPE**. 3. Fill in the required fields: **name**, **description**, **category**, **type**, and **intended use**. Fields marked with a red asterisk are **mandatory**. 4. Click **Save** to complete the insertion.  ## Inventory of an Existing PPE [Section titled “Inventory of an Existing PPE”](#inventory-of-an-existing-ppe) If the PPE has already been added and you want to add it to the inventory to manage its specifics (quantity, expiration, etc.): 1. From the menu, select **PPE Inventory**. 2. Click **New** and then the “**Select**” button to find and choose the device you want to inventory. 3. Enter the additional required data (such as quantity, expiration, etc.) and click **Save**.  ## Determining Prescriptions [Section titled “Determining Prescriptions”](#determining-prescriptions) Scrolling through the actions menu, locate the area dedicated to Personal Protection. The menu is divided into two sections: * PPE Prescriptions * PPE Deliveries **Prescriptions** define which PPE will be assigned to workers, while **deliveries** correspond to the register of when the PPE was physically **delivered**, including the quantity handed out and the list of recipients. **Note:** To determine Prescriptions, it is essential that the devices have been previously registered in the material resources. Once the devices are registered in the material resources, you can proceed with configuring the **Prescriptions**: 1. From the **Actions** menu, under **Personal Protection**, select **PPE Prescriptions**. 2. Click the **New** icon. At this point, you can choose the **insertion type** for the allocation: * **New:** Choose this option to create a completely new allocation. * **Copy from:** Select this option to duplicate an existing PPE allocation and modify it. In this example, we will proceed with **New**. 3. In the **Name** field, enter the name of the device to assign. 4. Select the PPE from the list of available material resources by clicking on \***Select**. 5. Click **Save** to complete the insertion.  ## Assigning PPE Recipients [Section titled “Assigning PPE Recipients”](#assigning-ppe-recipients) 1. Select the row corresponding to the PPE name. At the bottom of the screen, the **detail** window will open automatically. The first tab displays the previously entered information: here you can edit or add new data if necessary. The next tab, **Recipients**, allows managing the **recipients** of this PPE allocation. 2. Click the **New** button to assign the PPE to people. A registration window will open where you can select the allocation recipients. Recipients are added with one of the following statuses: * **New** – PPE has not yet been delivered; * **Valid** – PPE is currently valid; * **Expired** – PPE has expired and needs replacement.  ## Associating Resources to the PPE [Section titled “Associating Resources to the PPE”](#associating-resources-to-the-ppe) The **Requested by** tab allows you to associate the PPE with contexts where the device’s use is required to mitigate a risk. Specifically, you can link: * Tasks * Roles * Equipment * Environments * Substances * Work phases 1. Select the item of interest and click **Next**. A complete list of available elements for association will be displayed. Select the desired ones and confirm by clicking **Confirm**. 2. Once the operation status shows **Completed**, click **Finish** to conclude. The **Requested by** tab will then be populated with all the resources where the use of this PPE is required as a risk mitigation measure. *** ## PPE Delivery [Section titled “PPE Delivery”](#ppe-delivery) ### 1. Creating a Delivery [Section titled “1. Creating a Delivery”](#1-creating-a-delivery) 1. Go to the **PPE Deliveries** menu and click **New**. 2. Select the **PPE allocation** for which you want to register the delivery and click **Save**. 3. Fill in the delivery details: * **Delivery date** * (Optional) **Time slot** and **location** 4. Indicate the **notification recipients**: * If recipients were already associated with the allocation, they will be proposed automatically. * You can add others by clicking **Add (+)** and selecting **people** or **roles** from the organizational chart. * After selection, click **Save**. Clicking the created delivery row opens the **Details menu** at the bottom, showing all information related to the allocation and delivery.  ### 2. Assigning Devices to People [Section titled “2. Assigning Devices to People”](#2-assigning-devices-to-people) 1. Click **New** in the **Recipients** tab. 2. All people previously associated with the allocation will be listed. 3. Select the people to whom you want to **deliver the PPE** and click **Save**. The initial status for each recipient will be **To be completed**. ### 3. Recording the Delivery Outcome [Section titled “3. Recording the Delivery Outcome”](#3-recording-the-delivery-outcome) The delivery outcome can be recorded in two ways: **single** or **bulk**. #### Single Mode [Section titled “Single Mode”](#single-mode) * Click theicon or **double-click** on the person’s name to open the detail window. * Select the **delivery outcome** (e.g., `Passed`, indicating successful delivery). * (Optional) Check the **W (warning)** box to highlight those needing attention. * Edit, if necessary: * **Start validity date** * **End validity date** * Associate the PPE with the **inventory** if the device is registered. * Specify the quantity delivered. The default is 1, but you can modify it if needed. The delivered device quantity will automatically update the available quantity in the inventory once the delivery certificate is issued. You can then proceed in two ways: * **Save** to keep the option to modify data later. * Or click the **rosette icon** to **issue the delivery certificate**. Caution Once the certificate is issued, the delivery is considered complete and cannot be modified. #### Bulk Mode [Section titled “Bulk Mode”](#bulk-mode) * From the **Recipients** tab toolbar, click **Guided procedures** and select **Bulk edit**. * The list of all recipients will be shown. * Click the **status badge** to change it to `Passed` (equivalent to delivered). * (Optional) Check the **W (warning)** box to highlight those needing attention. * When finished, click **Confirm** to save all changes. * In bulk mode, the number of devices delivered is always 1 per recipient. Caution The outcome registration can only be modified until the delivery certificate is issued. From the guided procedures, you can also issue delivery certificates for all recipients who passed delivery using the **Bulk certificate creation** tool.  ## Printing the Delivery Certificate [Section titled “Printing the Delivery Certificate”](#printing-the-delivery-certificate) To open the **certificate printing** tool, click the blue icon representing the certificate. A window will open allowing you to verify and edit, if necessary, the data to be included on the certificate. These include: * Recipient’s **name** * The **action type**, automatically associated with the PPE allocation * The **issue date**, which can be modified or kept as previously entered * The **expiration date**, automatically inherited from the inventory if the PPE is registered, or manually editable if not registered  1. Verify all data accuracy and proceed with printing the certificate by clicking the **printer icon** button. 2. Select the desired **template** and click **Save**. You can then choose to print the certificate or generate a file in **PDF**, **HTML**, or **Word** format. 3. Archive the document in the office folder or save it locally on your PC for personal management. ## Multiple PPE delivery [Section titled “Multiple PPE delivery”](#multiple-ppe-delivery) In addition to the standard flow via the **PPE Deliveries** menu, a guided procedure is available to record the delivery of several PPE items to a single worker in a single operation. It is intended for cases where a worker receives multiple equipment at the same time (e.g. onboarding, role change or PPE wear). It is useful to track multiple deliveries and to produce a **delivery record** signed by the worker that acts as the delivery receipt. The procedure runs in **two steps**: in the first you select and configure what to deliver; in the second you review the final record and collect the recipient’s signature. ### Starting the procedure [Section titled “Starting the procedure”](#starting-the-procedure) 1. Open the **Worker** detail page. 2. From the toolbar, click the **Wizards** menu and select **Multiple PPE Delivery**.  ### Step 1 — Selecting the allocations [Section titled “Step 1 — Selecting the allocations”](#step-1--selecting-the-allocations) A window opens with the table of **PPE allocations** currently active for the worker. Each row has the following columns: * **Action code** and **Action name** of the allocation * **Last certificate release** date, if any * **Last certificate expiry** date, if any * **Status** of the allocation (New, Valid, Expiring, Expired) * **Inventory** — dropdown of the available inventory entries (with remaining quantity in brackets). If the action is not linked to a specific PPE inventory entry, a free text field is available to provide an indication * **Expiry date** of the new certificate — pre-filled with the due date of the inventory item selected or, if missing, computed from the allocation validity; editable * **Qty** — number of items delivered for that allocation (default 1) * **Return** — tick if, together with the delivery of the new PPE, the previously held PPE is being handed back Below the table a free **Notes** field is available; it will be reported read-only on the final record. For each allocation you want to deliver: 1. Tick the **checkbox** in the first column of the row: the editable fields of the row become enabled. 2. Verify or edit the inventory entry, the expiry date and the quantity. 3. If the delivery is a return, tick **Return**.  When done, click **Save** in the toolbar to move to Step 2. ### Step 2 — Final record and signature [Section titled “Step 2 — Final record and signature”](#step-2--final-record-and-signature) Step 2 shows the **delivery record** to be signed by the recipient. The record contains: * title and introduction of the record * summary of the performed deliveries and any notes * dedicated space for the recipient’s **signature** Once the signature has been placed, clicking **Save** again: 1. A prompt asks in which folder of the 4HSE filesystem to save the signed delivery document, which can be printed later. 2. On confirmation, the record is saved as an attachment and, for each selected allocation, 4HSE automatically creates: * a **delivery certificate**, with today’s issue date and the expiry indicated on the row * the link from the certificate to the **PPE allocation** * the **signed delivery record** attached to the produced certificates 3. If the delivery is linked to an inventory entry, the stock is automatically decremented based on the indicated quantity.  --- # Procedures > Management of prevention procedures: creation, recipients, reports, and attachments. The section dedicated to procedures is located within the **Prevention Actions** area of each project **office**. From **Actions**, select the **Procedures menu**, which is structured on two levels: * **Procedures**: define the **complete set of procedures** for the office. * **Reports**: define the **planning of renewals or reviews** of procedures by creating **reports**. Within the **Procedures** section, you can also: * **Register an existing certificate** (e.g., to monitor the expiration of an existing procedure or one that you don’t want to schedule). * **Schedule a report**. * **Register the result of a report** and generate a revision certificate. * **Generate a certificate** or upload an external one. ## Add a new procedure [Section titled “Add a new procedure”](#add-a-new-procedure) Tip Procedures can refer to **any business activity, process, or document** that requires periodic review or verification (e.g., grounding checks, periodic DVR review, or environmental assessments for specific risks). 1. Click **New** at the top left to choose the **type of procedure** to add. You can either **copy** an existing procedure or create a **new procedure**, which can be configured freely through a dedicated interface. In this example, we will add a **new environmental assessment procedure for physical or chemical agents**. 2. Click **Save**.  The **new row** corresponding to the procedure will now appear in the window, with all indicators set to **zero**. (If no changes are visible, just click **Refresh** in the toolbar). Tip **By selecting the procedure row**, tabs for **Details, Recipients, Reports, Resources, Events, and Attachments** become available at the bottom of the screen for data viewing and quick editing.  Double-clicking the row or the **link icon** opens the **procedure detail page**, where you can **view and manage** all related information: recipients, reports, and more.  ## Manage a procedure [Section titled “Manage a procedure”](#manage-a-procedure) Procedures can be managed both from the **Details tab** and the **Procedure detail page**. * The **Details** tab shows key information: * **Name** * **Description** * **Validity**: the interval between one review and the next. * **Expiring**: number of days before the expiration when the procedure is marked as “expiring”. * Assignment of **Responsible**, **Assigned**, and **Observer** roles. Use the **”+” button** to choose between **People**, **Users**, and **Roles** defined in the office’s “Safety Organization Chart”. Multiple users or roles can be assigned to the same task. These assignments are **automatically inherited by reports** scheduled for this procedure. Caution Only individuals who are **Users of the project** will receive **notifications** as **Responsible**, **Assigned**, or **Observer**. Each user can customize notification preferences in the **Preferences** menu. * The **Recipients** tab shows the people and items involved in the procedure. * The **Reports** tab lists all revisions of the procedure in reverse chronological order. * The **Requested by** tab lists items whose risks are mitigated by the procedure’s validity. * In the **Attachments** tab, you can: * **Link an existing file** from “Files” * **Upload a new file** ## Add recipients to a procedure [Section titled “Add recipients to a procedure”](#add-recipients-to-a-procedure) **Recipients** are the resources (workers, environments, equipment, etc.) for which the procedure applies. For each procedure, in the **Recipients** section, you must associate either: * The relevant **work phases**, or * The **office**, if one assessment covers all environments. This association is required for certified assessment of the procedure. > Recipients can be selected based on: > > * **Job roles** > * **Operational areas or departments** > * **Equipment** > * Specific **work phases** 1. Click **Recipients** 2. Click **New** 3. Select the recipient(s) using the available categories (hold Shift for multi-selection), then click **Save** (e.g., all environments subject to environmental assessments). 4. You can add recipients from multiple categories if needed. 5. All associated recipients will now be visible with their **certificate status**: * **“New”** until managed * **“Valid”** or **“Expired”** depending on the recorded certificate dates * **“Expiring”** if near expiration (based on the **Expiring** field of the course)  ## Associate resources [Section titled “Associate resources”](#associate-resources) From the **Requested by** menu of a procedure, you can indicate which **company resources** require the procedure. 1. Select resources from: * Role * Equipment * Environment * Substance * PPE * Job role * Work phase * Homogeneous group * Supplier 2. Click **Next** to select from existing items 3. Select the resources and click **Confirm**, then **Finish** Tip Associating a procedure with a **work phase** allows you to assess its impact on risk.  ## Schedule a report [Section titled “Schedule a report”](#schedule-a-report) Once recipients are linked to a procedure, you can schedule a report. 1. From the **Reports** menu, click **New** 2. Select the **Procedure** using **“Select”** (All available procedures for the office will be listed. If not listed, you must create the procedure first.) 3. Confirm the **procedure validity** 4. Set the **date** 5. The **Responsible**, **Assigned**, and **Observer** roles are inherited from the procedure but can be edited. If they are users, they will receive **notifications** for this activity. 6. Click **Save** ## Enroll recipients in a report [Section titled “Enroll recipients in a report”](#enroll-recipients-in-a-report) 1. Select the **Report** 2. Click **Recipients**, then **New** Only previously assigned procedure recipients will be listed. If none were added to the procedure, no options will be available. 3. Select the recipients and click **Save** Initial **report status** will be **To be completed**. ## Linked Modules Management [Section titled “Linked Modules Management”](#linked-modules-management) The **Linked Modules** tab allows you to create and manage structured modules associated with procedures. This feature enables the integration of technical checklists or operational reports directly into the procedure workflow, automatically attaching the generated documentation to the issued report. Through this section, it is possible to define which data templates must be completed during the execution of a procedure. The complete guide for configuring and filling out modules is available in the [Linked Modules to Procedures](/guides/action-forms/action-forms) section. ## Register the result of a report [Section titled “Register the result of a report”](#register-the-result-of-a-report) Results can be recorded **individually** or in **bulk**. ### Individual mode [Section titled “Individual mode”](#individual-mode) 1. Open the report detail by **double-clicking the recipient row** 2. Select the **result**: `Passed` or `Failed` 3. Click **Save** ### Bulk mode [Section titled “Bulk mode”](#bulk-mode) 1. From the report toolbar, click **Wizards** > **Bulk edit** 2. The list of report recipients will appear 3. Click the **status badge** to update it 4. (Optional) Check the **“W” (warning)** box to flag the entry with a visual icon 5. Click **Confirm** to save changes Caution The result can only be edited until the certificate is issued.  ## Generate a certificate [Section titled “Generate a certificate”](#generate-a-certificate) After registering a `Passed` result, you can issue the certificates. ### 1. Bulk creation via wizard [Section titled “1. Bulk creation via wizard”](#1-bulk-creation-via-wizard) * Click **Wizards** in the toolbar * Select **Bulk certificate creation** * The list of report recipients will appear * Select the recipients * Click **Confirm** ### 2. From report details [Section titled “2. From report details”](#2-from-report-details) * Open the report detail (double-click the row or click theicon) * Check the **start** and **end validity dates** * Click the **ribbon icon** to automatically issue a certificate The certificate will now be **valid** and visible in the **calendar**.  ## Manage a certificate [Section titled “Manage a certificate”](#manage-a-certificate) In the **Certificate** column of the “Recipients” tab, click the icon to open the **certificate detail page**, where you can: * **Print** * **Download** * **Attach a document** 1. Click to open the **certificate detail page** 2. It shows all report and result information, including notes and optional fields. Editable dates are for **issue** and **expiration** 3. To export, click the **Print** icon 4. Click **”…”** to browse available templates 5. Select the **desired template**, click **Save**, then **Next** to preview 6. Use **Print** to print locally or click **Next** to **export** or **archive** to “Files” Tip 4HSE provides editable templates. Click the **pencil icon** to open the editor, then save your custom template for future use.  ### Attachments [Section titled “Attachments”](#attachments) In the **Attachments** tab, you can: * Add a link to **existing files** in **“Files”** * Upload a **new file** --- # Training > Training management: courses, editions, certificates, and attachments in 4HSE. The **Training** section is located within the **Prevention Actions** area of each project **office**. From **Actions**, select the **Training menu**, which is structured on two levels: * **Courses**: Define the company’s **training needs**. * **Editions**: Establish the **planning** of course execution and renewal dates.  Within the **Training** section, you can also: * **Register an existing certificate** (e.g., for previous training or training without prior planning). * **Plan an edition**. * **Record the outcome of a planned training edition**. * **Produce a certificate** or upload an external one. * **Associate an employee’s certificates with company courses** and monitor their expiration. (e.g., a course issues certificates that attest to various skills, equalization of externally acquired training with company-delivered courses, or registration of previous training from an individual’s profile). ### Adding a New Course [Section titled “Adding a New Course”](#adding-a-new-course) 1. Click on **New** in the top left to choose the **course type** to add. You can choose between adding a course using the **Copy** tool or adding a **New course**, which can be freely configured through the dedicated interface that will open after clicking. In this example, we will choose to add a **standard general training course**. 2. Click on **Save**.  The **new row** corresponding to the training course will now appear within the window, with all indicators at **zero**. (If you don’t see any changes, simply click **Refresh** in the toolbar). Tip **By selecting the course row,** the **Details, Recipients, Editions, Resources, and Attachments tabs** become active at the bottom of the screen for data viewing or quick editing.  A **double click on the row or the “link” icon** will take you to the **course card**. From here, you can **view and manage** all information related to the course, participants, edition dates, and more in detail.  ### Managing a Course [Section titled “Managing a Course”](#managing-a-course) A course can be managed from both the **“Details Tab”** and the **“Course Card”**. * The **Details** gather the main course information: * **Name** * **Description** * **Session type**: indicates how the course is structured. Two options are available: * **Base and update**: the course consists of a **first base edition** followed by periodic **update** editions to be repeated over the years. In this case, you can also fill in the **Base course duration** and **Update course duration** fields. * **Single**: the course consists of a **single edition** that will not be repeated. In this case, you can also fill in the **Course duration** field. * **Validity**, which is the time interval between a certification and its renewal. * **Expiring**, which is the number of days before the expiration date when that specific activity is considered to be in an “expiring” status. * Indication of the **“Course Manager,” “Assigned,” and “Observer.”** With the **”+” button**, you can choose between **People**, **Office Users**, and **Roles** previously defined in the **Office Safety Organization Chart**. You can associate multiple subjects from different categories with the same role for a course. This association is **automatically inherited in subsequently planned Editions for the same course.** Caution Only if they correspond to project **Users** will the indicated individuals **receive notifications** as **“Manager,” “Assigned,” or “Observer.”** Each user can customize how they receive these notifications in the platform’s **Preferences** menu. * In **Recipients**, you can view the people from the office already enrolled in the course. * In **Editions**, the editions of the selected course are displayed in chronological order from most to least recent. * In **Requested by**, all elements whose risks will be mitigated by the administration of the training course are listed. * In **Attachments**, you can associate documentation related to the course: * By adding a **link to an existing file** in “Files.” * By uploading a **new file**. ### Adding Recipients to a Course [Section titled “Adding Recipients to a Course”](#adding-recipients-to-a-course) Recipients are the people who need to attend training courses based on the risks they face while performing their work. These can depend on their role, area, work equipment, or work phase. Each worker can be enrolled in one or more courses, mandatory or optional, but always necessary for their health and safety. 1. Click on **Recipients**. 2. Click on **New**. 3. Select the employees to be trained for the chosen course (press Shift for multiple selections) and click **Save**. 4. All course participants will be listed as **Recipients**, and each will show a **Status**: * **“New”** until managed. * **“Valid”** or **“Expired”** according to the dates reported in any training certificates already registered for the employee. * **“Expiring”** if the certificate’s expiration is approaching. The number of days preceding the expiration is set in the course’s **“Expiring”** field.  ### Associating Resources [Section titled “Associating Resources”](#associating-resources) From the course menu item **“Requested by”**, you can indicate which **company resources** necessitate the course. This way, you can keep track of the link between the course and specific training needs derived from duties, equipment, work environments, etc. 1. Select the resources to associate from: * Role * Job Position * Equipment * Environment * Substance * Work Phase * PPE 2. Click **Next** to select from the cataloged items. 3. Select the resources and click **Confirm**, then **Done**. Tip Associating an action with a **work phase** allows you to assess its impact on risks.  ### Planning an Edition [Section titled “Planning an Edition”](#planning-an-edition) Once recipients are associated with the course, you can plan an edition. 1. From the **Editions** menu, click **New**. 2. Select the **Course** via **“Select”**. All available courses for the office will be displayed. If the desired course is not found, you need to create it in the “Courses” section. 3. Verify the **validity** of the course. 4. Indicate the **date**, **edition type** (Base/Update), instructor, and location. 5. The roles of **Manager**, **Assigned**, and **Observer** are inherited but can be modified for a specific edition. These individuals, if users, will also **receive notifications** for this activity. 6. Click **Save**. ### Enrolling People in an Edition [Section titled “Enrolling People in an Edition”](#enrolling-people-in-an-edition) 1. Select the edition. 2. Click **Recipients**, then **New**. Only people already enrolled in the course will be suggested. If no recipients have been associated with the course, no people will be displayed for enrollment in the edition. 3. Select the people you want to enroll in the edition and click **Save**. The initial training **status** will be **To be completed**. ### Recording the Outcome of an Edition [Section titled “Recording the Outcome of an Edition”](#recording-the-outcome-of-an-edition) You can record the outcome of an edition in two ways: **individually** or in **bulk**, depending on the number of enrollees. #### Individual Mode [Section titled “Individual Mode”](#individual-mode) 1. Open the enrollment detail card by **double-clicking on the enrollee’s row**. 2. Fill out the form by selecting the **outcome**: `Passed` or `Failed`. 3. Save. #### Bulk Mode [Section titled “Bulk Mode”](#bulk-mode) 1. From the edition’s toolbar, click **Wizards**, then select **Bulk Edit**. 2. The list of enrollees for the edition opens. 3. Click on the **status badge** to change it. 4. (Optional) Check the **“W” (warning) box** to visually highlight a record that requires attention: an icon will be shown next to the corresponding row. 5. Press **Confirm** to save all changes. Caution The evaluation can only be changed until the certificate is issued.  ### Producing a Certificate [Section titled “Producing a Certificate”](#producing-a-certificate) After recording the outcome of the edition as **“passed”**, you can issue certificates: #### 1. Wizard for Bulk Creation [Section titled “1. Wizard for Bulk Creation”](#1-wizard-for-bulk-creation) * Click **Wizards** in the toolbar. * Select **Bulk Certificate Creation**. * The list of enrollees for the edition is shown. * Select the people for whom you want to issue the certificate. * Click **Confirm**. #### 2. Specific Issuance from Enrollment Detail [Section titled “2. Specific Issuance from Enrollment Detail”](#2-specific-issuance-from-enrollment-detail) * Open the enrollment detail (double-click on the row or click theicon). * Check the **start validity** and **end validity** dates. * Click the **rosette icon**; this will automatically issue a certificate for the participant. Once done, the certificate is **valid** and visible in the **expiration calendar**. ### Registering a Certificate (Previous Training) [Section titled “Registering a Certificate (Previous Training)”](#registering-a-certificate-previous-training) If you do not wish to plan an edition or if you want to register **previous training**, you can register a certificate. This operation can be performed from the list of **“Courses”** in the office menu. 1. Click on **Courses**. 2. **Select the desired course**. 3. In the toolbar of the **“Recipients”** tab, associate the participants to be certified. 4. Click **Wizards > Bulk Certificate Creation**. 5. Select the participants. 6. Fill in the certificate details and click **Confirm**. 7. Click **Done**. ### Associating an Employee’s Certificates with Company Courses [Section titled “Associating an Employee’s Certificates with Company Courses”](#associating-an-employees-certificates-with-company-courses) It’s possible for a worker to possess valid certificates issued by third parties or attestations referring to other courses. These can be equated to a company course by associating the corresponding certificate. Tip It’s necessary that: * The **reference course** exists in the office. * The **worker is enrolled** in the course. To associate: 1. Go to the **People** menu. 2. Select the worker and open their **card**. 3. From the **Certificates** menu, click **New** and fill in the data. 4. Select the newly created certificate. 5. In the **Actions** tab, click **New**. 6. Select the company reference course and click **Save**. The **expiration date** is automatically inherited. To change it: * Double-click on the row. * Uncheck the “Inherit expiration date from certificate” flag. * Enter the new date and **Save**. Tip If the certificate was created without an expiration date, it will always be considered valid. ### Managing a Certificate [Section titled “Managing a Certificate”](#managing-a-certificate) In the **Certificate** column of the “People” tab, the certificate icon is now visible, allowing access to the **certificate card**, from which you can: * **Print** * **Archive** * **Download** * **Attach a third-party certificate**. 1. Click to open the **certificate card**. 2. All information related to the **edition** and **result** is reported here, along with notes and optional fields. The editable dates refer to the certificate’s **issue** and **expiration**. 3. To export the document, click the **Print** icon. 4. Click on **”…​”** to access the list of available templates. 5. Select the **desired template** from the list and click **Save**, then next to access the document preview. 6. Click the “Print” icon for the local printer, or click “Next” to **export** or **archive** in “Files”. Tip 4HSE provides several editable templates. Clicking the **pencil icon** accesses the editing tool. Once modifications are complete, you can save the new template for future use.  ### Attachments [Section titled “Attachments”](#attachments) In “Attachments,” you can associate files related to the course: * By adding a link to **existing files** in **“Files”**. * By uploading a **new file**. ### Associating an Employee’s Certificates with Company Courses [Section titled “Associating an Employee’s Certificates with Company Courses”](#associating-an-employees-certificates-with-company-courses-1) It can happen that a worker obtains certificates and attestations with different names from those of courses taken within the company, but with the same training content. Alternatively, a company course, conducted in multiple sessions that characterize the same edition, may grant the worker more than one certificate to attest to different competencies. Furthermore, it may be necessary to upload all certificates a newly hired worker possesses in one session. To **monitor the expiration date reported on these certificates** and to **equate training obtained elsewhere** with that performed within the company, you can **create the corresponding certificate within 4HSE and associate it with the reference course.** Tip It’s necessary that a **reference course** for the type of attestation to be registered **already exists at the office** where the worker is employed, and that **the worker is associated with it.** If the worker possesses a certificate for a course not provided by the company, it is necessary to create it and enroll the worker before proceeding. To **associate an employee’s certificate with a company course**: 1. Go to the **People** menu. 2. Select the **worker** whose certifications you want to update, then **open their card.** 3. Select the “Certificates” menu. Using the “New” button, **create the certificate in 4HSE**, selecting the type of action it refers to and entering the document details in the appropriate sections, then save. 4. Select the newly created certificate, which will appear in a new row. 5. In the **Details** window below, select the **Actions** tab. 6. Select **New**. 7. **Associate the company course** to which you want the certificate to refer and save. The certificate’s **expiration date** will be **automatically inherited** and shown in the expiration calendar. To modify the certificate’s expiration date, once the course is associated, double-click on the new row displayed in the “Actions” tab and uncheck the “Inherit expiration date from certificate” box, then enter the new expiration date and save. Tip If no expiration date was indicated when creating the certificate in 4HSE (step 3), the certificate will always be valid. --- # Scheduler and planner --- # Scheduler and Calendar > Guide to using the scheduler and calendar to manage and filter deadlines in 4HSE. From the 4HSE interface, you can access the scheduler in two ways: In 4HSE, you can access the scheduler in two ways: * directly from the **main scheduler** icon on the desktop * from the office-specific scheduler The **difference** between the two is that the desktop scheduler gathers and displays deadlines and scheduled activities from **multiple projects and offices**. This means that if you are managing multiple companies, you can see an overview of all deadlines and planned actions, and filter to view only those relevant to the company of interest. If you are managing a **single project**, you can view all deadlines across the offices of that project. ## Office Scheduler [Section titled “Office Scheduler”](#office-scheduler) 1. Open the project and select the relevant office. 2. Click **Scheduler** in the left menu. The interface displays a set of filters labeled **“Search”** on the left side, while the right side is split into two tabs: **Deadlines** and **Calendar**. **a)** The **Deadlines tab** shows all activities that are due, as they have been scheduled as part of prevention actions. **b)** The tab on the right is the **Calendar**, which displays when the planned actions should be carried out. **c)** The **Search** filter panel allows you to display only certain types of actions: * Training * Maintenance * Procedures * Health Surveillance * Personal Protective Equipment (PPE) * Documents  You can also filter by **action status**, regardless of the type: * Expired * Expiring * New * Valid * Revoked * Rejected Another option is to filter by **date range**: * Last session of an action * Next session * Expiry date Or perform a **text search** by: * Action name * Recipient name All these filters can be combined to refine the search and get the desired result. ## Deadlines Tab [Section titled “Deadlines Tab”](#deadlines-tab) Each column has a header indicating its content. The first column contains icons indicating the **type of action**, followed by the **code**, the **name of the action**, and the **recipient icon**, which may represent: * a person * equipment * an environment * a substance Next come the **recipient code** and **name**, the **date of the last session**, the **expiry date**, and the **next scheduled date** if applicable. Finally, the **status** is displayed: * **Valid**: a currently effective prevention action * **Expired**: an action that needs to be renewed or is no longer effective * **New**: used for resources (human or material) for which no action has yet been performed, but a need has been identified. For example, a new employee enrolled in a training course will remain in “New” status until they are registered in a specific edition. * **Expiring**: a still-valid action approaching its expiry date, within the configured notice window. * **Revoked** and **Rejected**: used for [permits to work](/guides/permit-to-work/permit-to-work/) whose certificate was, respectively, withdrawn before its natural expiry or not approved. They are highlighted with a red badge. ## Calendar Tab [Section titled “Calendar Tab”](#calendar-tab) The **Calendar tab** displays all scheduled activities. The top toolbar allows you to select the preferred view mode: * Daily * Weekly * Monthly * Agenda view ## Exporting Deadlines and Calendar Views [Section titled “Exporting Deadlines and Calendar Views”](#exporting-deadlines-and-calendar-views) Both the **calendar** and the **deadlines list** can be **exported**. * The calendar exports to an `.ics` file, which can be imported into other time management tools. * The list of deadlines can be exported as a `.csv` file. ## Desktop Scheduler [Section titled “Desktop Scheduler”](#desktop-scheduler) The interface is very similar to the **office scheduler**. By scrolling through the filter menu on the left, you’ll notice that the main difference is the ability to search across **offices** and **projects**.  This tool allows you to view **upcoming and scheduled activities** for all offices (if you have only one project), or deadlines and activities from all projects if managing multiple ones in 4HSE. As with the office scheduler, all filters can be combined to narrow down results. The same export options are available, along with all the previously described features. For **planning actions and related deadlines**, please refer to the guides on **Prevention Actions**. --- # Supplier management --- # Associate Suppliers to Offices > How to associate suppliers to an office in 4HSE. Tip Consult the [Supplier Management](/guides/supplier-management/supplier-management) guide before proceeding Below is the **procedure** to correctly associate a supplier to an office. 1. Open the office where the supplier is involved. 2. From the office menu, select **Human Resources** and then **Suppliers** in the submenu.  3. Click on the **new** icon and select the desired supplier.  4. Click on **save** Note: before associating a work phase to a supplier, you need to create their profile first. For more information on how to create a new supplier profile, see [Supplier Management](/guides/supplier-management/supplier-management) ## Association Permissions [Section titled “Association Permissions”](#association-permissions) Once the office-supplier association is created, office users will have the following permissions on the supplier: * **Office Manager** -> **Supplier Admin** * **Office Guest** -> **Supplier User** The supplier users in turn acquire the following permissions on the office: * **Supplier User** -> **Office Guest** * **Supplier User** -> **Office Procedures User** --- # Associate Work Phase with Supplier > Procedure for associating a work phase with a supplier in 4HSE. Tip Refer to the guides [Supplier Management](/guides/supplier-management/supplier-management) and [DUVRI: Drafting and Printing](/guides/supplier-management/duvri) Here is the **procedure** to correctly associate a work phase with a supplier: 1. Open the office where the supplier is involved. 2. From the office menu, select **Work Phases**. 3. Select the desired **work phase** (add it if it is not already listed).  4. Expand/open the selected work phase by clicking the button. 5. Select **Suppliers** from the menu.  6. Click the **New** iconand select the relevant supplier.  **NOTE**: if the supplier is not already associated with the current office, they will be associated automatically. See [Associate Suppliers to Offices](/guides/supplier-management/associate-supplier-to-office/#association-permissions) for further details on permissions. 7. Click **Save** **Note:** Before associating a work phase with a supplier, their profile must be created. For more information on how to create a new supplier profile, see [Supplier Management](/guides/supplier-management/supplier-management). --- # DUVRI: Drafting and Printing > Guide to drafting, printing, exporting, and customizing the DUVRI document in 4HSE. The platform provides a **DUVRI template** that allows for automatic document generation. This template can be **customized** by the user or alternatively **replaced** with a custom model. After [registering the supplier](/guides/supplier-management/supplier-management), the user can choose to generate the DUVRI for: * **All offices in a project** (e.g., Main office, Office 1, Office 2, etc.) * A **specific office** (e.g., Office 2) ## DUVRI for the Supplier Across All Project Offices [Section titled “DUVRI for the Supplier Across All Project Offices”](#duvri-for-the-supplier-across-all-project-offices) Once the relevant project is open: 1. From the main menu, click on **Suppliers**. 2. Select the relevant **supplier** (e.g., Supplier 1). 3. Click the **Print** button . From here, simply select the desired template and proceed with **printing** or **exporting** in Microsoft Word, PDF, or HTML format.  ## DUVRI for the Supplier in a Specific Office [Section titled “DUVRI for the Supplier in a Specific Office”](#duvri-for-the-supplier-in-a-specific-office) Once the relevant office is open: 1. From the office menu, click and expand the **Human Resources** section. 2. Click on **Suppliers**. 3. Click the **Print** button . As before, select the desired template and proceed with **printing** or **exporting** in Microsoft Word or PDF format. ## Customizing the DUVRI Template [Section titled “Customizing the DUVRI Template”](#customizing-the-duvri-template) The **DUVRI template layout** provided by 4HSE is fully customizable and can also be entirely replaced with your own custom template. You can choose to use the default layout provided by 4HSE or upload your own DUVRI template. For more details, see the [template customization guide](https://dev.4hse.com/guides/print-templates-building/). Please note that, in addition to the **DUVRI**, the platform allows you to draft, customize, print, or export other types of documents, such as: * Risk Assessment Document (DVR) * Course attendance certificates * Technical and safety data sheets * PPE delivery register * Fitness certificates * Work environments * Substances * Appointments --- # Supplier Records Management > How to register, manage, and link suppliers and work phases in 4HSE. Within the work project, it is possible to **register suppliers**, associating them with a specific site and specifying which **work phases** they are involved in. In this section, you can also **search** for the desired supplier within the list, view the **history**, and **export the list** in csv format.  The details for each supplier can be entered through a dedicated window where the following are collected: * registry details and contact information * documents * associated work phases Furthermore, with a view toward full collaboration, one or more user accounts can be created for each supplier, with **specific access levels** to the platform. Based on all the data related to the supplier, it is possible to produce, print, or export the **DUVRI** (for more information, please refer to [DUVRI Drafting, Printing, and Exporting](/guides/supplier-management/duvri)). Additionally, we remind you that to generate the DUVRI, the supplier must be associated with the Work Phase(s) (refer to [Associate a work phase to a supplier](/guides/supplier-management/associate-work-phase-to-supplier)). Let’s see how to: * **Add a supplier** * **Delete a supplier** * **View the record details** ## Insert a supplier [Section titled “Insert a supplier”](#insert-a-supplier) Below is the procedure for inserting a new supplier. 1. Open the safety project menu and select the **Suppliers** tab. 2. Click on **new** and enter the supplier details. 3. Click on **save** . ## Delete a supplier [Section titled “Delete a supplier”](#delete-a-supplier) To delete a supplier, simply: 1. Select the row corresponding to the supplier you want to delete. 2. Click on the **delete** icon . ## View the record details [Section titled “View the record details”](#view-the-record-details) Once the supplier is selected, click on the expand button .  Within the supplier window, it is possible to: * view **details** and **contact info** * view the associated **work phases** * add or remove **users** linked to the supplier * create **folders** and **attach documents** ## Access from the Desktop icon [Section titled “Access from the Desktop icon”](#access-from-the-desktop-icon) By double-clicking on the Suppliers icon on the desktop, the list of suppliers accessible to the user is displayed, based on the projects they are associated with. From this list as well, for each supplier, it is possible to view details and define associations with sites, work phases, and other entities.  --- # Approvals: Project Administrator Guide > Operational guide for project administrators: how to understand and manage the approval system. The **Approvals** system is a feature designed to ensure maximum control over certifications and documents submitted by parties external to the project. In **4HSE**, when a **Supplier**, as the recipient of a **Procedure**, issues a certificate, it is subject to an **approval** process. The certificate issued by the supplier does not immediately validate the associated **Action**, which changes to **Valid** status only after review and confirmation by a project manager (**Admin** or **Manager**). ## 1. Assigning a Procedure to a Supplier [Section titled “1. Assigning a Procedure to a Supplier”](#1-assigning-a-procedure-to-a-supplier) The project **Manager** can assign a **Procedure** to a supplier, for example to request: * drafting of a DUVRI; * specific maintenance activities; * technical inspections carried out by external parties. In 4HSE, a supplier can be assigned **only Actions of type Procedure**.  ## 2. Receiving an Approval Request [Section titled “2. Receiving an Approval Request”](#2-receiving-an-approval-request) When the supplier, after completing the assigned preventive action, issues a certificate and associates it with that preventive action, the system automatically generates an **approval request**. The associated Action **is not updated immediately**; its status remains unchanged until the review process is completed. ## 3. Review and Outcome [Section titled “3. Review and Outcome”](#3-review-and-outcome) When an approval request is created, the project manager receives an **automatic notification**. The **Approvals** icon is available on the Desktop and provides access to the list of approvals to manage.  For each request, the manager can review: * certificate details; * the attachment uploaded by the supplier. After verification, the manager can proceed in one of the following ways: * **Accept**: the approval is confirmed, the certificate is validated, and the Action in the schedule changes to **Valid** status. The supplier receives a notification with a positive outcome. * **Reject**: if the documentation is incorrect or incomplete, the request is rejected. It is recommended to provide a reason in the **notes** field. The supplier receives a notification with the negative outcome and must submit a new approval request. ## Notifications and Communications [Section titled “Notifications and Communications”](#notifications-and-communications) Each phase of the workflow is supported by an automatic notification system: * the **Project Manager** receives a notification when a new approval request is available; * the **Supplier** receives a notification with the outcome of the request (Accepted or Rejected), including any notes. ## Managing Approval Requests [Section titled “Managing Approval Requests”](#managing-approval-requests) The **Approvals** interface allows involved users to view and manage all approval requests sent or received. The list shows the **complete history of steps** for each request, allowing full traceability of the approval process.  ## Search Filters [Section titled “Search Filters”](#search-filters) The search panel includes the following filters: * **Text search** * **Status**: filters requests based on the overall process status: * **In Progress** * **Completed** * **Step**: filters individual phases of the approval process: * **New** * **Approved** * **Rejected** It is important to distinguish between **step** and **status**: * the **step** represents a single action within the approval process; * the **status** indicates the overall condition of the request. ## Approval Details [Section titled “Approval Details”](#approval-details) Clicking on a row in the list opens the details section, organized into tabs: * **Details**: shows specific information about the approval. * **Events**: lists all executed steps, indicating who performed the action, the type of step, the date, and any notes. * **Attachments**: displays files attached to the approval, such as certificates submitted for validation. Each approval corresponds to one row in the list. When created, the initial **step** is “Creation” and the **status** is “In Progress”. At the end of the process, for example after approval, the row shows the **step** “Approved” and the **status** “Completed”. All historical details of step changes and attachments are available in the **Events** tab. ### Workflow Example [Section titled “Workflow Example”](#workflow-example) 1. The supplier creates an approval request * a step with status **New** is generated * the request is **In Progress** 2. The project manager approves the request * a new step with status **Approved** is generated * the request changes to **Completed** In case of rejection, a step with status **Rejected** is generated. ### List Columns [Section titled “List Columns”](#list-columns) The approvals list includes the following columns: | Column | Description | | ---------------- | ------------------------------------------------------------------------------------ | | **Name** | Approval name, generally composed of “Approval” + the Action name. | | **Step** | Process phase: **New**, **Approved**, or **Rejected**. | | **Status** | Overall request status: **In Progress** or **Completed**. | | **Requested by** | Email address of the user who performed the step (creation, approval, or rejection). | | **Dates** | Creation and modification dates of the step. | Tip See the guide [Supplier Management](/guides/supplier-management/supplier-management) --- # Approvals: Supplier Guide > Operational guide for suppliers: how to understand and manage the approval system. The **Approvals** system is a feature designed to ensure maximum control over certifications and documents submitted by parties external to the project. In **4HSE**, a supplier may be assigned a **Procedure** by the project manager, for example to carry out a technical activity, perform maintenance, or produce specific documentation. Once the required activity has been completed, the supplier must issue the related **certificate**, associating it with the assigned **Action**. Issuing the certificate does not immediately validate the Action: the system automatically starts an **approval** process, submitting the certificate for review by a project manager (**Admin** or **Manager**). The Action will change to **Valid** status only if the outcome is positive. Tip For more information about issuing certificates and managing **Procedure-type actions**, see the document [Procedure](/guides/prevention-actions/procedure-management). ## Issuing the Certificate and Submitting an Approval Request [Section titled “Issuing the Certificate and Submitting an Approval Request”](#issuing-the-certificate-and-submitting-an-approval-request) To create an approval request, the supplier must access their **supplier profile** from the **Suppliers** list (Desktop icon). Once inside the profile, they can issue the certificate and automatically send the approval request to the project manager. There are three main scenarios for submitting a request: ### 1. Certificate from the Supplier’s Schedule [Section titled “1. Certificate from the Supplier’s Schedule”](#1-certificate-from-the-suppliers-schedule) * The supplier selects a certificate directly from their schedule; * The association with the Action is automatic; * The system immediately generates the approval request; * Uploading the certificate file is required to complete the approval request.  ### 2. Certificate Created from the “Certificates” Menu [Section titled “2. Certificate Created from the “Certificates” Menu”](#2-certificate-created-from-the-certificates-menu) * The supplier creates a new certificate from the **Certificates** menu; * They must select the certificate and associate the assigned preventive Action; * Only at this point is the approval request created.  ### 3. Certificate Without File or Without Association [Section titled “3. Certificate Without File or Without Association”](#3-certificate-without-file-or-without-association) * If the certificate is created from the schedule but the approval submission process is canceled or the required certificate file is not uploaded, the approval request **is not completed**. * In this case, the supplier must access the **Certificates** menu, select the certificate that **was created even though the approval request was not sent**, link it to the Action, and follow the guided procedure to complete the request. Note In summary: the **approval request is created only when a certificate is linked to an Action**. ### 4. Waiting for Approval [Section titled “4. Waiting for Approval”](#4-waiting-for-approval) After saving the certificate, the Action **is not considered valid** until it has been reviewed by the project manager. The supplier will receive an automatic notification with the outcome of the approval request. ## Notifications and Communications [Section titled “Notifications and Communications”](#notifications-and-communications) Each phase of the approval workflow is supported by an automatic notification system: * the **Project Manager** receives a notification when a new approval request is available; * the **Supplier** receives a notification with the outcome of the request (Accepted or Rejected), including any notes. ### Setting the Supplier’s Assigned Contact [Section titled “Setting the Supplier’s Assigned Contact”](#setting-the-suppliers-assigned-contact) To ensure notifications are received (deadlines, schedules, approval outcomes), it is possible to designate one or more **assigned contacts** for the supplier. These users will receive the notifications. To set the assigned contact: 1. Access the **Info** section from the supplier’s main menu; 2. Enter the designated user’s **email address** in the **“Assigned Contact”** field. Note The email address must correspond to an active user in 4HSE; otherwise, the system will not be able to send notifications. ### Registering the User [Section titled “Registering the User”](#registering-the-user) If the assigned contact’s email is not yet registered as an active user: 1. Go to **Administration → Permissions** in the main menu. 2. Add the user’s email to the **Admin** or **Manager** group. For more information about permission meanings and access levels, see the document [Supplier Permissions](/guides/permissions/supplier-permissions). ## Managing Approval Requests [Section titled “Managing Approval Requests”](#managing-approval-requests) The **Approvals** interface allows involved users to view and manage all approval requests sent or received. The list shows the **complete history of steps** for each request, ensuring full traceability of the approval process.  ## Search Filters [Section titled “Search Filters”](#search-filters) The search panel includes the following filters: * **Text search** * **Status**: filters requests based on the overall process status: * **In Progress** * **Completed** * **Step**: filters individual phases of the approval process: * **New** * **Approved** * **Rejected** It is important to distinguish between **step** and **status**: * the **step** represents a single action within the approval process; * the **status** indicates the overall condition of the request. ## Approval Details [Section titled “Approval Details”](#approval-details) Clicking on a row in the list opens the details section, organized into tabs: * **Details**: shows specific information about the approval. * **Events**: lists all executed steps, indicating who performed the action, the type of step, the date, and any notes. * **Attachments**: displays files attached to the approval, such as certificates submitted for validation. Each approval corresponds to one row in the list. When created, the initial **step** is “Creation” and the **status** is “In Progress”. At the end of the process, for example after approval, the row shows the **step** “Approved” and the **status** “Completed”. All historical details of step changes and attachments are available in the **Events** tab. ### Workflow Example [Section titled “Workflow Example”](#workflow-example) 1. The supplier creates an approval request * a step with status **New** is generated * the request is **In Progress** 2. The project manager approves the request * a new step with status **Approved** is generated * the request changes to **Completed** In case of rejection, a step with status **Rejected** is generated. ### List Columns [Section titled “List Columns”](#list-columns) The approvals list includes the following columns: | Column | Description | | ---------------- | ------------------------------------------------------------------------------------ | | **Name** | Approval name, generally composed of “Approval” + the Action name. | | **Step** | Process phase: **New**, **Approved**, or **Rejected**. | | **Status** | Overall request status: **In Progress** or **Completed**. | | **Requested by** | Email address of the user who performed the step (creation, approval, or rejection). | | **Dates** | Creation and modification dates of the step. | Tip See the guide [Supplier Management](/guides/supplier-management/supplier-management) --- # Expired invitation link > How to unblock a User stuck in the 'Pending' status. When an Admin creates a new User in 4HSE, the system sends an invitation email to the address provided, containing a link to complete the registration. Until the first login is performed, the User remains in the **Pending** status. The link contained in the email has a limited validity of **30 minutes**. If the email ends up in the spam folder, or if the recipient does not open the link in time, the first login cannot be completed and the User is unable to enter the platform. This article describes how to recognize the problem and the correct procedure to unblock the User. ### Admin side [Section titled “Admin side”](#admin-side) In the user list of the Project or Office, the User continues to appear in the **Pending** status even some time after the invitation has been sent. ### User side [Section titled “User side”](#user-side) The User reports one of the following situations: * they have never received the invitation email; * they have found the invitation email, but the link, once opened, no longer works. In both cases, the User cannot complete the first login and set their own password. ## What not to do: deleting and recreating the User [Section titled “What not to do: deleting and recreating the User”](#what-not-to-do-deleting-and-recreating-the-user) When an invitation does not go through, a frequent reaction is to delete the User from the list and add them back, expecting that a new invitation email will be generated. **This operation does not solve the problem.** Deleting the User from the list and adding the same email address again does not trigger a new invitation email. The result is that the User still cannot access the platform and the Admin still sees the **Pending** status. The correct way to allow the User to enter the platform is the password reset procedure described in the next section. ## Solution: password reset from the login page [Section titled “Solution: password reset from the login page”](#solution-password-reset-from-the-login-page) To resolve the situation, no action is required from the Admin: the User can complete the first login independently, by using the password reset procedure. 1. Open the 4HSE login page. 2. Select the **Forgot password?** link. 3. Enter the **Email** with which the User was registered in 4HSE. 4. Select **Submit**. 5. Check the inbox (including the spam folder) and open the link received. 6. Set the new password and confirm it. 7. Select **Submit** to complete the operation. At the end of the procedure, the User can log in with the email and the password just set. The status in 4HSE changes from **Pending** to **Active**. Note The link in the password reset email also has a validity of **30 minutes**. If it expires before being used, the procedure must be repeated from the login page. For the full details of the reset procedure, refer to the [Forgot password](/guides/troubleshooting/forgot-password) guide. ## Common Issues Troubleshooting [Section titled “Common Issues Troubleshooting”](#common-issues-troubleshooting) Below is a summary of the most frequent situations related to user invitations that did not go through, and the recommended solutions. | Issue | Common Cause | Recommended Solution | | :------------------------------------------------------------- | :----------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Invitation email not received** | The email ended up in the spam/junk folder, or the address provided contains a typo. | Check the **spam** folder. Verify the address with the Admin: **the email is the exact identifier** with which the User was registered in 4HSE. | | **Invitation link not working** | The link in the invitation email has a limited validity of **30 minutes** and has expired. | Proceed with the **password reset** from the login page: the new email contains a valid link to set the password and complete the first login. | | **User deleted and added again without receiving a new email** | Adding the same email address again does not generate a new invitation. | Do not delete and recreate the User. The User must perform the **password reset** procedure from the login page, using the email with which they were originally registered. | | **The User is still “Pending” after the password reset** | The password reset was successful, but the first login has not yet been performed. | The User must log in to 4HSE with the new password. Once they are inside the platform, the status automatically changes to **Active**. | --- # Forgot Password > Guide to the password recovery and reset procedure in 4HSE. Access to 4HSE is based on the email address used during registration, which uniquely identifies each user. If you are unable to log in due to forgotten credentials, the platform provides a guided procedure for recovering your password. ## Password Reset Procedure [Section titled “Password Reset Procedure”](#password-reset-procedure) To reset the password of your account: 1. From the login screen, select the **Forgot password?** link. 2. You will be asked to enter the **Email** associated with your account. 3. Select **Send**. > **Note:** If the email entered is not associated with an active account, the system cannot send the reset link. 4. The system will email the provided address, containing a password reset link. > **Warning:** The link is valid for **30 minutes**. 5. Open the received link. A guided procedure will help you set a new password using two fields: new password and confirmation. 6. When finished, select **Send** to complete the operation.  After completing these steps, the new password will be active immediately. ## Troubleshooting Common Access Issues [Section titled “Troubleshooting Common Access Issues”](#troubleshooting-common-access-issues) Below are the most frequent issues related to access and password recovery, along with the recommended solutions. ### Login and Password Reset Issues [Section titled “Login and Password Reset Issues”](#login-and-password-reset-issues) | Issue | Common Cause | Recommended Solution | | :-------------------------- | :------------------------------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------- | | **Login failed** | Entering an email address different from the one used during registration, or a typo. | Check that the email address is correct. **The email is the exact identifier** used to register the user in 4HSE. | | **Reset link not received** | Entering an email address different from the one used during registration, or a typo. | Check that the email address is correct. **The email is the exact identifier** used to register the user in 4HSE. | | **Reset link not received** | The email ended up in the spam/junk folder. | Check your **spam** or junk folder. If the issue persists, contact your administrator. | | **Reset link not working** | The password reset link is valid for **30 minutes**. | Restart the **Forgot password** procedure and use the new link. | ### Registration and Whitelabel Issues [Section titled “Registration and Whitelabel Issues”](#registration-and-whitelabel-issues) | Issue | Common Cause | Recommended Solution | | :--------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- | | **Newly created user** | The user has not yet completed the first login. | Check the invitation email and click the link to set the initial password. Until this step is completed, the user is not registered on the platform. | | **Login failed** | The user is trying to access a different domain than the one in which they were registered. **This can happen only in projects that use a custom domain (whitelabel).** | Log in from the correct domain. If the user was created under the wrong domain, the account must be recreated. | Tip To improve account security, it is always recommended to protect your credentials and consider enabling multi-factor authentication (MFA). ## Managing and Changing the Password as an Active User [Section titled “Managing and Changing the Password as an Active User”](#managing-and-changing-the-password-as-an-active-user) If you are already logged into the system, you can change your password at any time through the **account management panel**. The [Account Management](/guides/first-steps/account-console) guide provides instructions on: * accessing the account management panel * configuring access settings * changing the password * enabling multifactor authentication (MFA) --- # Widget --- # Widget Editor > Guide to using the editor to create and edit custom widgets in 4HSE. The widget editor is a tool that allows you to create and modify widgets. A widget can be thought of as a small application—for example, a form for entering personal data, or a checklist to inspect a piece of equipment. A widget is made up of other widgets. Generally, we call the base widgets *components*, the building blocks available in the editor, but technically they are also widgets. By combining layout components, static components, and input components, we build our widget. The result is a tree of components/widgets nested within one another. ## Creating a New Widget [Section titled “Creating a New Widget”](#creating-a-new-widget) To create a new widget, we start from the file system.  By selecting **New widget**, a window opens allowing us to create and edit the widget. First, we must choose a base template. Currently, four templates are available: * Blank template: contains only a layout component (more on this later) * Vertical form: a template designed to easily create forms with input fields stacked vertically * Inline form: a template meant for organizing content horizontally * Form: an example template for building a checklist Note After choosing the template, its content can be modified. ## Editing a Widget [Section titled “Editing a Widget”](#editing-a-widget) Similarly, to edit an existing widget, start from the file system, select the widget (with `.hf` extension), then click the pencil icon in the toolbar or right-click the widget and choose **Edit**.  This opens the editor directly with the selected widget, ready for editing. ## Editor [Section titled “Editor”](#editor) Whether you’re creating a new widget or editing an existing one, you’ll be working in the editor. The editor window contains several key areas: ### Components [Section titled “Components”](#components) The left panel lists all available components that can be added to your widget (more will be added in future updates). These include: * Labeled input: components with a label and an input field. Ideal for vertical forms.  * Basic input: plain input fields, useful for inline forms.  * Static: non-interactive components like labels, titles, etc. * Layout: used to organize content visually (explained further below) * Snippets: reusable pieces of widgets ### Tree [Section titled “Tree”](#tree) Also in the left panel, under the “TREE” tab, you can view your widget’s structure. This is useful to understand the actual layout of the widget you’re editing. Selecting a node in the tree also highlights it in the center preview and in the properties panel on the right. Selecting components is necessary to edit, delete, or duplicate them. Sometimes components are tightly packed, so selecting them from the tree is easier. ### Preview – Center Panel [Section titled “Preview – Center Panel”](#preview--center-panel) The center of the editor displays a live preview of the widget. This graphical preview shows what the widget will look like in use. However, since this area is used for other tasks too, the preview may not be 100% accurate. Use the toolbar’s preview function for an exact result. Hovering over a component highlights it and shows its type. Clicking a component selects it, which also updates the tree and the properties panel on the right. Once selected, two icons appear: one to duplicate and one to delete the component. ### Properties [Section titled “Properties”](#properties) The properties panel is on the right. Each component has properties—for example, text size, margins, or an input’s default value. These are shown when the component is selected in the tree or preview. Changes made here will immediately reflect in the preview (you may need to click elsewhere, like the white space or another property, for them to apply). Each property can be enabled via its corresponding checkbox. If the checkbox is off, the component uses the default value. If it’s on, you can customize the property. This lets you tailor components to your needs. Different components have different sets of properties. ### Drag & Drop [Section titled “Drag & Drop”](#drag--drop) You can drag components in several ways: * From the **COMPONENTS** panel to the preview area to add new elements exactly where you want them. * Within the preview area to rearrange them. Holding the CTRL key during drag turns the cursor into a plus icon, meaning the component will be duplicated, not moved. ## Layouts [Section titled “Layouts”](#layouts) Let’s take a closer look at layout components. These are essential for organizing your content effectively. Using them correctly saves time and gives precise control over layout; using them incorrectly can lead to frustration. ### Inline Layout [Section titled “Inline Layout”](#inline-layout) This layout mimics word processor forms. Components are arranged side-by-side and wrap to the next line automatically when space runs out.  Only certain components can be displayed this way. Others, like titles or labeled inputs, will automatically break to a new line. ### Horizontal Layout [Section titled “Horizontal Layout”](#horizontal-layout) This looks similar to the inline layout but offers more control. Components can be spaced evenly, centered, aligned to the right, etc.  ### Vertical Layout [Section titled “Vertical Layout”](#vertical-layout) Components are stacked vertically. Ideal for simple forms or, when combined with horizontal layouts, for complex arrangements. ## Example: Rack Inspection Checklist [Section titled “Example: Rack Inspection Checklist”](#example-rack-inspection-checklist) Let’s create a checklist for inspecting storage racks.  This form uses both vertical and horizontal layouts. We first set the toolbar option: *Device layout*: **A4** We started with a vertical layout and added a title.  Next, we added two *horizontal layouts* and inserted *text boxes* from the labeled input components. To align the *Inspection date* and *Name* fields, we set the label width to 120px. To right-align the *Rack No./Department* and *Signature* fields, we set the layout property *Spacing between items* for both horizontal layouts.  We then added another *horizontal layout* containing four *vertical layouts*. Each vertical layout contains a *title* with a description: No., Items to check, etc. We configured the following: * Horizontal layout padding: 0 * Vertical layout widths: 10%, 50%, 14%, 14% * Disabled vertical layout height using the checkbox * Vertical layout borders: Solid, 1px * Title font size: 3 * Title font weight: Normal  We duplicated the horizontal layout.  In the new row, we removed titles from the last two columns and increased the font size of the remaining titles from 3 to 4. Thanks to disabling the “Height” property earlier, these now appear as empty cells that still fill the vertical space. We duplicated this row three more times.  We then updated the titles and adjusted row heights to achieve the final design.  Tip To simplify the creation of these types of content, we are designing a new table-style layout. Tip Don’t forget to save your work frequently—just in case! Tip If you make a mistake, don’t worry! Use the undo button in the toolbar to go back. --- # How to Use Widgets > A practical guide on running, using, and saving widgets in 4HSE. In the [Widget Editor](/guides/widget/widget-designer-intro) article, we covered how to create and edit widgets. Now let’s see how we can use them. A widget is saved as a file in the 4HSE file system and has the `.hf` extension. To *run* or use a widget, simply double-click on the file.  Note You can also select the widget file you want to use and click the button in the toolbar, or right-click on the file and select **Run**. Running the widget opens it in a new window.  In this window, you can fill out the widget form, save the filled form, or print it. A widget with the `.hf` extension works like a template that you can run as many times as needed. Each time you launch an `.hf` file—even the same one—it’s like opening a new instance of the widget. The most common use case is creating a widget-form that can be filled out whenever needed. Each time you run a widget and save it, a new file is created—this file is the result of your filled-out widget, and it has the `.hc` extension.   You can reopen and edit your `.hc` file, or create a new one by launching the original `.hf` file. --- # Work phases and risk assessment --- # DVR Printing > Guide to printing and exporting the DVR in 4HSE, including template selection. You can access the DVR printing function from several entry points, listed below. Tip See the guide [DVR Writing](/guides/work-phases-and-risk-assessment/dvr-writing) ## Priting from the “Office” menu [Section titled “Priting from the “Office” menu”](#priting-from-the-office-menu) Click the row corresponding to the relevant office and then click the button in the “Details” tab at the bottom. Then follow the steps in the “Printing procedure” section.  ## Printing from the “Info” menu of an office [Section titled “Printing from the “Info” menu of an office”](#printing-from-the-info-menu-of-an-office) Open the office detail page and go to the “Info” menu. In the “Details” tab, click the button. Then follow the steps in the “Printing procedure” section.  ## Printing procedure [Section titled “Printing procedure”](#printing-procedure) ### 1. Template selection [Section titled “1. Template selection”](#1-template-selection) When opening the print menu, the system displays a dropdown with the **recently used templates** (up to 5). If this is the first time printing for that context, the field will be empty. To search for a different template, click the **Search** button. An advanced selection window will open with three selectable filters via the toolbar buttons: * **Current project** (active by default) — shows templates associated with the current project. * **Partner** — shows templates provided by the partner, with the option to filter by country. * **4HSE** — shows templates provided by 4HSE, with the option to filter by country. When selecting the **Partner** or **4HSE** source, a country filter becomes available on the toolbar to narrow down the results. A text search field is also available to quickly find the desired template. Once a template is selected from the window, it will be automatically added to the recent templates list for quicker access in future sessions.  ### 2. Template choice [Section titled “2. Template choice”](#2-template-choice) For the DVR, the following are available: * The **main document template** * The **associated lists** (employees, equipment, work phases, etc.), which will be printed as **separate attachments**. All print templates can be customized by clicking the **Edit** button . For customization instructions, see [Customizing Templates](/guides/file-management/template-custom). Once the template is selected, click the **“Next”** button to proceed to the **Preview** step. 3. Do you want to print or export the generated document? * **To print the DVR:** Click the button at the top left to send the document to a local printer. * **To export the DVR:** Click the “Next” button at the bottom of the screen to move to the “Save as” screen. Here, you can export the document in *HTML* or *Microsoft Word 2007/2010* format. * **Save to your PC:** If the “Save to PC” option is selected, click the “Confirm” button at the bottom of the screen to start the export process. * **Save to 4HSE Documents:** If you select “Save to documents”, you’ll be able to choose the internal folder where you want to save the exported document. 1. Click the button to open your reserved space for documents and attachments. Once you choose the folder where to save the DVR, click thebutton at the top left of the screen. If the destination folder does not exist yet, you can create a new one directly from the toolbar by clicking the **New Folder** button.The folder name will now appear on the previous screen. Click “Next” to continue. 2. A new tab, previously disabled, called “Details” will now be available. In this screen, you can assign some properties to the document before exporting it to the selected folder. Finally, click the “Confirm” button at the bottom of the screen to start the export process. --- # DVR Writing > Guide to compiling, assessing, and printing the DVR in 4HSE, including template customization. All data included in the DVR is taken from information entered into the 4HSE system to describe and manage workplace safety. Therefore, the first step is to complete the necessary sections of the platform, following the instructions below. Tip See the guides [Insert Offices and People](/guides/first-steps/insert-offices-and-people) and [DVR Printing](/guides/work-phases-and-risk-assessment/dvr-printing) ## Enter office-related information [Section titled “Enter office-related information”](#enter-office-related-information) This step involves replicating the company structure and current safety setup within 4HSE. Proceed as follows: 1. Open an office 2. Go to the **Human Resources** menu: * Link the **PEOPLE** 3. Go to the **Material Resources** menu: * Add or import **ENVIRONMENTS** * Add or import **EQUIPMENT** * Add or import **SUBSTANCES** 4. Go to the **Work Phases** menu: * Create the **Work Phases** 5. Go to the **Safety Organization** menu: * Add the **ROLES** * Assign the **NOMINATED PERSONS** 6. Go to the **Actions** menu: * Add **TRAINING** courses * List **PPE (Personal Protective Equipment)** * Plan **MAINTENANCE** activities * List **PROCEDURES** ## Perform risk assessment [Section titled “Perform risk assessment”](#perform-risk-assessment) In the **Work Phases** menu: 1. Open a work phase: * Associate the **SOURCES** * List the **HAZARDS** (by creating or linking them) * Identify **RISKS** (by marking a hazard as “PRESENT”) * Associate **RISK MANAGEMENT ACTIONS** * Assign the **PEOPLE** involved in the phase * Link suppliers (only for DUVRI) 2. Assess a risk: * Open the risk matrix by clicking the **RISK ASSESSMENT** button within each “Risk” item * Enter the **INITIAL PROBABILITY AND DAMAGE** values to define the **INITIAL RISK** * Enter the **PROBABILITY AND DAMAGE IMPACT** values for each mitigation action to calculate the **RESIDUAL RISK** ## Edit and save a template [Section titled “Edit and save a template”](#edit-and-save-a-template) When accessing the document print menu, in addition to selecting an available template, you can customize it by editing the underlying HTML. Choose one from the list using the icon, then save with.  **Click to view and edit the related HTML code.** A preview editor will open, with the code editor on the right and a live preview on the left.  Once you’ve made changes, you can save your version using the icon. Select the desired destination within the related “Archive” file system and click “Save”.  The modified file will be used automatically for the first export of the document and will then appear in the list of available templates for that document. --- # The Risk Assessment Matrix > Guide to using the PxD matrix for risk assessment within work phases in 4HSE. Risk **assessment** in 4HSE can be performed using the **PxD matrix**, accessible from the **Work Phases** menu via the button within each risk entry. Tip To understand how to access the matrix and perform risk assessment, see [Work Phases and Risk Assessment](/guides/work-phases-and-risk-assessment/work-phases) Note Before adding a new risk, you must indicate its presence in the **Hazards** tab by checking the **PRESENT** box. Once selected, the risk will appear in the **Risks** tab with initial, variation, and final risk values all set to 0.  The matrix allows you to define **Probability** and **Damage** values to determine the **Initial Risk**. After linking **mitigation actions**, each can be assigned an impact value on the **initial risk**, which may be adjusted over time. This results in the **Residual Risk** value.  ## Probability and Damage: Matrix Structure [Section titled “Probability and Damage: Matrix Structure”](#probability-and-damage-matrix-structure) The **matrix** is structured as a Cartesian grid, with: * the **Damage (D)** value on the X-axis, representing the impact severity if the event occurs * the **Probability (P)** value on the Y-axis, representing how likely the event is to occur Each risk has both an **initial value** and a **final (residual) value**. The final value depends on the **mitigation actions** taken, for which you can define their **impact** on both probability and damage. **Probability** and **Damage** are rated on a scale from 1 to 9: * From **Unlikely** to **Very Likely** for probability * From **Minor** to **Very Severe** for damage   To **add** a mitigation action (after it has been linked to the relevant work phase): 1. Click the **Actions** tab at the bottom 2. Click **New** and select the desired action 3. Define the **impact values** for probability and damage 4. Click **Save** to confirm the entry or changes  ## Risk Values [Section titled “Risk Values”](#risk-values) After defining **probability**, **damage**, and linking the necessary **actions**, the matrix will display two risk values: * **Initial Risk** * **Residual Risk** Each risk value is represented by a **color** indicating the **severity** and corresponding **priority for action**: * **Blue**: very low * **Green**: low * **Yellow**: medium * **Orange**: high * **Red**: very high You can view the full legend, including the associated risk values and intervention priorities, by hovering over the **question mark icon** next to **Risk Matrix**.  The list of risks associated with each work phase is shown in the **Risks** tab (where you previously accessed the assessment matrix), displaying: * **Initial Risk** * **Variation** * **Final Risk** To **edit the values**, either double-click the corresponding row or click the **open in new window** button.  **Note:** If a risk has been entered but not yet assessed, all three values will be 0. --- # Work Phases and Risk Assessment > Managing work phases and risk assessment in 4HSE, with practical examples. Work phases are used to describe in detail the tasks performed by workers in different roles. This is essential for identifying **hazards** associated with the physical resources used (work environments, equipment, and substances), and consequently, for identifying and assessing the **risks** to which workers are exposed. Through this analysis, it becomes possible to define the most effective **mitigation actions**, also considering **exposure time**, in order to ensure adequate prevention and protect workers’ health. Tip Linking **Actions** to **Work Phases** allows you to automate the notification of tasks to be performed and the workers they apply to. These notifications are shown in the **Suggestions** section. To create a new work phase: 1. Access the relevant office; 2. Open the “Work Phases” menu; 3. Click on **“NEW”**; 4. Fill in the dialog with the required data; 5. Save to add the new phase to the list. Note For more details, please refer to the dedicated sections on **Prevention Actions** and **Contractor Management and DUVRI**. ## Risk Assessment [Section titled “Risk Assessment”](#risk-assessment) Risk assessment in 4HSE is carried out using a **matrix**, accessible via the button available in each risk entry.   This matrix allows you to: * Determine the values for **Probability** and **Severity**, which define the **Initial Risk**; * Link **mitigation actions**, to which an **impact** value can be assigned; * Calculate the **Residual Risk**, taking into account the effect of the applied actions. This value can be updated over time to reflect changes in operating conditions or prevention measures. ### How to perform a risk assessment [Section titled “How to perform a risk assessment”](#how-to-perform-a-risk-assessment) 1. **Open a work phase**, then: * Link the **Sources** (environments, equipment, substances); * List the **Hazards**, by linking or creating them. If needed, enable the **“Present”** flag to indicate that the hazard is active in that phase;  * Identify the **Risks**; * Link the appropriate **Mitigation Actions**;  * Link the **People** involved in the phase; * (Optional, for DUVRI) Link the **Suppliers**. 2. **Assess each risk**: * Enter the **matrix** by clicking on the **“Risk Assessment”** button in the **Risk** entry; * Enter the **Initial Probability** and **Initial Severity** values to determine the **Initial Risk**; * For each **mitigation action**, enter the **impact on Probability and Severity** to calculate the **Residual Risk**.  --- # Release v2.0.x > Release notes for 4HSE v2.0 ## v2.0.0 — January 2020 [Section titled “v2.0.0 — January 2020”](#v200--january-2020) ### New Features [Section titled “New Features”](#new-features) * **4HSE v2 platform** — Complete rewrite of the application with a modern architecture, new user interface, and improved data management. This major release includes redesigned modules for managing offices, projects, people, actions, certificates, risks, demands, equipment, substances, work environments, and materials (PPE). * **New access control system** — A completely redesigned permission system provides fine-grained control over who can access and modify data across the application. * **Notification system** — A new notification engine delivers alerts and updates to users based on configurable rules and triggers. * **Contextual help** — Integrated help links throughout the application provide quick access to relevant documentation. * **Document templates** — Support for document templates (DVR and others) with dynamic data population. ## v2.0.1–v2.0.23 — March 2020 [Section titled “v2.0.1–v2.0.23 — March 2020”](#v201v2023--march-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * Multiple rounds of bug fixes and stability improvements following the v2.0 launch, including fixes to forms, grids, permissions, notifications, invoicing, certificates, material items, document management, office creation wizards, and action suggestions. --- # Release v2.10.x > Release notes for 4HSE v2.10 ## v2.10.0 — August 2021 [Section titled “v2.10.0 — August 2021”](#v2100--august-2021) ### New Features [Section titled “New Features”](#new-features) * **Certificate management overhaul** — The certificate module has been completely rewritten with new list views, detail forms, action management, and bulk editing capabilities for action session subscriptions. * **New API endpoints** — Added REST API endpoints for certificates, certificate actions, action sessions, and action subscriptions. ### Improvements [Section titled “Improvements”](#improvements) * **Certificate views** — New computed certificate views with automatic updates provide always-current data. * **Local data filtering** — Improved client-side data filtering for faster and more responsive list views. * **Office copy** — The office copy feature now preserves certificate associations. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Various fixes** — Fixed multiple issues with certificate display, action window management, and data loading. ## v2.10.1–v2.10.2 — August 2021 [Section titled “v2.10.1–v2.10.2 — August 2021”](#v2101v2102--august-2021) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple fixes including data display and navigation corrections. --- # Release v2.11.x > Release notes for 4HSE v2.11 ## v2.11.0 — September 2021 [Section titled “v2.11.0 — September 2021”](#v2110--september-2021) ### New Features [Section titled “New Features”](#new-features) * **New project management** — A completely redesigned project list and detail view with improved forms, grid displays, and navigation. * **Scheduled view updates** — Views are now automatically updated on a scheduled basis, ensuring data accuracy without manual intervention. * **API documentation viewer** — A new interactive API documentation viewer makes it easier to explore and understand the available API endpoints. ### Improvements [Section titled “Improvements”](#improvements) * **Subscription management** — Improved subscription status handling with better access control integration. * **First access wizard** — Improved the first-time user setup wizard. * **Project error reporting** — Better error reporting during project creation. * **View hook system** — A new view hook system enables more efficient data recalculation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Subscription status** — Fixed an issue where subscription status changes could trigger incorrect behavior. * **Project grid** — Fixed display issues in the project grid. * **Help context** — Fixed several contextual help link issues. * **Multiple fixes** — Fixed various issues with access control, data display, and navigation. ## v2.11.1 — October 2021 [Section titled “v2.11.1 — October 2021”](#v2111--october-2021) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Multiple fixes** — Fixed several issues reported in production. --- # Release v2.12.x > Release notes for 4HSE v2.12 ## v2.12.0 — October 2021 [Section titled “v2.12.0 — October 2021”](#v2120--october-2021) ### New Features [Section titled “New Features”](#new-features) * **Subscription and billing management** — A comprehensive subscription management system with plan selection, billing details, invoice management, and automated payment processing via webhooks. * **Admin panel** — New administrative tools for managing partners, subscriptions, project statistics, and user activity logs. * **Website user API** — New API endpoint for user management from the website. ### Improvements [Section titled “Improvements”](#improvements) * **Person management** — Improved person detail view with better navigation and data display across offices, actions, and certificates. * **Contextual configuration** — Forms and grids now support contextual configuration for more relevant data display. * **Attachment management** — Improved authentication handling for file access. * **Print reports** — Fixed and improved print report generation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Various fixes** — Fixed multiple issues including address book display, person office grid, entity employee creation, project validation, and contextual help links. ## v2.12.2–v2.12.4 — November 2021 [Section titled “v2.12.2–v2.12.4 — November 2021”](#v2122v2124--november-2021) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including subscription handling, data display corrections, orphan dependency cleanup, and project deletion improvements. --- # Release v2.13.x > Release notes for 4HSE v2.13 ## v2.13.1 — November 2021 [Section titled “v2.13.1 — November 2021”](#v2131--november-2021) ### New Features [Section titled “New Features”](#new-features) * **Sales panel** — A new sales management panel provides an overview of partners, subscriptions, and project statistics with filtering and search capabilities. * **Employee count tracking** — Active employee counts are now displayed in subscription and partner lists for easier capacity management. * **User activity statistics** — New user login and activity statistics help track platform usage. * **Subscription API** — New REST API endpoints for subscription management. ### Improvements [Section titled “Improvements”](#improvements) * **Partner management** — Improved partner forms with subscription tabs, invoice management, and better navigation. * **Grid filtering** — Added combo filter behavior for more flexible grid filtering. * **Project deletion** — Improved project deletion with better dependency handling. * **Security headers** — Improved content security policy configuration. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Multiple fixes** — Fixed various issues including search, filtering, toolbar display, permission management, and navigation corrections. ## v2.13.2 — December 2021 [Section titled “v2.13.2 — December 2021”](#v2132--december-2021) ### Improvements [Section titled “Improvements”](#improvements-1) * **Reporting** — Added new reporting capabilities. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Invoice handling** — Fixed an issue with invoice data management. --- # Release v2.14.x > Release notes for 4HSE v2.14 ## v2.14.0 — December 2021 [Section titled “v2.14.0 — December 2021”](#v2140--december-2021) ### New Features [Section titled “New Features”](#new-features) * **Context menu (kebab menu)** — A new context menu system (kebab icon) provides quick access to common actions directly from list rows, including opening details, navigating to related records, and performing bulk operations. * **History tracking** — A new history management system allows you to view and track changes over time for records. * **Delete confirmation** — A new delete confirmation dialog provides a clearer and safer deletion experience. * **Record disabling** — Records can now be disabled instead of deleted, preserving data for audit purposes. ### Improvements [Section titled “Improvements”](#improvements) * **Grid improvements** — Added reload capability and improved column display in grids. * **Address book grid** — Improved the address book grid with better column layout. * **Print system** — Restored and improved the print/export functionality. --- # Release v2.15.x > Release notes for 4HSE v2.15 ## v2.15.0 — January 2022 [Section titled “v2.15.0 — January 2022”](#v2150--january-2022) ### New Features [Section titled “New Features”](#new-features) * **Action list improvements** — Redesigned action list views with improved filtering and display capabilities. ### Improvements [Section titled “Improvements”](#improvements) * **View data refresh** — Improved the reliability and performance of scheduled view data updates. * **Form improvements** — Enhanced form behavior with better field handling. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Multiple fixes** — Fixed various issues with data display, migration handling, and form behavior. ## v2.15.1–v2.15.6 — February 2022 [Section titled “v2.15.1–v2.15.6 — February 2022”](#v2151v2156--february-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes addressing issues reported in production, including data display corrections and stability improvements. --- # Release v2.16.x > Release notes for 4HSE v2.16 ## v2.16.0 — February 2022 [Section titled “v2.16.0 — February 2022”](#v2160--february-2022) ### New Features [Section titled “New Features”](#new-features) * **Action actor management** — A new actor management system allows you to assign responsible persons and roles to actions, with dedicated forms and views. * **Update wizard** — A new update process guides users through important changes when upgrading to a new version. ### Improvements [Section titled “Improvements”](#improvements) * **Cache and view management** — Improved tools for rebuilding caches and computed views. * **Form and wizard improvements** — Enhanced form and wizard behavior with better navigation and validation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Various fixes** — Fixed multiple issues with image display, wizard behavior, and form validation. ## v2.16.1–v2.16.5 — March 2022 [Section titled “v2.16.1–v2.16.5 — March 2022”](#v2161v2165--march-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes addressing data display, form behavior, permission, and navigation issues. --- # Release v2.17.x > Release notes for 4HSE v2.17 ## v2.17.0 — March 2022 [Section titled “v2.17.0 — March 2022”](#v2170--march-2022) ### New Features [Section titled “New Features”](#new-features) * **Scheduler redesign** — A completely redesigned scheduler with calendar views, subscription management, and improved navigation. The scheduler is now available at both the office and person level. * **User impersonation** — Administrators can now switch to another user’s view for troubleshooting and support purposes. ### Improvements [Section titled “Improvements”](#improvements) * **Calendar management** — Improved calendar component with better date handling and read-only mode support. * **User identity performance** — Optimized user identity data handling for faster loading in large organizations. * **Permission checks** — Improved permission checking with support for array-based permission validation. * **Action session management** — Improved action session date forms and navigation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Project creation** — Fixed an issue that could prevent project creation in certain configurations. * **Calendar display** — Fixed read-only calendar display issues. * **Certificate tab** — Fixed a display issue in the certificate tab view. * **Various fixes** — Fixed multiple issues with scheduler filters, action sessions, and date handling. ## v2.17.1–v2.17.7 — May 2022 [Section titled “v2.17.1–v2.17.7 — May 2022”](#v2171v2177--may-2022) ### Improvements [Section titled “Improvements”](#improvements-1) * **Multi-language support** — Added French and Spanish language support with complete translations. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including scheduler issues, file synchronization improvements, translation corrections, and various stability fixes. --- # Release v2.18.x > Release notes for 4HSE v2.18 ## v2.18.0 — June 2022 [Section titled “v2.18.0 — June 2022”](#v2180--june-2022) ### New Features [Section titled “New Features”](#new-features) * **Notification configuration** — A new project-level notification configuration system allows you to customize which notifications are sent and to whom, with support for email templates and digest scheduling. * **Entity configuration** — A new entity configuration system allows administrators to customize the behavior and settings of different entity types per project. * **User permission generation** — Automatic permission generation for new users based on their role and project assignments. ### Improvements [Section titled “Improvements”](#improvements) * **Notification templates** — Improved email notification templates with better formatting and data display. * **Help system** — Added contextual help links to additional areas. * **Internationalization** — Improved translation handling across the application. * **Form improvements** — Enhanced form save behavior and data validation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Label positions** — Fixed label alignment issues in forms. * **Notification translations** — Fixed several notification translation issues. * **Various fixes** — Fixed multiple issues with permissions, form saving, and data display. ## v2.18.1 — June 2022 [Section titled “v2.18.1 — June 2022”](#v2181--june-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Multiple fixes** — Fixed several issues including translation corrections, form display, and navigation issues. --- # Release v2.19.x > Release notes for 4HSE v2.19 ## v2.19.0 — June 2022 [Section titled “v2.19.0 — June 2022”](#v2190--june-2022) ### New Features [Section titled “New Features”](#new-features) * **Organizational structure management** — A comprehensive organizational structure module allows you to define and manage organizational units, roles, and person assignments with a hierarchical tree view. This includes dedicated forms and grids for units, roles, and people within the organization. * **Project notification configuration** — Notification settings can now be configured at the project level, accessible directly from the project navigation tree. ### Improvements [Section titled “Improvements”](#improvements) * **Context menu enhancements** — Added context menu actions to more areas of the application. * **Grid behavior** — Improved dynamic grid behavior with better link handling and double-click navigation. * **Permission management** — Refined permission rules for the organizational structure module. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Organizational data** — Fixed an issue where root organizational units could have incorrect parent references. * **Various fixes** — Fixed multiple issues with grid display, form handling, permissions, and navigation. --- # Release v2.1.x > Release notes for 4HSE v2.1 ## v2.1.0 — March 2020 [Section titled “v2.1.0 — March 2020”](#v210--march-2020) ### New Features [Section titled “New Features”](#new-features) * **Single sign-on support** — The application now supports single sign-on authentication, allowing users to log in using their organization’s identity provider for a seamless and secure experience. * **Session and version control** — The application now checks for session validity and new versions, ensuring users are always on the latest release. ### Improvements [Section titled “Improvements”](#improvements) * **Incompatible screen redirect** — Users on unsupported screen sizes are now redirected to a friendly message page. ## v2.1.1 — March 2020 [Section titled “v2.1.1 — March 2020”](#v211--march-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Multiple fixes** — Fixed several issues including data display errors, form handling, and navigation corrections. ## v2.1.2 — March 2020 [Section titled “v2.1.2 — March 2020”](#v212--march-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **General fix** — Fixed an issue reported after the v2.1 release. --- # Release v2.20.x > Release notes for 4HSE v2.20 ## v2.20.0 — June 2022 [Section titled “v2.20.0 — June 2022”](#v2200--june-2022) ### New Features [Section titled “New Features”](#new-features) * **Whitelabel customization** — Partners can now fully customize the application branding, including logos, colors, and translations, for a personalized experience for their clients. ### Improvements [Section titled “Improvements”](#improvements) * **Partner management** — Added new fields and configuration options to the partner profile, including support contact information. * **Application services** — Improved how the application loads partner-specific settings and branding at startup. ## v2.20.1 — July 2022 [Section titled “v2.20.1 — July 2022”](#v2201--july-2022) ### Improvements [Section titled “Improvements”](#improvements-1) * **Person data** — Added a new field to the person record for more complete employee profiles. * **Data backup** — Improved the backup management interface. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Country list** — Added a missing country entry to the country selection dropdown. * **Data caching** — Fixed an issue with local data caching that could cause stale data to be displayed. * **Login flow** — Fixed a minor issue in the login redirect process. --- # Release v2.21.x > Release notes for 4HSE v2.21 ## v2.21.0 — July 2022 [Section titled “v2.21.0 — July 2022”](#v2210--july-2022) ### New Features [Section titled “New Features”](#new-features) * **Person detail view** — A completely redesigned person detail view provides a more organized and comprehensive overview of employee information, including address book, action subscriptions, and employee associations. * **Person filter** — A new filtering system for the person list allows you to search and filter by multiple criteria, with a dedicated filter panel and quick filter buttons. * **Person grid improvements** — The person list now displays additional fields such as gender and project association for a more complete overview. * **Desktop icons** — New desktop icons are available for quick access to key sections of the application. ### Improvements [Section titled “Improvements”](#improvements) * **Person API** — The person API now supports more flexible data retrieval with additional view fields. * **Employee details** — Improved the display of employee-related information including history tracking. * **Grid dynamic behavior** — Improved the behavior of dynamic grids for a more consistent user experience. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Attribute tab** — Fixed a display issue in the custom attributes tab. * **Person data source** — Fixed an issue with the person data source that could return incorrect results. ## v2.21.1 — July 2022 [Section titled “v2.21.1 — July 2022”](#v2211--july-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Person detail** — Fixed several display and navigation issues in the person detail view. * **Action subscription** — Fixed a navigation issue in the person action subscription view. * **Window management** — Fixed an issue where windows could lose focus or display incorrectly in certain scenarios. --- # Release v2.22.x > Release notes for 4HSE v2.22 ## v2.22.0 — July 2022 [Section titled “v2.22.0 — July 2022”](#v2220--july-2022) ### New Features [Section titled “New Features”](#new-features) * **Notification digest** — A new notification digest system lets you configure how and when you receive notification summaries, with support for simple and advanced scheduling modes. * **Timezone-aware notifications** — Notifications are now delivered based on your timezone setting, ensuring you receive them at the right time regardless of your location. ### Improvements [Section titled “Improvements”](#improvements) * **Notification settings** — A new time picker interface makes it easier to configure when notifications are sent. * **Email notifications** — Improved the notification delivery system with better scheduling and timezone handling. * **Contextual help** — Added help links to the notification settings area. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Date handling** — Fixed an issue where notification dates could be inverted, causing incorrect scheduling. ## v2.22.1 — July 2022 [Section titled “v2.22.1 — July 2022”](#v2221--july-2022) ### Improvements [Section titled “Improvements”](#improvements-1) * **User invitation emails** — Invitation emails now include the user’s email address for better clarity. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Partner management** — Fixed a display issue in the partner management view. ## v2.22.2 — August 2022 [Section titled “v2.22.2 — August 2022”](#v2222--august-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **User data** — Fixed an issue with user data retrieval that could return incomplete results. * **Window focus** — Fixed an issue where application windows could behave unexpectedly when switching between views. --- # Release v2.23.x > Release notes for 4HSE v2.23 ## v2.23.0 — August 2022 [Section titled “v2.23.0 — August 2022”](#v2230--august-2022) ### New Features [Section titled “New Features”](#new-features) * **Incident management** — A new incident (event) management module allows you to record and track workplace incidents, including linking actions, resources, and people to each incident. Incidents can be managed from both the office and project level. * **Expiring items configuration** — A new configuration form lets you manage expiration settings for action subscriptions within a project. * **Action form improvements** — Action forms now support additional fields for more detailed action tracking. ### Improvements [Section titled “Improvements”](#improvements) * **Incident resources** — You can now link equipment, substances, work environments, and materials to incidents for complete traceability. * **Incident actions** — Actions can now be directly associated with incidents, with dedicated forms and grid views. * **Scheduler filter** — Added new filter options to the scheduler for more precise search results. * **Computed view updates** — Improved the accuracy and reliability of computed action and subscription data. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Incident data** — Fixed an issue with incident data naming that could cause confusion. ## v2.23.1 — August 2022 [Section titled “v2.23.1 — August 2022”](#v2231--august-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Various fixes** — Fixed several issues reported after the initial incident management release, including navigation and display corrections. ## v2.23.3 — August 2022 [Section titled “v2.23.3 — August 2022”](#v2233--august-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **General fix** — Fixed an issue that could cause errors in specific scenarios. ## v2.23.4 — September 2022 [Section titled “v2.23.4 — September 2022”](#v2234--september-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Translation corrections** — Fixed several translation issues across the application. * **Form validation** — Fixed multiple form validation and display issues. * **Permission cache** — Improved the reliability of the permission cache system. ## v2.23.5 — September 2022 [Section titled “v2.23.5 — September 2022”](#v2235--september-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Data display** — Fixed an issue where certain data could be displayed incorrectly in list views. ## v2.23.6 — September 2022 [Section titled “v2.23.6 — September 2022”](#v2236--september-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-5) * **General stability** — Fixed issues that could cause errors in specific workflows. --- # Release v2.24.x > Release notes for 4HSE v2.24 ## v2.24.0 — October 2022 [Section titled “v2.24.0 — October 2022”](#v2240--october-2022) ### New Features [Section titled “New Features”](#new-features) * **Form designer** — A completely new visual form designer lets you create custom forms with a drag-and-drop interface, including support for text fields, checkboxes, radio buttons, date pickers, color pickers, rich text editors, and more. * **Widget system** — A new widget system provides building blocks for custom forms, with support for layout containers, tabs, and flexible positioning. * **Form preview and playback** — You can now preview and test your custom forms before publishing them, with full support for read-only and disabled states. * **Multi-language support** — French and Spanish languages are now available in addition to English and Italian. ### Improvements [Section titled “Improvements”](#improvements) * **Designer palette** — The form designer includes a palette of available widgets that can be dragged onto the canvas. * **Widget properties** — Each widget supports configurable properties including dimensions, colors, background images, and responsive layouts. * **Snippet support** — Reusable form snippets can be created and inserted into forms for faster design. * **Certificate permissions** — Improved certificate manager access control rules. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Designer stability** — Fixed several issues with the form designer including drag-and-drop behavior, tab layout handling, and property editing. * **Form playback** — Fixed issues with form rendering when viewing completed forms. * **Attachment handling** — Fixed an issue with saving attachments from within custom forms. ## v2.24.1 — October 2022 [Section titled “v2.24.1 — October 2022”](#v2241--october-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Various fixes** — Fixed multiple issues reported after the form designer release, including data display, permission, and navigation corrections. ## v2.24.2 — November 2022 [Section titled “v2.24.2 — November 2022”](#v2242--november-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Data retrieval** — Fixed an issue that could cause incorrect data to be returned in certain views. --- # Release v2.25.x > Release notes for 4HSE v2.25 ## v2.25.0 — December 2022 [Section titled “v2.25.0 — December 2022”](#v2250--december-2022) ### New Features [Section titled “New Features”](#new-features) * **Help system** — A new integrated help system provides contextual assistance throughout the application, with a dedicated help panel that shows relevant documentation based on the current view. * **Billing and subscription management** — A new subscription and billing management system allows administrators to manage plans, view invoices, and handle subscription changes directly from the application. * **Academy integration** — Quick access to the training academy is now available from the application toolbar. ### Improvements [Section titled “Improvements”](#improvements) * **Inactive window styling** — Inactive windows now have a distinct visual style to help you identify the active window more easily. * **View manager improvements** — Improved the reliability and performance of computed data views for actions and subscriptions. * **Entity information API** — A new API endpoint provides entity metadata and configuration information. * **Help grid decorator** — Lists now support integrated help links for quick access to relevant documentation. * **Certificate detail** — Improved the certificate detail view with additional information. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Action subscription detail form** — Fixed display issues in the action subscription detail form. * **Certificate action suggestions** — Fixed an issue with certificate action suggestion display. * **Translation corrections** — Fixed a translation issue in the application. * **Data transfer** — Fixed an issue with data transfer handling. ## v2.25.1 — December 2022 [Section titled “v2.25.1 — December 2022”](#v2251--december-2022) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Multiple fixes** — Fixed several issues including person grid display, certificate action display, data filtering, and navigation corrections. ## v2.25.2 — January 2023 [Section titled “v2.25.2 — January 2023”](#v2252--january-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Data display** — Fixed a display issue in a specific data view. ## v2.25.3 — January 2023 [Section titled “v2.25.3 — January 2023”](#v2253--january-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **General fix** — Fixed an issue that could cause errors in certain scenarios. ## v2.25.4 — January 2023 [Section titled “v2.25.4 — January 2023”](#v2254--january-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Form display** — Fixed two display issues in forms. ## v2.25.5 — February 2023 [Section titled “v2.25.5 — February 2023”](#v2255--february-2023) ### Improvements [Section titled “Improvements”](#improvements-1) * **Document references** — Cleaned up outdated document references in the application. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-5) * **Data retrieval** — Fixed an issue with data retrieval that could return incorrect results. * **General stability** — Fixed several stability issues. ## v2.25.6 — February 2023 [Section titled “v2.25.6 — February 2023”](#v2256--february-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-6) * **General fix** — Fixed an issue reported in production. ## v2.25.8 — March 2023 [Section titled “v2.25.8 — March 2023”](#v2258--march-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-7) * **Multiple fixes** — Fixed several issues including data display and form validation corrections. --- # Release v2.26.x > Release notes for 4HSE v2.26 ## v2.26.0 — March 2023 [Section titled “v2.26.0 — March 2023”](#v2260--march-2023) ### Improvements [Section titled “Improvements”](#improvements) * **Office person management** — Improved the office person management view with better navigation and workplace assignment capabilities. * **Person data** — Added additional data fields to the person view for more comprehensive employee profiles. * **Person API** — Improved the person data API with more flexible data retrieval. * **Material (PPE) display** — Improved the material list display with additional fields. * **Data sanitization** — Improved data sanitization across the application to ensure consistent and clean data display. * **Notification scheduling** — Improved the reliability of scheduled notification processing. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Dictionary data** — Fixed an issue with dictionary data retrieval. * **Person office view** — Fixed a data display issue in the person-office association view. ## v2.26.1 — March 2023 [Section titled “v2.26.1 — March 2023”](#v2261--march-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Person office data** — Fixed an issue with person-office data display that could show incomplete information. * **Data sanitization** — Fixed a data processing issue. * **Dictionary data** — Fixed an additional dictionary data retrieval issue. ## v2.26.2 — April 2023 [Section titled “v2.26.2 — April 2023”](#v2262--april-2023) ### Improvements [Section titled “Improvements”](#improvements-1) * **Person grid** — Enhanced the person list with improved column display and filtering capabilities. * **Certificate display** — Improved the certificate grid with additional columns and sorting options. * **Person detail navigation** — Added certificate section to the person detail navigation for employees and external contacts. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Certificate action display** — Fixed a display issue in the certificate action grid. * **Action session data** — Fixed an issue with action session data views. ## v2.26.3 — May 2023 [Section titled “v2.26.3 — May 2023”](#v2263--may-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Certificate view updates** — Fixed an issue with certificate view refresh timing. * **Period updates** — Fixed an issue with scheduled period update processing. * **Entity attachments** — Fixed an issue with entity attachment handling. * **Scheduler calendar** — Fixed a display issue in the scheduler calendar view. * **Attachment folder contents** — Fixed a display issue in the attachment folder content list. --- # Release v2.27.x > Release notes for 4HSE v2.27 ## v2.27.0 — May 2023 [Section titled “v2.27.0 — May 2023”](#v2270--may-2023) ### New Features [Section titled “New Features”](#new-features) * **Incident resource management** — Incidents now support linking to multiple resource types including actions, people, and equipment with dedicated management views. * **Partner archive configuration** — Partner archive settings can now be configured per installation for more flexible deployment. ### Improvements [Section titled “Improvements”](#improvements) * **Project view updates** — The project view now automatically updates when the associated partner changes, ensuring data consistency. * **Error handling** — Improved error handling and reporting across the application. * **Person event permissions** — Refined access control for person-related incident data. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Incident data** — Fixed an issue with incident data retrieval that could return incomplete results. ## v2.27.1 — May 2023 [Section titled “v2.27.1 — May 2023”](#v2271--may-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Multiple fixes** — Fixed several issues including data display and navigation corrections. ## v2.27.2 — June 2023 [Section titled “v2.27.2 — June 2023”](#v2272--june-2023) ### New Features [Section titled “New Features”](#new-features-1) * **Notification templates** — A new notification template system allows customizing the content and layout of email notifications with support for dynamic data. * **Custom form integration** — Custom forms created with the form designer can now be integrated into notification workflows. ### Improvements [Section titled “Improvements”](#improvements-1) * **Permission management** — Improved how permissions are checked and applied across the application. * **Error handling** — Improved error handling for background processes. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Data display** — Fixed a display issue that could affect certain list views. --- # Release v2.28.x > Release notes for 4HSE v2.28 ## v2.28.0 — June 2023 [Section titled “v2.28.0 — June 2023”](#v2280--june-2023) ### New Features [Section titled “New Features”](#new-features) * **Workplace management** — A new workplace management module allows you to define and manage workplaces with person and supplier associations, providing a more complete picture of who works where. * **Risk assessment views** — New computed views for risks and demands provide automatically updated data for risk assessments, with support for hierarchical parent structures. * **Demand resource management** — Demands now support linking to resources such as equipment, substances, and work environments. * **Computed data views** — New automatically updated views for actions, demands, risks, and certificates ensure data is always current without manual refresh. * **Project backup** — Enhanced the project backup system with improved handling of complex data structures. ### Improvements [Section titled “Improvements”](#improvements) * **Data hierarchy** — Improved how parent-child relationships are tracked across the application, providing more accurate data in hierarchical views. * **Person and scheduler filters** — Improved filtering options in person and scheduler views for more precise results. * **Work group management** — Enhanced work group forms with better text display and color options. * **Column labels** — Improved column labels across various grids for better clarity. * **Help context** — Updated contextual help links across the application. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Risk evaluation form** — Fixed an issue in the risk evaluation form. * **Danger copy** — Fixed an issue when copying danger records. * **Demand action tab** — Fixed a display issue in the demand action tab. * **Attachment metadata** — Fixed an issue with attachment metadata parent tracking. * **Workplace data sources** — Fixed data source configuration for workplace person and supplier views. * **Work group constructor** — Fixed an issue in the work group creation process. * **Certificate resource type** — Fixed an incorrect resource type in certificate views. * **Action subscription resources** — Fixed a display issue with action subscription resources. ## v2.28.1 — June 2023 [Section titled “v2.28.1 — June 2023”](#v2281--june-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Multiple fixes** — Fixed several issues including data display and navigation corrections. ## v2.28.2 — June 2023 [Section titled “v2.28.2 — June 2023”](#v2282--june-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Data display** — Fixed a display issue in a specific data view. ## v2.28.3 — July 2023 [Section titled “v2.28.3 — July 2023”](#v2283--july-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **General fix** — Fixed an issue that could cause errors in certain scenarios. ## v2.28.4 — July 2023 [Section titled “v2.28.4 — July 2023”](#v2284--july-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **General fix** — Fixed an additional issue reported in production. --- # Release v2.29.x > Release notes for 4HSE v2.29 ## v2.29.0 — July 2023 [Section titled “v2.29.0 — July 2023”](#v2290--july-2023) ### New Features [Section titled “New Features”](#new-features) * **Hierarchical group management** — A new hierarchical group (hgroup) system allows you to organize people and resources into nested groups within offices, providing a more flexible organizational structure. * **Office copy with groups** — The office copy feature now includes hierarchical group data, ensuring a complete copy of the organizational structure. * **Subscriber type management** — New subscriber type tracking provides more detailed information about subscription participants. ### Improvements [Section titled “Improvements”](#improvements) * **Person and scheduler filters** — Further improved the filtering capabilities in person and scheduler views. * **Work group form** — Improved the work group form with better labeling and display. * **Demand creation wizard** — Improved the demand creation wizard resource selection. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Person filter** — Fixed several issues with the person filter that could return incorrect results. * **Work group labels** — Fixed label display issues in work group person and supplier views. * **New work group selector** — Fixed a filtering issue in the new work group selector. --- # Release v2.2.x > Release notes for 4HSE v2.2 ## v2.2.0 — March 2020 [Section titled “v2.2.0 — March 2020”](#v220--march-2020) ### New Features [Section titled “New Features”](#new-features) * **Bulk certificate generation** — You can now generate certificates in bulk, significantly reducing the time needed to create certificates for multiple people or entities. * **Report cards** — A new report card feature allows you to generate summary reports for projects and people. ### Improvements [Section titled “Improvements”](#improvements) * **Grid data filtering** — Improved how data is filtered in list views for more accurate results. * **Material item selector** — Added a selection column to the material item selector for easier bulk operations. ## v2.2.2 — April 2020 [Section titled “v2.2.2 — April 2020”](#v222--april-2020) ### Improvements [Section titled “Improvements”](#improvements-1) * **Academy integration** — Added the academy icon for quick access to training resources. * **API help** — Added help documentation links to the API section. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Scheduler issues** — Fixed several issues with the scheduler display and behavior. * **Various fixes** — Fixed multiple issues including API versioning, translations, and data display corrections. ## v2.2.3 — April 2020 [Section titled “v2.2.3 — April 2020”](#v223--april-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **General fixes** — Fixed several issues reported in production. ## v2.2.4 — April 2020 [Section titled “v2.2.4 — April 2020”](#v224--april-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **General fix** — Fixed an issue reported in production. --- # Release v2.30.x > Release notes for 4HSE v2.30 ## v2.30.0 — August 2023 [Section titled “v2.30.0 — August 2023”](#v2300--august-2023) ### New Features [Section titled “New Features”](#new-features) * **Person transfer wizard** — You can now transfer people between offices with a step-by-step wizard that handles role assignments, equipment, substances, work environments, and other entity associations automatically. * **Risk assessment document templates** — New templates are available for generating risk assessment documents (DVR) with improved formatting for job roles. ### Improvements [Section titled “Improvements”](#improvements) * **Person creation workflow** — The person creation process now tracks change history and validates office assignments more thoroughly. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Person form validation** — Fixed an issue where the person form did not correctly verify office assignments before saving. ## v2.30.1 — August 2023 [Section titled “v2.30.1 — August 2023”](#v2301--august-2023) ### Improvements [Section titled “Improvements”](#improvements-1) * **Payment and billing details** — Improved the display and management of customer payment information within projects. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Root-level permissions** — Fixed a missing permission configuration that could prevent certain administrative operations. * **Person creation** — Fixed an issue in the person creation workflow that could cause errors under specific conditions. ## v2.30.2 — August 2023 [Section titled “v2.30.2 — August 2023”](#v2302--august-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Notification delivery** — Fixed an issue where some notifications were not being sent correctly. * **Payment details display** — Fixed a display issue in the payment information section. ## v2.30.3 — September 2023 [Section titled “v2.30.3 — September 2023”](#v2303--september-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Person API** — Fixed an issue with the person data retrieval that could return incorrect results in certain scenarios. * **Work group configuration** — Fixed an incorrect setting that could affect work group behavior. * **Risk assessment templates** — Fixed a formatting issue in the DVR job roles template. --- # Release v2.31.x > Release notes for 4HSE v2.31 ## v2.31.0 — September 2023 [Section titled “v2.31.0 — September 2023”](#v2310--september-2023) ### New Features [Section titled “New Features”](#new-features) * **Permission management** — A completely new permission system allows you to view and manage user permissions directly within the application, with dedicated grid and form views for assigning and reviewing access levels. * **Compact permission view** — A new streamlined view lets you quickly see and edit permissions for people across offices and projects, with office-level detail forms. * **Related user management** — You can now link application users to employee records with a guided wizard that supports level selection and execution steps. * **Project permission management** — Permissions can now be configured directly at the project level, making it easier to control who has access to specific projects. * **Partner and supplier permissions** — Partners and suppliers now have dedicated permission management, replacing the previous user-based approach with a more streamlined workflow. ### Improvements [Section titled “Improvements”](#improvements) * **Person display in permissions** — The person’s name and user status are now shown in permission detail views for better clarity. * **Permission icons in taskbar** — Permission entries now display icons and titles in the navigation taskbar. * **Related user notes** — You can now add notes when linking users to employee records. * **Search improvements** — Text search in lists has been improved to return more accurate results. * **User input widgets** — New specialized input fields for selecting users and entities, with improved autocomplete and label display. * **Status input** — A new status selector widget provides a more intuitive way to set and display record statuses across the application. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Project tree navigation** — Fixed an issue where the project navigation tree displayed incorrect items. * **Slow query performance** — Fixed a database query performance issue that could cause slowdowns when loading access control data. * **Wizard labels** — Fixed misaligned labels in the person transfer wizard. * **Translation errors** — Fixed several translation issues in the permission management interface. * **Delete operations** — Fixed an issue where delete operations on permissions could fail silently. * **Person data filtering** — Fixed incorrect data filtering when viewing person records across different offices. ## v2.31.1 — September 2023 [Section titled “v2.31.1 — September 2023”](#v2311--september-2023) ### Improvements [Section titled “Improvements”](#improvements-1) * **Person import with user linking** — Importing people now supports automatically linking to existing application users. * **Contextual help** — Added contextual help links to additional sections of the application. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Permission rebuild** — Fixed an issue where permission recalculation could fail for certain office and supplier associations. * **Office tree display** — Fixed a navigation issue in the office tree view. * **Subscription management** — Fixed an issue with subscription plan handling that could cause errors during plan changes. * **Organizational unit display** — Fixed an incorrect display in the organizational unit list. * **Permission recalculation** — Fixed a scenario where permission data was not correctly refreshed after changes. ## v2.31.2 — October 2023 [Section titled “v2.31.2 — October 2023”](#v2312--october-2023) ### Improvements [Section titled “Improvements”](#improvements-2) * **Onboarding wizard** — Users arriving from the website now see a guided setup wizard to help them get started. * **Performance improvements** — Significant performance optimizations when loading and computing permission data, resulting in faster page loads. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Wizard read-only mode** — Fixed an issue where the move wizard incorrectly displayed fields as read-only. * **User creation language** — Fixed an issue where the language setting was not correctly applied when creating new users. * **Empty fields display** — Fixed a display issue where some fields appeared empty when they should have shown data. * **Supplier form** — Fixed a form validation issue in the supplier detail view. ## v2.31.3 — October 2023 [Section titled “v2.31.3 — October 2023”](#v2313--october-2023) ### Improvements [Section titled “Improvements”](#improvements-3) * **Partner admin role** — Partner administrators now also have manager-level access, providing them with more complete control over their organization’s data. * **Performance optimization** — Improved performance when loading user identity data, reducing load times for large organizations. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Person office display** — Fixed an issue with how person-office associations were displayed in certain views. * **Navigation menu** — Fixed a main menu display issue that could occur after session changes. * **Bulk delete** — Improved the bulk delete behavior for equipment, people, substances, and work environments, with better handling of permission checks. * **Permissions** — Fixed an issue where certain access control rules were overly permissive. * **Form validation** — Fixed a form submission issue that could occur in specific conditions. * **Backup configuration** — Fixed an issue with the backup settings interface. ## v2.31.4 — November 2023 [Section titled “v2.31.4 — November 2023”](#v2314--november-2023) ### Improvements [Section titled “Improvements”](#improvements-4) * **Report image embedding** — Images in exported reports are now embedded inline, improving compatibility with different PDF viewers and email clients. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Action session dates** — Fixed the date selection interface for action sessions to be more intuitive. * **Attachment folders** — Fixed a navigation issue in the attachment folder tree. * **Report styling** — Fixed a styling issue in exported reports that could affect the appearance of certain elements. * **Security headers** — Fixed a content security policy configuration issue. --- # Release v2.32.x > Release notes for 4HSE v2.32 ## v2.32.0 — November 2023 [Section titled “v2.32.0 — November 2023”](#v2320--november-2023) ### New Features [Section titled “New Features”](#new-features) * **Calendar improvements** — The calendar view now supports additional display modes and interactions, making it easier to navigate and manage scheduled activities. * **Background task processing** — A new task processing system enables asynchronous operations such as people synchronization, improving reliability and performance for large data operations. ### Improvements [Section titled “Improvements”](#improvements) * **Data copy improvements** — The project copy feature now handles more entity types correctly, including actions, demands, equipment, and attachments. * **Person filter and scheduler filter** — Improved filtering options in the person and scheduler views for more precise results. * **Reporting data sources** — Additional data sources are now available for use in custom reports, including office and project-level data. * **CSV import progress** — The CSV import wizard now shows a progress indicator during the import process. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Period-based queries** — Fixed an issue where period filters could return incorrect results for certain date ranges. * **Permission compact view** — Fixed a data issue in the compact permission view. * **Context navigation** — Fixed the contextual navigation to correctly display relevant sections. ## v2.32.1 — December 2023 [Section titled “v2.32.1 — December 2023”](#v2321--december-2023) ### Improvements [Section titled “Improvements”](#improvements-1) * **Certificate management** — Certificates now support action management directly from the certificate detail view, with improved grid and form interactions. * **Action subscription management** — Streamlined the action subscription workflow with fewer redundant steps and better navigation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Data visibility** — Fixed several issues where records were not visible to users who should have had access, particularly for suppliers, equipment, substances, and work environments. * **Subscription billing** — Fixed a billing asset loading issue. * **Person navigation** — Fixed navigation issues when moving between person-related views. * **Address book display** — Fixed a display issue in the address book grid. * **Work group display** — Fixed incorrect data shown in work group, person office, and employee grids. * **Scheduler navigation** — Fixed navigation issues in the scheduler subscription detail view. * **Project navigation** — Fixed an issue where project tree navigation could show incorrect sections. * **Attribute display** — Fixed attribute grid display in certain views. * **Permission form** — Fixed a permission form behavior issue when switching between contexts. ## v2.32.2 — December 2023 [Section titled “v2.32.2 — December 2023”](#v2322--december-2023) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Certificate permissions** — Fixed an issue where certificate permissions were not correctly evaluated, potentially preventing access to authorized certificates. ## v2.32.3 — December 2023 [Section titled “v2.32.3 — December 2023”](#v2323--december-2023) ### Improvements [Section titled “Improvements”](#improvements-2) * **Notification performance** — Improved the performance of the notification processing system to handle large volumes more efficiently. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Certificate tree navigation** — Fixed a missing item in the certificate navigation tree. * **Attribute set display** — Fixed an issue where custom attribute input fields could display incorrectly in certain configurations. ## v2.32.5 — January 2024 [Section titled “v2.32.5 — January 2024”](#v2325--january-2024) ### New Features [Section titled “New Features”](#new-features-1) * **Academy integration** — The application now supports links to the training academy platform. * **People synchronization** — A new people synchronization feature allows automatic synchronization of employee data with external systems, including permission management and error handling. ### Improvements [Section titled “Improvements”](#improvements-3) * **Certificate action forms** — Improved the certificate action form with additional fields and better validation. * **Action session forms** — Enhanced the action session subscription forms with more flexible input options. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Action session scheduling** — Fixed an issue in the action session scheduling for periodic and health-type actions. * **Data listing performance** — Fixed a performance issue when loading large data lists. * **Certificate documentation** — Fixed incorrect display of certificate-related information. ## v2.32.6 — February 2024 [Section titled “v2.32.6 — February 2024”](#v2326--february-2024) ### Improvements [Section titled “Improvements”](#improvements-4) * **Scheduler detail view** — The scheduler subscription detail view now shows more relevant information and handles date display more accurately. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-5) * **Certificate detail display** — Fixed incorrect data shown in the certificate detail view. * **Certificate form** — Fixed a form behavior issue when editing certificate records. * **Bulk certificate actions** — Fixed an issue where bulk certificate operations could fail for certain action types. * **Person API** — Fixed an issue with the person data retrieval that could return incomplete results. * **Work group entity display** — Fixed a data display issue in work group entity views. ## v2.32.7 — February 2024 [Section titled “v2.32.7 — February 2024”](#v2327--february-2024) ### Improvements [Section titled “Improvements”](#improvements-5) * **Subscription notes** — You can now add and view notes on subscription records. * **Subscription display** — Improved the subscription detail view with better data presentation for both project and partner subscriptions. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-6) * **People synchronization** — Fixed an issue where the people sync process could handle certain edge cases incorrectly. * **Person manager** — Fixed a navigation issue in the person management view. --- # Release v2.33.x > Release notes for 4HSE v2.33 ## v2.33.0 — March 2024 [Section titled “v2.33.0 — March 2024”](#v2330--march-2024) ### New Features [Section titled “New Features”](#new-features) * **Automatic view updates** — The system now automatically updates computed views (such as action subscriptions, risks, demands, and more) in real-time as underlying data changes, eliminating the need for manual refresh and ensuring data is always up to date. * **Background queue processing** — A new message queue system processes data updates in the background, improving application responsiveness during complex operations. * **Layout preferences** — You can now customize the layout of certain views, including choosing background images and display preferences that persist across sessions. * **Window position memory** — The application now remembers the size and position of windows between sessions for a more personalized workspace. ### Improvements [Section titled “Improvements”](#improvements) * **Person creation API** — The person creation process through the API is now more flexible, with relaxed requirements for the person identifier field. * **Scheduler subscription improvements** — The scheduler now provides better navigation between person, calendar, and subscription views. * **Hierarchy level computation** — Improved the accuracy of organizational hierarchy level calculations. * **Work environment data** — Fixed and improved the work environment data views to include all relevant fields. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Billing detail display** — Fixed an issue where billing detail attributes were saved but not displayed to the user after initial entry. * **Action subscription data** — Fixed several issues where action subscription computed data could show stale or incorrect values. * **Action session date data** — Fixed an incorrect data calculation in action session date views. * **Action form** — Fixed a form field issue in the periodic action form. ## v2.33.1 — March 2024 [Section titled “v2.33.1 — March 2024”](#v2331--march-2024) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Equipment view** — Fixed an issue where equipment data could display incorrectly in certain configurations. * **Calendar navigation** — Fixed calendar interaction issues that could occur when navigating between months. * **Attachment processing** — Fixed an issue with attachment metadata processing that could cause errors. * **People synchronization** — Fixed an issue with the people sync task execution. ## v2.33.2 — April 2024 [Section titled “v2.33.2 — April 2024”](#v2332--april-2024) ### New Features [Section titled “New Features”](#new-features-1) * **Certificate action management** — Extended certificate management with dedicated action handling, including automatic status updates and permission controls. ### Improvements [Section titled “Improvements”](#improvements-1) * **Scheduler filtering** — Improved the scheduler subscription filter for more accurate results. * **Session verification interval** — Optimized the frequency of session and version checks to reduce unnecessary network requests. * **Address book and organization** — Improved the address book functionality and organizational structure management. * **Unit of measure migration** — Units of measure data has been migrated to a more flexible format. * **Background task reliability** — Improved the reliability of background task processing to better handle edge cases. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Work group grid** — Fixed a display issue in the work group grid view. ## v2.33.3 — May 2024 [Section titled “v2.33.3 — May 2024”](#v2333--may-2024) ### Improvements [Section titled “Improvements”](#improvements-2) * **Attachment management** — Significantly improved the attachment and document management system with better folder organization, permission handling, and metadata extraction. * **Certificate permissions** — Refined certificate permission rules for more granular access control. * **Data serialization** — Improved how data is formatted and delivered to the application for better consistency. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Certificate deletion** — Fixed an issue where certificates could not be deleted under certain conditions. * **Folder navigation** — Fixed several issues with folder display and navigation in the office view. * **Partner view** — Fixed a data display issue in the partner view. * **Scheduler filter** — Fixed a filtering issue in the scheduler view. * **Attachment metadata** — Fixed an issue with attachment metadata processing and display. * **Action subscription status** — Fixed an issue where changing a certificate status from expiring to expired did not correctly update the associated action subscription status. * **Material list** — Fixed a display issue in the office material list. ## v2.33.4 — May 2024 [Section titled “v2.33.4 — May 2024”](#v2334--may-2024) ### Improvements [Section titled “Improvements”](#improvements-3) * **Area folder organization** — Improved the naming and organization of area-specific document folders. * **Attachment API** — Enhanced the attachment data retrieval with better formatting and more efficient data delivery. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Person office grid** — Fixed a display issue in the person-office association grid. ## v2.33.5 — May 2024 [Section titled “v2.33.5 — May 2024”](#v2335--may-2024) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-5) * **Person navigation** — Fixed a navigation issue in the person detail tree view. * **Entity attachment permissions** — Fixed a permission issue that could prevent access to certain attachments. * **DVR template** — Fixed an issue with risk assessment document (DVR) template generation that could produce incorrect output. * **Workplace entity view** — Fixed a data display issue in the workplace entity view. * **Report data sources** — Added new data sources for work group reporting in custom reports. ## v2.33.6 — May 2024 [Section titled “v2.33.6 — May 2024”](#v2336--may-2024) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-6) * **Work environment management** — Fixed a navigation and interaction issue in the office work environment management view. --- # Release v2.34.x > Release notes for 4HSE v2.34 ## v2.34.0 — July 2024 [Section titled “v2.34.0 — July 2024”](#v2340--july-2024) ### New Features [Section titled “New Features”](#new-features) * **New login page** — The login page has been redesigned with a fresh layout for a more modern and user-friendly sign-in experience. * **Incident reporting** — A new incident (event) management module is now available, allowing you to record, track, and manage workplace incidents with dedicated forms and views at the project level. Incidents support public-facing forms for external reporting. * **Entity documentation API** — A new API endpoint provides access to entity documentation and dependency information, making it easier to integrate with external systems. * **Authentication token management** — Improved the security of user authentication with better token handling and validation. ### Improvements [Section titled “Improvements”](#improvements) * **Event visibility controls** — Incident records now have visibility controls based on office-level user roles, ensuring that sensitive information is only accessible to authorized personnel. * **Incident data tracking** — Incidents now track creator information and support richer data fields including injury details and status management. * **People synchronization** — Improved error reporting and handling during the people synchronization process, including better deactivation handling. * **User locale** — The user’s language preference is now correctly applied across all areas of the application. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Logout redirect** — Fixed an issue where users were not correctly redirected after logging out. * **Authentication validation** — Fixed an issue where empty authentication tokens could cause errors. * **Data type handling** — Fixed a data type issue that could cause incorrect display of active/inactive status in history views. * **Button styling** — Fixed a text color issue on certain buttons. * **Material form** — Fixed a form configuration issue in the material (PPE) detail view. * **Action subscription data** — Fixed an issue where action subscription computed data could be incomplete. * **Certificate action triggers** — Fixed a missing trigger that could prevent automatic updates when certificate actions changed. * **Permissions** — Fixed an incorrect access control rule that could affect API access. * **Danger form** — Fixed an issue in the danger detail form that could prevent proper data entry. * **Attachment cleanup** — Fixed a minor issue with attachment metadata cleanup when deleting entity attachments. ## v2.34.1 — July 2024 [Section titled “v2.34.1 — July 2024”](#v2341--july-2024) ### Improvements [Section titled “Improvements”](#improvements-1) * **Small screen warning** — Users accessing the application on screens that are too small now see an improved warning message explaining the minimum screen requirements. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Billing webhook** — Fixed an issue with the billing webhook processing that could cause errors. --- # Release v2.35.x > Release notes for 4HSE v2.35 ## v2.35.0 — July 2024 [Section titled “v2.35.0 — July 2024”](#v2350--july-2024) ### New Features [Section titled “New Features”](#new-features) * **Automatic incident cleanup** — Incidents that are no longer needed are now automatically cleaned up by the system on a scheduled basis, reducing manual maintenance. * **Bulk delete improvements** — The bulk delete functionality has been completely reworked with a new, more reliable approach that provides better feedback and handles permissions correctly. ### Improvements [Section titled “Improvements”](#improvements) * **Incident management** — Improved the incident (event) module with better attachment handling, entity assignment, person and resource management, and permission controls. * **Office incident visibility** — Incident records in the office view now have improved navigation and access controls. * **Material (PPE) selection** — Added a new material selector in the office view for easier assignment of personal protective equipment. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Period filter** — Fixed an issue where the period filter could produce incorrect results in certain views. * **Permission display** — Fixed an incorrect permission display in the compact permission grid. ## v2.35.1 — September 2024 [Section titled “v2.35.1 — September 2024”](#v2351--september-2024) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Entity attachments** — Fixed an issue where entity attachment grids could display incorrectly after certain operations. ## v2.35.2 — September 2024 [Section titled “v2.35.2 — September 2024”](#v2352--september-2024) ### Improvements [Section titled “Improvements”](#improvements-1) * **Certificate form** — Enhanced the certificate form with additional fields and improved validation for more complete certificate data entry. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Support page** — Fixed a display issue on the project support page. * **Attachment management** — Fixed an issue with attachment handling that could cause errors in certain scenarios. * **Person form** — Fixed a missing field in the person detail form. * **Permissions** — Fixed an incorrect access control configuration that could affect certain operations. --- # Release v2.36.x > Release notes for 4HSE v2.36 ## v2.36.0 — September 2024 [Section titled “v2.36.0 — September 2024”](#v2360--september-2024) ### Improvements [Section titled “Improvements”](#improvements) * **Contextual help in activity log** — Help links are now available in the activity log list and detail views, making it easier to find relevant documentation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Certificate management** — Fixed an issue that could prevent certificate features from working correctly. * **Static asset caching** — Fixed a problem where outdated versions of the application could be served from the browser cache after an update. --- # Release v2.37.x > Release notes for 4HSE v2.37 ## v2.37.0 — November 2024 [Section titled “v2.37.0 — November 2024”](#v2370--november-2024) ### New Features [Section titled “New Features”](#new-features) * **Project dashboard** — A new dashboard is now available within each project, providing an at-a-glance overview of key safety metrics including incident trends, certificate statuses, action subscription progress, and upcoming deadlines. * **Office dashboard** — Offices now have a dedicated dashboard summarizing recent activity logs, safety statistics, and operational status for the selected office. * **Incident trend chart** — A new line chart visualizes incident trends over time, with support for year-over-year comparison, filtering by category and status, and tracking of injury days. * **Certificate status chart** — A new bar chart displays the distribution of certificate statuses (valid, expiring, expired), available in both project and person dashboards. * **Incident and sickness day counters** — New summary widgets display the total number of incidents and cumulative sickness days, giving a quick snapshot of key safety indicators. * **Action subscription overview widgets** — New widgets show the status distribution of action subscriptions as a doughnut chart, a detailed list of subscriptions with direct links, and a counter for subscriptions approaching their deadline. ### Improvements [Section titled “Improvements”](#improvements) * **Dashboard filtering** — Dashboard charts and widgets now support filtering by time period, allowing you to focus on the data that matters most. * **Label alignment in forms** — Form field labels can now be aligned more flexibly, improving readability in custom configurations. * **Activity log list in dashboards** — The latest activity log entries are now displayed directly in office and project dashboards, with improved formatting and data handling. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Certificate permissions** — Fixed an issue where certificate permissions were not correctly applied when split across different roles. * **Office incident data** — Fixed a data retrieval issue that could cause incorrect results when viewing incidents at the office level. * **Scheduler interval selection** — Fixed a problem where the interval filter in the scheduler was not working as expected. * **Action subscription navigation** — Fixed broken links when navigating from dashboard widgets to the scheduler or to work group details. * **Dashboard chart labels** — Fixed alignment and display issues with chart labels on the project dashboard. * **Suggestion system** — Fixed an issue that could cause errors in the autocomplete suggestion system under certain conditions. --- # Release v2.38.x > Release notes for 4HSE v2.38 ## v2.38.0 — November 2024 [Section titled “v2.38.0 — November 2024”](#v2380--november-2024) ### New Features [Section titled “New Features”](#new-features) * **Redesigned dashboards** — The project, office, and person dashboards have been reorganized with an improved layout. Obligation charts and lists are now displayed more prominently alongside activity logs, with better use of available space. * **Obligation expiring count on dashboards** — Dashboards now show a count of obligations that are about to expire, giving you a quick overview of upcoming deadlines. * **Obligation list on dashboards** — A new obligations list widget has been added to office and project dashboards, showing the current status of your obligations at a glance. ### Improvements [Section titled “Improvements”](#improvements) * **Period filtering on dashboard statistics** — Dashboard statistics now respect the selected time period filter, allowing you to view data for specific date ranges instead of only the current period. * **Activity log visibility based on permissions** — The activity log section on dashboards is now only visible to users who have the appropriate permissions, keeping the interface cleaner for other users. * **Activity log is now read-only** — The activity log can no longer be manually created, edited, or deleted, ensuring data integrity of the recorded operations. * **Updated application font** — The application now uses an updated font for improved readability across all screens. * **Event chart hides future months** — The events timeline chart no longer displays empty future months, providing a cleaner view of your data. * **Automatic cleanup of old data** — Completed tasks and duplicated view logs are now automatically removed after 30 days to keep your workspace clean and improve performance. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Person list mobile phone display** — Fixed an issue where mobile phone numbers were not displayed correctly in the person list. * **Form designer label alignment** — Fixed label alignment options not working correctly in the form designer. * **Activity log entity name** — Fixed incorrect entity names being shown in the activity log grid. * **Dashboard chart titles** — Fixed incorrect titles on doughnut charts across dashboards. ## v2.38.1 — December 2024 [Section titled “v2.38.1 — December 2024”](#v2381--december-2024) ### New Features [Section titled “New Features”](#new-features-1) * **Dashboard refresh button** — All dashboards now include a refresh button, allowing you to reload dashboard data without navigating away from the page. --- # Release v2.39.x > Release notes for 4HSE v2.39 ## v2.39.0 — January 2025 [Section titled “v2.39.0 — January 2025”](#v2390--january-2025) ### New Features [Section titled “New Features”](#new-features) * **Clickable icons in obligation lists** — Icons for activities, subscribers, and certificates in obligation lists now show a pointer cursor and are clickable, making it easier to navigate to related records. ### Improvements [Section titled “Improvements”](#improvements) * **Increased grid item limit** — Grids now support displaying up to 10,000 items in client mode, up from the previous 1,000 limit, improving the experience when working with large datasets. * **Task processing performance** — Background task processing has been optimized for faster execution. * **Updated icon set** — Various interface icons have been refreshed with a more modern and consistent appearance. * **Star icon display** — The star/favourite icon is now rendered with the correct filled and outline styles. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Entity configuration during project creation** — Fixed an issue where configuration keys were not correctly associated when creating a new project. * **User name and surname on project creation** — Fixed incorrect user name and surname being saved during the project creation wizard. * **Email notification recipients** — Fixed an issue where certain email addresses were excluded from notifications. ## v2.39.1 — January 2025 [Section titled “v2.39.1 — January 2025”](#v2391--january-2025) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Scheduler calendar error** — Fixed an error that could occur when opening the scheduler calendar for activities without subscriber or location data. * **Checkbox styling in selector tables** — Fixed the appearance of selection checkboxes in table rows to display correctly. * **User detail page error** — Fixed an error that could occur when opening the detail page of a user that no longer exists in the project. * **Employee type display in office people list** — Fixed the employee/external type label not showing correctly in the office people list. ## v2.39.2 — January 2025 [Section titled “v2.39.2 — January 2025”](#v2392--january-2025) ### New Features [Section titled “New Features”](#new-features-1) * **Rolling 12-month dashboard charts** — Dashboard charts for activities and events now display data for the last 12 months on a rolling basis, instead of only the current calendar year. Month labels also include the year for clarity. ### Improvements [Section titled “Improvements”](#improvements-1) * **Folder browser performance** — The folder selection dialog now loads folder contents more efficiently, especially for projects with many folders. * **File type icons** — File type icons (PDF, Word, Excel, images, etc.) are now displayed correctly in attachment lists. * **Permissions sorting in role management** — Fixed the sorting of permission weights in the role assignment views so that the highest permission is correctly identified. * **Activity log reliability** — Improved the reliability of activity logging to prevent errors when processing changes to activities and sessions. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Notification delivery** — Fixed an issue that could prevent notifications from being delivered to some recipients. * **Dashboard widget stability** — Fixed potential display issues on dashboards when multiple chart widgets were loaded simultaneously. ## v2.39.3 — January 2025 [Section titled “v2.39.3 — January 2025”](#v2393--january-2025) ### Improvements [Section titled “Improvements”](#improvements-2) * **Activity log descriptions** — Activity log entries now show more descriptive labels for sessions, session dates, subscriptions, demands, and risk demands, making it easier to identify what was changed. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **File attachment handling** — Fixed an error that could occur when processing files without a file extension. ## v2.39.4 — February 2025 [Section titled “v2.39.4 — February 2025”](#v2394--february-2025) ### Improvements [Section titled “Improvements”](#improvements-3) * **Obligation list filtering in person and office views** — The obligation list in person and office detail views now correctly filters results to show only the obligations relevant to that person or office. * **Folder creation dialog size** — The dialog for creating new folders in the document area has been resized for better usability. ## v2.39.5 — February 2025 [Section titled “v2.39.5 — February 2025”](#v2395--february-2025) ### Improvements [Section titled “Improvements”](#improvements-4) * **Locale-aware date formatting** — Dates throughout the application are now displayed according to your browser’s locale settings, ensuring a consistent and familiar date format. * **Updated form designer icons** — Icons in the form designer for buttons, checkboxes, radio buttons, columns, rows, and other elements have been updated with a more modern appearance. * **Event list column order** — The incident detail column in the event list has been repositioned for a more logical reading order. * **Notification digest date format** — The date picker in the notification digest test now uses your local date format. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Completed task cleanup** — Fixed the automatic cleanup of completed background tasks to only remove the intended task type, preventing accidental deletion of other task records. * **Security improvement in file management** — Fixed a potential security issue in the file management area. * **Activity subscription data processing** — Fixed an error that could occur when processing activity subscription changes. --- # Release v2.3.x > Release notes for 4HSE v2.3 ## v2.3.0 — April 2020 [Section titled “v2.3.0 — April 2020”](#v230--april-2020) ### New Features [Section titled “New Features”](#new-features) * **Period management** — A new period system allows you to track historical changes over time for people, offices, and other entities, with support for viewing data at specific points in time. * **Gantt-style visualization** — Time-based data can now be visualized in a timeline view for better planning and overview. * **Entity cache and labels** — Improved data caching and automatic label generation for better performance and display. * **Color gradients** — New color gradient support in data displays for visual differentiation. * **Error dialogs** — Improved error handling with clear error messages and dialogs. ### Improvements [Section titled “Improvements”](#improvements) * **Notification system** — Updated the notification system to work with the new period management feature. * **Data queries** — Improved query performance with support for period-based filtering and union queries. * **Help system** — Added English language help content. * **Scheduler** — Fixed and improved the office scheduler. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Performance** — Removed a feature that was causing performance issues. * **Period behavior** — Fixed several issues with period-based data queries. * **Data integrity** — Fixed issues with data counting and constraint handling. ## v2.3.1–v2.3.11 — August 2020 [Section titled “v2.3.1–v2.3.11 — August 2020”](#v231v2311--august-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including scheduler corrections, performance improvements, support page redirect, API documentation updates, and various stability fixes. --- # Release v2.40.x > Release notes for 4HSE v2.40 ## v2.40.0 — February 2025 [Section titled “v2.40.0 — February 2025”](#v2400--february-2025) ### New Features [Section titled “New Features”](#new-features) * **Project notification settings** — You can now configure email notifications separately for each project, including a dedicated settings interface and email testing. ### Improvements [Section titled “Improvements”](#improvements) * **Permission checks on subscriptions** — Improved access control verification when managing action subscriptions and sessions. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Timezone handling** — Fixed incorrect time display caused by a timezone conversion issue. * **Duplicate configuration entries** — Fixed an issue where duplicate configuration entries could appear. --- # Release v2.41.x > Release notes for 4HSE v2.41 ## v2.41.0 — April 2025 [Section titled “v2.41.0 — April 2025”](#v2410--april-2025) ### New Features [Section titled “New Features”](#new-features) * **Attendance register** — You can now view, fill in, and print attendance registers for training sessions directly from session dates. The register includes a header, participant list, and signature support. * **Bulk download as ZIP** — You can download entire attachment folders as a ZIP archive. The file is generated in the background and you receive an email notification when it is ready. * **Dashboard charts** — Statistical charts (bar, doughnut, and line) are now available on office, person, and project dashboards. * **Entity data storage** — A new storage system is available for saving configuration data associated with entities, used internally for features such as attendance register settings. ### Improvements [Section titled “Improvements”](#improvements) * **Session date context menu** — Session dates now have a context menu with quick actions including open, delete, and open attendance register. * **Refresh button in attendance register** — A dedicated button lets you regenerate the attendance register form without leaving the page. * **Task list performance** — The task list now loads faster by requesting only the data it needs. * **Activity log in project configuration** — A log of operations is now visible in the project configuration area. * **Larger default modal windows** — Modal windows now open at a larger default size for better readability. * **Improved charts** — Charts have been upgraded, enabling multiple chart instances on the same page. * **Rich text editor updated** — The rich text editor has been streamlined by removing unused features. * **Description fields support longer text** — Description fields across the application now support larger content. * **Updated icon set** — Several outdated icon references have been corrected. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed session date context menu** — The context menu on session dates now correctly disables options based on permissions and action type. * **Fixed code editor button state** — The code editor expand button is no longer incorrectly disabled in certain contexts. * **Fixed broken icons** — Resolved broken icon references in various parts of the interface. ## v2.41.1 — April 2025 [Section titled “v2.41.1 — April 2025”](#v2411--april-2025) ### Improvements [Section titled “Improvements”](#improvements-1) * **Improved attendance register printing** — The print function for attendance registers now works more reliably across browsers. * **Improved download confirmation dialog** — The ZIP download confirmation dialog now displays at a proper width for better readability. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed attachment folder display** — Resolved a visual issue with attachment popups where the title area could be cut off. * **Fixed project permission cleanup** — The project permission panel now correctly releases resources when closed. * **Fixed log operation configuration** — The log operation configuration panel now correctly cleans up when closed. * **Fixed attachment context menu** — Removed an inapplicable download option from the attachment folder context menu. * **Fixed task list performance** — The task list now retrieves only the data it needs, reducing load times. --- # Release v2.42.x > Release notes for 4HSE v2.42 ## v2.42.0 — May 2025 [Section titled “v2.42.0 — May 2025”](#v2420--may-2025) ### New Features [Section titled “New Features”](#new-features) * **Material items management** — You can now manage individual material items (inventory units) directly within an office, including creating, editing, and viewing item details such as quantity, serial number, and due date. * **Fast planning for training sessions** — A new planner allows you to quickly schedule training subscriptions by selecting existing sessions or creating new ones. * **Planned certificates chart** — Dashboards for offices, persons, and projects now include a chart showing planned certificate actions over time. * **Person historicize action** — You can now historicize a person record, archiving it while preserving its data for future reference. * **PPE available quantity on materials** — The materials list now displays the available quantity of PPE items, calculated from inventory minus assigned certificates. ### Improvements [Section titled “Improvements”](#improvements) * **PPE pre-selected when creating material items** — When creating a new material item from a PPE material, the PPE type is automatically pre-selected. * **Certificate quantity from subscriptions** — Certificates created from training session subscriptions now correctly set the PPE quantity to the value specified by the user, defaulting to 1. * **Default placeholder for subscription date** — The subscription form now shows a placeholder indicating the default date value. * **Guest set as default office permission** — New office permissions now default to “guest”, ensuring area-level permission choices work correctly. * **Improved file move permission check** — When moving attachments, folder selectability now also considers project-level modify permissions, not just manager-level access. * **Attachment path refresh on move** — Moving an attachment now correctly refreshes its office, project, and supplier information. * **Cascading cleanup on person and role deletion** — Deleting a person or an office role now automatically removes related references from actions, sessions, and subscriptions. * **Material items linked to certificates** — Certificates created from PPE subscriptions now track the originating material item for better traceability. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed PPE permission in office view** — The PPE actions tab in the office view now correctly checks the appropriate permission group. * **Fixed certificate permission resolution** — Resolved an issue where certificate permissions were not resolved correctly. * **Fixed material count in views** — The material view now correctly calculates item counts. * **Fixed material item grid filter** — Filters in the material item grid now work as expected. * **Fixed attachment creation in system folders** — Creating attachments in restricted system directories is now properly blocked. * **Fixed scheduler button toggle** — Toggle buttons in the scheduler now correctly reflect their active or inactive state. * **Fixed session date double-click** — Double-clicking a session date in the scheduler now opens the expected detail view. * **Fixed action historicize** — Resolved an issue that could prevent actions from being historicized correctly. * **Fixed demand action tab** — The demand action grid tab now loads correctly. ## v2.42.1 — June 2025 [Section titled “v2.42.1 — June 2025”](#v2421--june-2025) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed permission check on scheduler buttons** — The planner and certificate buttons in the scheduler now correctly verify user permissions before becoming available. --- # Release v2.43.x > Release notes for 4HSE v2.43 ## v2.43.0 — June 2025 [Section titled “v2.43.0 — June 2025”](#v2430--june-2025) ### Improvements [Section titled “Improvements”](#improvements) * **Docs link now opens in your language** — The documentation shortcut on the desktop now opens directly in your preferred language (Italian or English) instead of the default page. * **Academy renamed to Docs** — The desktop icon previously labelled “Academy” is now called “Docs” to better reflect its purpose. * **Removed contextual help button from toolbars** — The help button that appeared in grids, forms, calendars, and attachment panels has been removed to simplify the interface. ## v2.43.1 — June 2025 [Section titled “v2.43.1 — June 2025”](#v2431--june-2025) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed project deletion failures** — Resolved an issue that could prevent projects from being deleted correctly. * **Fixed schedule toolbar button states** — Toggle buttons in the schedule toolbar now correctly reflect their active/inactive state. --- # Release v2.44.x > Release notes for 4HSE v2.44 ## v2.44.0 — June 2025 [Section titled “v2.44.0 — June 2025”](#v2440--june-2025) ### New Features [Section titled “New Features”](#new-features) * **New sign-in system** — The platform now uses a modern identity provider for authentication, enabling more secure login, logout, and session management. * **Language selector on login** — You can now choose your preferred language directly from the login screen. * **Mobile app URL support** — The mobile application is now accessible via dedicated URL paths and can be configured per white-label. ### Improvements [Section titled “Improvements”](#improvements) * **User profile opens in the same tab** — Clicking on your profile now navigates within the current browser tab instead of opening a new one. * **Pending users activated on first login** — Users with a pending status are now automatically activated when they log in for the first time. * **Reference date option for certificate views** — Certificate view updates can now include a configurable reference date. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed documentation links** — Links to user manuals now point to the correct destination. ## v2.44.2 — July 2025 [Section titled “v2.44.2 — July 2025”](#v2442--july-2025) ### New Features [Section titled “New Features”](#new-features-1) * **Material items available via API** — Material item data is now available through the public API. * **Record history on delete** — Deleting certain records now automatically creates a historical snapshot before removal. ### Improvements [Section titled “Improvements”](#improvements-1) * **Only active projects shown in global views** — The global scheduler and people windows no longer display content from inactive projects. * **Faster startup** — The application no longer loads all projects at startup, improving initial load time. * **Already associated entities hidden in selection dialogs** — When adding entities to work groups or roles, items that are already associated are no longer shown in the selection list. * **Improved Person API** — The Person API endpoint has been updated with additional fields and documentation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed partner icon display** — Partner icons are now shown correctly. * **Prevented bookmarking inactive projects** — Inactive projects can no longer be bookmarked, avoiding confusion in the project list. ## v2.44.3 — July 2025 [Section titled “v2.44.3 — July 2025”](#v2443--july-2025) ### Improvements [Section titled “Improvements”](#improvements-2) * **Partner configuration form uses full width** — The partner support configuration form now spans the full width of the page for better readability. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Fixed registration confirmation emails** — Resolved an issue where user registration confirmation emails could fail to send. * **Fixed notification delivery for certain users** — Notifications are now correctly delivered regardless of user account variations. * **Fixed access error on units of measure** — Accessing the units of measure list no longer returns an error. ## v2.44.4 — July 2025 [Section titled “v2.44.4 — July 2025”](#v2444--july-2025) ### New Features [Section titled “New Features”](#new-features-2) * **Location field in maintenance orders** — The maintenance order detail form now includes a location field. ### Improvements [Section titled “Improvements”](#improvements-3) * **Available quantity shown in delivery form** — When creating a delivery, the available quantity of each material item is now visible in the selection list. * **Inactive project offices hidden in filters** — The person filter and scheduler filter no longer show offices belonging to inactive projects. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Fixed organizational unit navigation highlighting** — Rows in the organizational unit tree are now highlighted correctly. * **Fixed duplicate icon not showing** — The duplicate action icon is now displayed properly in grids. * **Fixed attribute description field** — The rich-text description field for attributes now works correctly. ## v2.44.5 — July 2025 [Section titled “v2.44.5 — July 2025”](#v2445--july-2025) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-4) * **Fixed CSV export formatting** — Exported CSV files now use proper formatting to prevent issues with special characters in field values. --- # Release v2.45.x > Release notes for 4HSE v2.45 ## v2.45.0 — August 2025 [Section titled “v2.45.0 — August 2025”](#v2450--august-2025) ### New Features [Section titled “New Features”](#new-features) * **Webhook management** — You can now configure, edit, and test webhooks directly from the application. A dedicated configuration section lets you define endpoints, select which events to listen to, and send test requests to verify your setup. * **In-app tips system** — Contextual tips now appear within the application to guide you through important changes, such as the new permissions model and the activity log relocation. * **Group-based permission management** — User permissions are now managed through groups. You can create groups, assign permissions to them, and add or remove members directly from the group manager. * **Add members to groups** — A new form allows you to search for and add existing users as members of a group. ### Improvements [Section titled “Improvements”](#improvements) * **Project admin menu hidden for managers** — The project administration menu is now only visible to admin users, reducing clutter for manager-role users. * **Milliseconds removed from task grid** — Date and time columns in the task grid no longer display milliseconds for a cleaner presentation. * **Group name translations displayed** — The group grid now shows translated group names based on your language preference. * **Permission button restricted to admins** — The permission button is now only enabled for admin users. * **Improved API documentation** — API specifications have been expanded for certificates, certificate actions, persons, action subscriptions, and members. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed toolbar button behaviour** — Resolved an issue where toolbar buttons could behave incorrectly in certain views. * **Fixed readonly field handling** — Corrected a problem where readonly fields were not rendered properly. * **Fixed permission checks for group operations** — Resolved permission errors when performing actions on groups. * **Fixed member creation and deletion** — Corrected issues that could cause failures when creating or removing project members. * **Fixed attachment operations** — Resolved errors related to attaching and deleting entity attachments. * **Fixed webhook form save** — Corrected an issue where event data was missing when saving a webhook configuration. ## v2.45.1 — September 2025 [Section titled “v2.45.1 — September 2025”](#v2451--september-2025) ### New Features [Section titled “New Features”](#new-features-1) * **Office template selection in project creation** — When creating a new project, you can now choose from predefined office templates (including locale-specific templates) or start with an empty structure. ### Improvements [Section titled “Improvements”](#improvements-1) * **Improved office copy process** — Copying offices between projects now handles data more reliably. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed attachment permissions** — Resolved an issue preventing correct access to entity attachments. * **Fixed period behaviour in certain records** — Corrected a problem where period-related data could fail on specific record types. ## v2.45.2 — September 2025 [Section titled “v2.45.2 — September 2025”](#v2452--september-2025) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Fixed attachment access for specialized users** — Users with module-specific roles (maintenance, courses, PPE, inspections, health) can now correctly view and manage attachments. --- # Release v2.46.x > Release notes for 4HSE v2.46 ## v2.46.0 — September 2025 [Section titled “v2.46.0 — September 2025”](#v2460--september-2025) ### New Features [Section titled “New Features”](#new-features) * **Checklist form details view** — You can now view and fill in checklist forms directly from within action subscriptions, including a detailed header showing action name, date, location, and subscriber. * **Fast checklist completion from the scheduler** — A new quick-access checklist form lets you complete checklists directly from the scheduler subscription view without navigating away. * **Splashscreen on application load** — A branded splashscreen is now displayed while the application loads, providing visual feedback during startup. * **French and Spanish example office templates** — New pre-built office templates are available in French and Spanish when creating a project. * **AI assistant** — A new AI-powered chat assistant is available, with session management and conversation history. * **Repeatable row input** — A new repeatable-row input allows you to manage dynamic lists of structured data within forms. ### Improvements [Section titled “Improvements”](#improvements) * **Country filter in copy and template wizards** — When copying entities or selecting templates, you can now filter by country to quickly find the right source. * **Filter by current office in copy wizards** — Copy wizards for actions, equipment, roles, substances, work environments, materials, and work groups now support filtering by the current office. * **Large file download support** — Downloading large files is now more reliable, preventing timeouts on big exports. * **Address book management improvements** — The address book now supports create and update operations with improved access control. * **Action entity support in checklists** — Checklist configurations now support the action entity type, enabling richer form setups. * **Subscription grid enhancements for action sessions** — The action session subscription grid now includes additional context and inline actions for better session management. * **Material and PPE grid improvements** — Material item and PPE managers now provide a more consistent grid experience with improved toolbar actions. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed chart quarter and period calculations** — Resolved issues where chart time slots could generate invalid quarter labels or assign incorrect years. * **Fixed record deletion errors** — Resolved an issue where deleting certain records could fail unexpectedly. --- # Release v2.47.x > Release notes for 4HSE v2.47 ## v2.47.0 — November 2025 [Section titled “v2.47.0 — November 2025”](#v2470--november-2025) ### New Features [Section titled “New Features”](#new-features) * **AI assistant** — A new AI-powered chat assistant is available from the taskbar. You can start conversations, review past sessions, and get contextual help directly within the application. * **Country field on projects** — Projects now include a country field (defaulting to Italy) so you can specify the country where each project is located. * **Project grid enhancements** — The project list now supports additional filters and columns, including partner information, for easier project management. ### Improvements [Section titled “Improvements”](#improvements) * **Form export with images** — Exporting forms now correctly includes images and produces more reliable output. * **Improved activity session forms** — The subscription forms for activity sessions (checks and inspections) have been reorganized and streamlined for a more consistent editing experience. * **Improved form field rendering** — The form viewer now handles additional field types and configurations more reliably, including better support for attachments and conditional fields. * **Simplified date selection in fast checklists** — Selecting dates when performing quick checklists is now more straightforward. * **Improved notification and registration flow** — Notification handling and user registration confirmation have been streamlined for greater reliability. * **Address book improvements** — The address book now returns all entries when no specific entity is selected, making it easier to browse contacts. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed checklist permissions** — Resolved an issue where certain checklist actions were not respecting user permissions correctly. * **Fixed confirmation dialog behavior** — The “remember my choice” confirmation dialog now works correctly in all scenarios. * **Fixed create certificate button** — The button to create a certificate in activity sessions now appears and functions as expected. * **Fixed scheduler display** — Resolved an issue that could cause the scheduler view to render incorrectly. * **Fixed AI assistant visibility** — The AI assistant icon in the taskbar now shows and hides correctly based on your account configuration. * **Fixed chat history** — Resolved an issue where previous AI chat messages were not loading properly. * **Fixed work group data retrieval** — Resolved issues with work group data that could cause errors in certain configurations. * **Fixed translation issues** — Corrected missing or incorrect translations in several areas of the interface. --- # Release v2.48.x > Release notes for 4HSE v2.48 ## v2.48.0 — January 2026 [Section titled “v2.48.0 — January 2026”](#v2480--january-2026) ### New Features [Section titled “New Features”](#new-features) * **Units management** — A new entity type for managing organizational units, with full support for tree navigation, info forms, address books, file storage, permissions, roles, and relations with offices, work groups, and suppliers. * **Workflow system** — Introduced workflows with configurable instances, events, transitions, and form-based actions. Workflows can be started from certificate action grids and include attachment management and approval processes. * **Approvals window** — A dedicated window for viewing and filtering approval requests across action subscriptions. * **Events grid** — New grid for browsing events within units, with proper permissions. * **Actor management** — New actor-based role system allowing entity-specific role assignments and filtering by actor role. ### Improvements [Section titled “Improvements”](#improvements) * **Certificate workflow integration** — The certificate “new” button now opens the workflow form when a workflow is configured, with attachment upload support and visibility of certificate attachments in workflow details. * **Suppliers global grid** — Delete and import buttons are hidden in the global suppliers grid to prevent unintended operations. * **Office resource selector** — The resource selector in offices now shows only suppliers related to the current office. * **Scheduler badge** — Clicking the scheduler badge now opens the workflow window directly. * **Workflow start feedback** — Improved feedback when starting a workflow instance. * **German templates** — Added German language project templates. * **Chart translations** — Dashboard charts are now fully translated. * **Approval request column** — The approval request column in action subscription grids is now hidden by default to reduce clutter. * **New subscriptions treated as expired** — Added support for treating newly created subscriptions as expired, useful for onboarding scenarios. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed certificate action permissions** — Fixed an issue where unit users could not access certificate actions correctly. * **Fixed notification handling** — Fixed notifications not being sent or displayed properly in certain workflow scenarios. * **Fixed checklist configuration** — Fixed checklist info text and configuration not loading correctly. * **Fixed address book display** — Fixed a rendering issue in the address book index view. * **Fixed export functionality** — Resolved an error that prevented data exports from completing. * **Fixed period queries** — Fixed incorrect results when filtering by period. * **Fixed statistic counter layout** — Fixed a display issue in statistic counters. * **Fixed supplier grid delete** — Fixed inconsistent delete behavior in the supplier grid. * **Fixed attachment file selector** — Fixed incorrect root directory shown in the attachment file selector. ## v2.48.1 — February 2026 [Section titled “v2.48.1 — February 2026”](#v2481--february-2026) ### Improvements [Section titled “Improvements”](#improvements-1) * **Permission caching** — Introduced caching for permission checks, improving page load performance on complex configurations. * **Improved session management** — Improved session refresh logic for more reliable authentication handling. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed office role deletion** — Fixed an issue where deleting an office role could leave orphaned related data. --- # Release v2.49.x > Release notes for 4HSE v2.49 ## v2.49.0 — February 2026 [Section titled “v2.49.0 — February 2026”](#v2490--february-2026) ### New Features [Section titled “New Features”](#new-features) * **Related forms** — You can now create, edit, and manage related forms directly from the action detail window. Related forms support multilingual templates, custom names, and configurable required/optional status. * **New form engine** — A redesigned form system powers the rendering, loading, saving, and drafting of forms, with support for attachment management and local draft saving. * **Action form executor** — Actions now include a dedicated forms tab where you can open and fill in related forms in a resizable window, with attachment upload support. * **Action session forms** — Form executors are now available for action sessions and session dates, allowing you to fill in forms at each level of the action hierarchy. * **Incident fields** — New fields have been added to the incident (event) form and grid, providing more detail when recording workplace incidents. * **Permission endpoint** — A new endpoint is available for retrieving entity-level permissions, supporting the updated permission model. ### Improvements [Section titled “Improvements”](#improvements) * **Attachment grid on session dates** — Session date detail now includes an attachment grid for managing related documents. * **Checklist activation date** — The checklist activation date is now set to match the certificate date for better traceability. * **Simplified attachment grid** — The attachment grid now shows only the file name, reducing visual clutter. * **Cleaner file import** — The upload progress indicator is now hidden during file import to avoid confusion. * **Improved subscription grid** — The action subscription grid has been redesigned for improved layout and column management. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed related form icons and tooltips** — Fixed incorrect icons and missing tooltips in the related forms interface. * **Fixed related form labels** — Fixed labels not displaying correctly in certain related form configurations. * **Fixed checklist form binding** — Fixed the checklist form incorrectly binding to the wrong subscription level. * **Fixed alert dialog styling** — Fixed the font in alert dialogs not matching the application theme. * **Fixed dialog error title** — Removed an incorrect title shown in error dialogs. * **Fixed form component registration** — Fixed an issue where certain form components failed to load correctly. * **Fixed required attribute in related forms** — Fixed the required attribute not being applied correctly in related form configuration. ## v2.49.1 — March 2026 [Section titled “v2.49.1 — March 2026”](#v2491--march-2026) ### New Features [Section titled “New Features”](#new-features-1) * **Secure attachment links** — You can now generate short-lived, one-time-use secure links for accessing attachments without requiring an active session. ### Improvements [Section titled “Improvements”](#improvements-1) * **Designer typography** — Improved the typography options in the form designer with additional property support. ## v2.49.2 — March 2026 [Section titled “v2.49.2 — March 2026”](#v2492--march-2026) ### Improvements [Section titled “Improvements”](#improvements-2) * **Certificate release date** — When creating a certificate, the release date now defaults to today and the expiration date is automatically calculated when a validity period is configured. * **Improved error handling** — Improved resilience when processing user-related operations. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed form attachment saving** — Fixed an issue where attachments in form submissions could fail to save correctly. * **Fixed log operation grid** — Fixed a display issue in the log operation grid. --- # Release v2.4.x > Release notes for 4HSE v2.4 ## v2.4.0 — September 2020 [Section titled “v2.4.0 — September 2020”](#v240--september-2020) ### New Features [Section titled “New Features”](#new-features) * **Document management system** — A completely new document and attachment management system with folder navigation, drag-and-drop file uploads, file preview, search, and metadata tracking. Documents are now organized in a hierarchical folder structure with support for project, office, and supplier contexts. * **Document migration wizard** — A guided wizard helps you migrate existing documents to the new management system. * **Certificate enhancements** — Certificates now support procedure names and can be associated with offices, work phases, and risk sources. * **Risk demand navigation** — You can now navigate directly from risk demands to the associated actions. * **Project data fields** — Additional data fields are now available on project records. * **Wizard improvements** — Improved wizard navigation with back-step support and better validation dialogs. ### Improvements [Section titled “Improvements”](#improvements) * **File handling** — Support for file replacement, inline preview, and special characters in file paths. * **Attachment metadata** — Automatic metadata extraction and tracking for uploaded files. * **Backup system** — Improved backup handling with attachment export support. * **Partner management** — Partners now default to active status on creation. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Login button** — Fixed a display issue with the login button. * **File extension handling** — Fixed an issue with unrecognized file extensions. * **Entity permissions** — Fixed a permission issue with entity attachments. * **Various fixes** — Fixed multiple issues with window management, wizard navigation, and data display. ## v2.4.1–v2.4.5 — October 2020 [Section titled “v2.4.1–v2.4.5 — October 2020”](#v241v245--october-2020) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including attachment special character handling, folder creation for template projects, form display issues, report generation, and entity attachment display corrections. --- # Release v2.50.x > Release notes for 4HSE v2.50 ## v2.50.0 — March 2026 [Section titled “v2.50.0 — March 2026”](#v2500--march-2026) ### New Features [Section titled “New Features”](#new-features) * **Redesigned simplified form designer with new field types** — The simplified form designer has been completely rebuilt with support for multiple field types: text inputs, text areas, dropdown menus, radio buttons, checkbox groups, and signature fields. Each field can include an optional description or help text for additional guidance. * **New print template selector** — A redesigned template selector organizes templates by category: recently used, office/project templates, partner templates, and default templates. Includes search by name and country filtering. * **Create folders from the file save dialog** — You can now create new folders directly when saving attachments, without leaving the save dialog. * **Grid export options** — When exporting grid data, you can now choose between exporting only visible columns (preserving sort order) or all available columns. A progress indicator shows export status. * **Custom branded loading screen** — Whitelabel customers now see their own logo and brand colors on the application loading screen. * **Signature widget in the visual form designer** — The signature/drawing widget is now available in the visual form designer palette, allowing it to be used when building custom form layouts. ### Improvements [Section titled “Improvements”](#improvements) * **Improved form template management** — Form templates are now managed through the file system with searchable metadata, enabling better organization and faster template discovery. * **Updated form typography** — Forms created with the simplified designer now use an improved font for better readability. * **Faster category dropdowns** — Equipment and work environment category dropdowns now load instantly. * **Form name validation** — The form name field is now required when creating or editing related forms, preventing empty names. * **Project icon permissions** — File permissions for project icons are now correctly synchronized when the icon is changed. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Fixed procedure copy not including configured forms** — Copying a procedure now correctly replicates all associated modules and form configurations. * **Fixed “Create from template” dialog** — Corrected the window title and fixed an issue where search filters were not applied correctly on initial load. * **Fixed form state tracking** — Resolved an issue where forms could lose their state when the same form appeared in different contexts. * **Fixed a layout issue in the form designer** — Corrected a rendering error that could cause widget positioning to break in the form designer. ## v2.50.1 — April 2026 [Section titled “v2.50.1 — April 2026”](#v2501--april-2026) ### Improvements [Section titled “Improvements”](#improvements-1) * **Removed deprecated contextual help** — The old contextual help tips have been removed across the application in favor of the new documentation experience. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Fixed attachment sync removing linked files** — The attachment synchronization process no longer deletes existing attachments when the corresponding file is still present. * **Fixed duplicate country entries in selectors** — Removed duplicate country options that appeared in the print template selector and in the template source selection step. * **Fixed expired items still marked as valid** — Resolved an issue where a failure during the scheduled expiry check could halt the entire process, leaving some items expired but still flagged as valid. * **Fixed missing styles in notification popovers under whitelabel** — Feature announcement popovers now display with the correct background, colors, and typography when accessing the application through a whitelabel. * **Fixed an issue in the risk assessment module** — Corrected a regression affecting risk demand handling. ## v2.50.2 — April 2026 [Section titled “v2.50.2 — April 2026”](#v2502--april-2026) ### New Features [Section titled “New Features”](#new-features-1) * **New print template for work phases with equipment and PPE** — A new print template lists, for each person, their assigned work phases together with the related equipment and personal protective equipment. Available in all supported languages. ### Improvements [Section titled “Improvements”](#improvements-2) * **Warning column in the deadline list** — The deadline list now includes a dedicated warning column, making it easier to spot items approaching their expiration. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Fixed attachment search with body parameters** — Attachment searches now correctly accept filter parameters sent in the request body, matching the documented behavior. * **Hidden office field when creating a new safety role** — The office field no longer appears in the safety organization role creation form, where it was not applicable. * **Fixed attachment selector crash with restricted root paths** — The attachment selector no longer crashes when opened on a root path where the user only has access to deeper sub-folders. Intermediate folders are now shown as non-selectable placeholders, and all accessible roots are displayed instead of only the shallowest one. --- # Release v2.51.x > Release notes for 4HSE v2.51 ## v2.51.0 — April 2026 [Section titled “v2.51.0 — April 2026”](#v2510--april-2026) ### New Features [Section titled “New Features”](#new-features) * **Personal protective equipment delivery widget** — A new widget streamlines recording the delivery of a single piece of personal protective equipment, with automatic detection of the item, available stock lots, and a re-delivery flag for clearer record keeping. ### Improvements [Section titled “Improvements”](#improvements) * **Project creation restricted to admins from the desktop** — The project creation shortcut on the main desktop is now reserved for administrators. Standard users can still create projects from the multi-company panel. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Print templates now available on units** — Units can now be printed using the available templates, restoring missing options. * **Improved work phases print template** — Fixed issues affecting the recently introduced template that lists work phases with related equipment and personal protective equipment per person. ## v2.51.1 — May 2026 [Section titled “v2.51.1 — May 2026”](#v2511--may-2026) ### Improvements [Section titled “Improvements”](#improvements-1) * **Delivery details carried over to certificates** — Information entered when delivering a piece of personal protective equipment is now passed to the related certificate, keeping records consistent. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **DUVRI print errors fixed** — Resolved errors that prevented the DUVRI document from printing correctly. --- # Release v2.52.x > Release notes for 4HSE v2.52 ## v2.52.0 — May 2026 [Section titled “v2.52.0 — May 2026”](#v2520--may-2026) ### New Features [Section titled “New Features”](#new-features) * **Person profile photo** — You can now upload a profile photo on each person, with the picture shown next to the identity fields in the form and carried over to the person view. * **Person verification badge with QR code** — A new “Show verification QR” action is available on each person. The QR points to a public verification page that displays the person’s photo, identity details, employer, qualifications, and grouped certificates (training, health, PPE, procedures, checks) together with an overall preventive compliance status. * **Public verification page** — A dedicated public page renders the person badge from the QR link, with mobile-friendly layout, downloadable attachments, qualifications driven by the risk aggregator, and a clear message when the link has expired. ### Improvements [Section titled “Improvements”](#improvements) * **Refined person badge layout** — The badge document now shows hire date, contract type, qualification and role, a unique code with QR, and the generation date. Certificate attachments have been removed from the badge view, and the overall status is now expressed as “Preventive compliance: valid / not valid”. * **Longer-lived signed verification links** — Signed verification URLs can now be issued with a longer validity, making badge QR codes usable for extended periods without regeneration. * **Photo deletion confirmation** — Deleting a person photo now asks for explicit confirmation to prevent accidental removal. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Items of archived persons no longer appear as active** — Records with their own active period (for example a person’s office assignment) are now correctly hidden when their parent record has been archived. ## v2.52.1 — May 2026 [Section titled “v2.52.1 — May 2026”](#v2521--may-2026) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Print templates can be saved again from related grids** — Fixed an error that prevented saving print templates from grids showing related records. --- # Release v2.53.x > Release notes for 4HSE v2.53 ## v2.53.0 — May 2026 [Section titled “v2.53.0 — May 2026”](#v2530--may-2026) ### New Features [Section titled “New Features”](#new-features) * **PPE delivery wizard** — A new multi-step delivery form lets you record PPE handed out to one or more people in a single flow, with a paginated list of delivery rows, a summary step, and a notes field before saving. * **Course duration and session type** — When creating or editing a training course you can now choose whether the course is delivered as a single session or as base plus update sessions, and set the corresponding duration. Once a course has been created, its session type can no longer be changed. * **Session duration prefill** — Training session forms now include an editable duration field that defaults to the value configured on the parent course (single, base, or update), and hide the session type selector when the course only allows a single session. * **Training certificate duration and type** — Training certificates now record duration in minutes and session type. When the certificate is created from a session or a course, the duration is prefilled from the course configuration and remains editable; standalone certificates accept manual values. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Log grid search now resets correctly** — Clearing the search field and reloading the log grid now shows all records again, instead of keeping the previous search filter applied. * **Consistent action label in toolbar and menu** — The “Fill in form” action now uses the same label and icon both in the toolbar and in the contextual menu. * **Safer label rendering for subscriptions** — Fixed an error that could occur when displaying a subscription whose linked record had been removed. ## v2.53.1 — May 2026 [Section titled “v2.53.1 — May 2026”](#v2531--may-2026) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Certificate creation no longer crashes for non-training actions** — Opening or saving a certificate linked to an action other than training no longer fails. ## v2.53.2 — May 2026 [Section titled “v2.53.2 — May 2026”](#v2532--may-2026) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **Bulk certificate creation no longer crashes on actions without configuration data** — Starting the bulk certificate wizard from an action that has no additional configuration data no longer fails, and the wizard now opens with empty defaults for the affected fields. ## v2.53.3 — May 2026 [Section titled “v2.53.3 — May 2026”](#v2533--may-2026) ### Improvements [Section titled “Improvements”](#improvements) * **Reworked “Save as” dialog for attachments** — Choosing where to save a file now uses a redesigned dialog that lets you browse and pick a destination folder and type a filename in the same step. Folders you don’t have access to are no longer required to load before the picker becomes usable, and the destination tree stays open even when your starting folder isn’t visible. * **More reliable PPE delivery save** — Saving a multi-row PPE delivery now creates the related certificate and action link in a single operation, reducing the chance of partial saves if something goes wrong mid-way. ## v2.53.4 — June 2026 [Section titled “v2.53.4 — June 2026”](#v2534--june-2026) ### Improvements [Section titled “Improvements”](#improvements-1) * **Release notes link in About** — The About window now includes a direct link to the release notes, so you can check what changed in the latest version at any time. * **Suggested filename for PPE delivery documents** — When exporting a multi-person PPE delivery, the filename is now prefilled with the person’s name and the date, making delivery documents easier to recognize and file. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-3) * **Attachment list now loads correctly** — Fixed an issue where the list of attachments for some records could fail to load and show an access error, even though you had permission to view the record itself. --- # Release v2.54.x > Release notes for 4HSE v2.54 ## v2.54.0 — July 2026 [Section titled “v2.54.0 — July 2026”](#v2540--july-2026) ### New Features [Section titled “New Features”](#new-features) * **Permit to Work** — Certificates can now act as time-bound work permits: authorize a specific activity for a specific person or team, for a limited period, and verify it on site by scanning a QR code. See the [Permit to Work guide](/guides/permit-to-work/permit-to-work/). * **Certificate life cycle** — Certificates now carry a status — Draft, Valid, Revoked or Rejected — so you can prepare an authorization, approve it, withdraw it, or record that it was not approved. Expired status is derived automatically from the validity dates. * **Time-limited permits** — When issuing a certificate you can enable hour-level precision and set an exact start and end time, ideal for short-lived permits such as hot work valid for just a couple of hours. Without it, certificates keep working with day-level dates as before. * **Required forms before issuing a certificate** — Forms linked to an action can now be marked as required. The certificate cannot be created until every required form has been completed, with a clear indication of which forms are still pending. * **Verification QR code on certificates** — From a certificate detail you can now generate a secure, time-limited verification link and its QR code to share the permit. * **Public verification page** — Scanning a certificate’s QR code opens a public, read-only page — no account required — that shows the permit’s up-to-date status, the worker or team, the validity dates and any attachments. Expired links show a clear message inviting to request a new QR code. * **Person badge printing** — A new print template lets you print a person’s badge. ### Improvements [Section titled “Improvements”](#improvements) * **New statuses and exact times in the scheduler** — The deadlines list now shows the Revoked, Rejected and Expiring statuses with a dedicated color and icon, and displays the time alongside the date for permits that use hour-level precision. * **Prompt, time-aware expiry** — Permit expiry is now recalculated frequently and, when hour-level precision is enabled, honors the exact time of day, so a permit moves to expiring and expired right when it should. * **Clearer certificate status labels** — Certificate status labels have been reworded for clarity. --- # Release v2.5.x > Release notes for 4HSE v2.5 ## v2.5.0 — October 2020 [Section titled “v2.5.0 — October 2020”](#v250--october-2020) ### Improvements [Section titled “Improvements”](#improvements) * **API index** — A new API index endpoint provides a catalog of available API resources. * **Translation correction** — Fixed the translation of “outsider” to “external” for external contacts. * **Project user office list** — Added support for viewing user-office associations within projects. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Multiple fixes** — Fixed several issues reported in production. ## v2.5.1–v2.5.7 — January 2021 [Section titled “v2.5.1–v2.5.7 — January 2021”](#v251v257--january-2021) ### Improvements [Section titled “Improvements”](#improvements-1) * **Icon refresh** — Updated icons throughout the application for a more consistent visual style. * **Row-level actions** — Added in-row action icons for quicker access to common operations. * **Suggestion filtering** — Added filtering capabilities to the suggestion system. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including icon display corrections, certificate list navigation, suggestion system improvements, and various stability fixes. --- # Release v2.6.x > Release notes for 4HSE v2.6 ## v2.6.0 — January 2021 [Section titled “v2.6.0 — January 2021”](#v260--january-2021) ### New Features [Section titled “New Features”](#new-features) * **New web client framework** — A completely rewritten front-end framework provides a faster, more responsive user experience with modern component architecture including forms, grids, toolbars, and tabbed interfaces. * **Office copy wizard** — A new wizard allows you to copy an entire office structure, including work environments, equipment, substances, jobs, risks, and documents, to quickly set up new offices based on existing ones. * **API integration** — New REST API endpoints for actions, demands, materials, risk demands, and substances. * **Unsaved changes warning** — The application now warns you before navigating away from a form with unsaved changes. ### Improvements [Section titled “Improvements”](#improvements) * **Custom attributes** — Added support for custom attributes on work environments. * **Grid improvements** — Multi-select grids with selection counters, improved sorting, and column persistence. * **Window management** — Improved window focus, sizing, and taskbar icon display. * **Action suggestions** — Improved action suggestion system with better filtering and display. * **Office sorting** — Offices are now sorted by default in the list view. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Sorting on non-indexed fields** — Fixed an issue where sorting on certain fields could cause errors. * **Various fixes** — Fixed multiple issues with window destruction, wizard tabs, and grid behavior. ## v2.6.1–v2.6.8 — April 2021 [Section titled “v2.6.1–v2.6.8 — April 2021”](#v261v268--april-2021) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including project creation issues, notification preferences, attribute grid display, translation corrections, rich text editor translations, and action grid navigation. --- # Release v2.7.x > Release notes for 4HSE v2.7 ## v2.7.0 — May 2021 [Section titled “v2.7.0 — May 2021”](#v270--may-2021) ### New Features [Section titled “New Features”](#new-features) * **Cross-project office copy** — You can now copy offices between different projects, including all associated data such as jobs, risks, demands, actions, and documents. * **Risk copy** — A new risk copy feature allows you to duplicate risk assessments between offices, with options to copy or link entities and manage duplicates. * **Contextual help in wizards** — Contextual help is now available in all wizards and detached windows. ### Improvements [Section titled “Improvements”](#improvements) * **Copy wizard** — The office copy wizard now includes a comparison step for managing duplicates, with tree-based selection and grid comparison views. * **Job management** — Improved job management with people, actions, and certificates tabs. * **Grid delete behavior** — Improved the toolbar delete button behavior to correctly reflect selection state. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Multiple fixes** — Fixed various issues with copy operations, grid columns, and navigation. ## v2.7.1–v2.7.4 — June 2021 [Section titled “v2.7.1–v2.7.4 — June 2021”](#v271v274--june-2021) ### Improvements [Section titled “Improvements”](#improvements-1) * **Period management** — Re-enabled period management with improved dialog behavior. * **Notification links** — Notifications now include direct links to the relevant records. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * Multiple rounds of fixes including data display, navigation, and notification corrections. --- # Release v2.8.x > Release notes for 4HSE v2.8 ## v2.8.1 — July 2021 [Section titled “v2.8.1 — July 2021”](#v281--july-2021) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **General fix** — Fixed an issue reported in production. ## v2.8.2 — July 2021 [Section titled “v2.8.2 — July 2021”](#v282--july-2021) ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-1) * **Multiple fixes** — Fixed several issues including data display and navigation corrections. ## v2.8.3 — July 2021 [Section titled “v2.8.3 — July 2021”](#v283--july-2021) ### Improvements [Section titled “Improvements”](#improvements) * **Data anonymization tools** — Added tools to support database anonymization processes, including attachment metadata cache rebuild. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes-2) * **General fixes** — Fixed issues reported in production. --- # Release v2.9.x > Release notes for 4HSE v2.9 ## v2.9.0 — July 2021 [Section titled “v2.9.0 — July 2021”](#v290--july-2021) ### New Features [Section titled “New Features”](#new-features) * **Incident management (full release)** — The incident management module is now fully featured, with comprehensive support for incident recording, tracking, and reporting. Incidents support associations with people, actions, resources, and custom date/time tracking with timezone-aware timestamps. ### Improvements [Section titled “Improvements”](#improvements) * **Incident views** — New computed views provide real-time data for incidents and their associations, with automatic updates as data changes. * **Incident search** — Improved search capabilities for incident resources. ### Bug Fixes [Section titled “Bug Fixes”](#bug-fixes) * **Date/time handling** — Fixed several issues with date and time saving and display in incident records.