We’ve rolled out a set of updates focused on improving data accuracy, assessment review process, and overall user experience. Here’s what’s new:
1. Improved validation for custom field names in registers
To prevent confusion and ensure data integrity, users can no longer create or rename a custom field with a name that already exists in the register—either as a default or custom field.
Attempting to create or rename a field with a duplicate or restricted name will now trigger this error: "A field with this name already exists as a custom or default 6clicks field. Please choose a different name."
Impact on imports: If duplicate field names already exist in a register, the import process will now fail due to conflicting header names. Users must resolve these conflicts before re-importing.
Existing duplicate fields are not automatically renamed. However, any rename attempt will be subject to the new uniqueness check.
2. New ‘Partially compliant’ status in QBA assessments
We’ve added a new status option—Partially compliant—to the 'Compliance status' dropdown in QBA Assessments.
Users can now select, filter by, and report on this new status.
Indicators for this status appear in the UI when selected.
Dev API support is included, so you can programmatically access the "Partially compliant" status via integrations.
Analytics module supports the new compliance status: "Partially compliant" in QBA assessment reports
3. New permission: 'Projects & playbook task'
A new permission is available under General > My Tasks:
When enabled, users can view and action all project tasks assigned to them.
Linked data tab visibility depends on having the Projects & playbooks permission.
Existing users with Projects & playbooks permission are granted this new permission automatically.
4. UI and performance improvements
We’ve made key updates to improve usability and performance:
Standarized layout for the Risk review side panel and Overview tab.
Optimized performance for the User Permissions dialog under the Administration area.