These are the release notes for March 2026 from Kubo.
See a summary of all the updates and click on the links to navigate to each one.
Version 1.4.13
NEW FEATURES
IMPROVEMENTS
Version 1.4.12
NEW FEATURES
March 30, 2026 - Version 1.4.13
New features
New bulk actions in the student list by company (administrator view)
We have implemented checkbox selection for students in the list by company under the Students > To List menu, with the aim of facilitating certain bulk operations, such as enrollment and user management.
When selecting one or more students, the Batch actions button is enabled, allowing the following operations:
-
Enroll in trainings
-
Enroll in tracks
-
Exclusion of training enrollments
Exclusion is allowed only for enrollments that have not yet started.
-
Exclusion of track enrollments
Exclusion is allowed only for enrollments that have not yet started.
-
Activating students
-
Deactivating students
This update makes management more agile, practical, and efficient, reducing the need for individual actions.
Notes:
-
Bulk actions, such as exclusion of users or adjustment of the validity of access to trainings or trails, will not be performed in this new feature, in order to prevent improper actions by administrators. These actions may impact student history, as well as user tier controls for the monthly billing of the customer’s contract.
-
When opting for batch exclusion (without consumption initiated), the accounting of active enrollments from previous months may be altered. We emphasize that the quantity of enrollments recorded in the month will be considered for the monthly billing of contract tiers, without any type of retroactive action.
Improvements
Information on trail availability in the list (administrator view)
We have added an Active column to the trail list, which allows you to quickly identify which tracks are available to users and sort the list based on this status, making it easier to manage and organize content.
March 09, 2026 - Version 1.4.12
New features
Student email verification settings (administrator view and student view)
We have added a new setting to the environment that allows you to define whether student email verification will be mandatory or optional for access to the platform.
In some cases, security requirements prevent emails from being resent when the student's account is not recognized or when it is full, causing the email to bounce back. In addition, it is also possible to configure specific email domains that will not need to go through this verification (whitelist).
On the settings screen, the field Require email verification for the student has been added. When set to Yes, the platform will enable two options in the field Block access for unverified emails:
-
Yes: the student will be required to confirm their email before logging in. If they try to access without confirming, the platform will display a warning and allow them to request the verification email again.
-
No: the student will be able to access the platform even without confirming their email. However, a warning will be displayed in the student's view to remind them to confirm.
The Email domains that do not require verification (Whitelist) field allows you to configure email domains that will not need to go through the verification process. The platform allows you to add more than one domain, simply separating them with semicolons in the configuration field. This is useful, for example, to automatically approve trusted corporate emails.