TECHNICAL NOTE – NAVIGATION AND REGISTER SCOPING

Version 5.0 introduces a rebuilt navigation, and with it a change to the way registers scope the platform. Registers are no longer a mode you enter and stay inside; they are applied as an ordinary filter. Register-nested links continue to work and are redirected to their global equivalent, but the register is not reapplied as a filter, so existing bookmarks and saved links will return a wider set of records than before.

TECHNICAL NOTE – TAG CREATION PERMISSIONS

Version 5.0 includes a change to who can create tags. Tag creation is now resolved through team feature settings: a user can create tags if they are a member of at least one active team with the setting enabled.

The setting is disabled on all existing teams on upgrade. Tag administration in the admin area is unchanged and remains administrator-only.

NEW FUNCTIONALITY & FEATURES

The following is a summary of the new features and improvements that have been implemented in version 5.0. Additional minor changes to interface and configuration options may not be outlined within this changelog.

If you would like further information about any of the features or improvements listed below, please contact Clew Support at support@clew.io

1. A new way to navigate Clew

The dropdown-driven header has been replaced by a persistent left-hand panel that adapts to where you are in the platform, with a narrow rail for switching between Dashboard, Modules and Organisation in a single click. The register tree is hierarchical, searchable, collapsible and keyboard accessible, and every module now carries its own icon. Module icons ship as defaults across 49 core types and remain editable per core type in admin.

Breadcrumbs have moved into the top bar and now cover dashboards as well as module and record pages. On register pages the breadcrumb shows the full register ancestry and carries a dropdown, allowing you to move to a parent, sibling or child register without leaving the page.

The profile menu has been rebuilt into four groups, with several items renamed. Logging out now uses an inline confirmation rather than a browser dialog.

i. Registers as a filter

Module lists are global by default and a register is applied as a filter, in the same way as location or business unit. You can move between an organisation-wide view and a single register without leaving and re-entering a scope, and links are no longer nested under a register path. Creating a record from within a register still defaults that register on the new record.

ii. Rebuilt list views

Module list views have been rebuilt, replacing the server-rendered pages, legacy filter row and server-side pagination. The result is faster loading, in-table pagination and sorting, and consistent behaviour across the platform. Column composition continues to be driven by each module's configuration, so existing admin settings carry across unchanged.

Empty lists and filtered lists are now distinguished. A list with no records shows an empty state with an inline add action, while a search or filter that matches nothing keeps the table header visible above a separate no results message.

iii. Row-level actions on lists

The pinned column at the end of each row is now an Actions cell containing row-level Edit and Delete, both of which act on the list without a page reload. Modules with a headline action show it as a labelled primary button at the start of the cell, with further actions in an overflow menu: Respond on Surveys, Start and Stop on Workshops, and Run on Schedules.

Actions are resolved per list rather than per row, so a row you cannot act on shows the control disabled rather than hidden. Row Delete requires the delete permission on the record and the mass permission on the module. Mass Delete sits permanently in the action bar wherever the tenant grants the mass permission.

iv. A consistent filter bar

Filtering has been unified into a single filter bar across datagrid and module lists, carrying a search box, the Register filter, Tags, Refine By, Advanced filters, saved filters and Clear filters.

The Register filter allows multiple registers to be selected from a hierarchical picker, drilling to any depth. The control previously labelled Refine by is now Tags. Refine By is a new control that narrows a list by common attributes such as state, custom type and objective type. Each module's stock toggles now sit inside Advanced filters alongside your saved filters.

Filter selections are remembered per module rather than globally, so filtering Risks to one register no longer filters Incidents the same way. Selections are held in the browser and do not follow a user to another machine.

The Project/Register show view gains its own version of the bar, allowing you to choose which module subpanels are visible and apply a tag filter across all of them at once.

2. Redesigned AI form completion

The AI-assisted form experience has been reworked. An Ask Clew action bar sits at the top of the form, and All possible fields populates every eligible field in one action once you have supplied context. Reject all returns the fields to blank, or you can generate again.

Individual AI-enabled fields carry a control to improve that field, and a reject control that appears once AI has written to it and returns the field to your previous text. Acceptance is implicit throughout: generated content is saved with the record unless you reject or edit it.

3. Monte Carlo and Costed Risk Improvements

Pre-mitigation and post-mitigation simulations no longer have to be run separately. Select a category, opt into a combined run, and both are run automatically with the outputs generated side by side on the simulation report.

P10, P50 and P90 values are available as fields on Risk in the dashboard builder, so simulation output can be added to any widget in the same way as any other risk field. Where multiple runs exist, the most recent is used. No new dashboard type and no additional permissions are required.

Calculated Residual is a new option that works out post-mitigation exposure at run time from values recorded on mitigation actions, rather than from a typed residual rating. It is selected through a Residual values selector on the run page and works with a combined run. Actions gain two optional fields, Cost Saving ($) and Likelihood Reduction (%). Where several actions apply to one risk, cost savings add and likelihood reductions multiply. A risk with no action values keeps the residual values recorded on it, and calculated values are never written back to the risk rating.

Three related improvements shipped in 4.24 and are included here for completeness: setting the rating type and category once at the top of a simulation with a per-risk override, a likelihood decimal field on all rating types, and a change to the simulation access policy so that a simulation can be read by anyone who can read every risk within it.

4. Simple Risk Assessments

Risk assessments now support a simple mode in which job step hazards and controls are held as plain text on the job step rather than as links to the controls and hazards libraries. This removes two frictions of shared records: editing a title no longer changes it for every assessment that references it, and a user is no longer missing items they lack permission to see. Simple entries also keep the order you put them in, in the panel, the sub-panel and PDF exports.

Simple mode is enabled per custom type in admin, so different risk assessment types can work in different ways. Toggling the setting does not migrate data in either direction, and simple mode replaces the library-linking interface for that custom type, including the ability to build job steps from the library.

Editing simple hazards and controls happens in a dedicated modal with two tabs. The List tab gives each entry its own row with add, move and remove controls, and the Text tab is a plain text area with one entry per line. Switching between tabs preserves the content.

5. Delegated tag creation

Tag creation is now a team feature setting, alongside cloning, custom fields, notifications, workflows and the other delegable capabilities. Users in a team that grants it can create the tags they need without raising a request with an administrator. Changes to the setting are recorded in team history.

Creating a tag from a record requires both the capability and update permission on the record. Attaching and detaching existing tags is unchanged. Tags remain a single tenant-wide vocabulary, and tag administration remains in the admin area. See the technical note above for the effect on existing administrators.

IMPROVEMENTS / CHANGES

1. Latest Survey Result on simple risks

Survey results are now visible on controls in the control sub-panel of a simple risk, matching bowtie risks. Latest Survey Result is also available as a column on controls list views.

2. Vacant roles in the filter builder

Role vacancy is now a condition in the generic filter builder rather than only a hard-coded pill on the Roles list. It can be saved as part of a favourite filter, combined with other conditions, and applied through a Role association on another record type.

3. Date validation on external forms

External form schemas now carry the same occurred at and reported at date validation as the backend. Previously a form could be submitted successfully and then fail on acceptance; the form now blocks the submission at the point of entry.

4. Triggers on form submissions

An after-update trigger on a form submission can now run a callback event on the record that submission created. This can be used to stamp data from the submission onto the new record, such as setting an incident's Reported At from the form submission timestamp.

5. Sort step in CSV export templates

Export column chains gain a Sort step, allowing a collection to be ordered before First, Last or Join consumes it. This allows an export to express something such as the highest inherent rating rather than returning an arbitrary record. A Filter step now also preserves the order of the collection it receives.

6. Announcements for client system administrators

Announcements can now be set up by customers themselves rather than requiring Clew to configure them.

DEPRECATIONS

1. Register roll-up

Roll up from child registers is removed on item lists under the new navigation and register based filtering replaces it. Where a register's children were previously rolled up automatically, select the registers required in the Register filter, which supports drilling to any depth.

2. Workflow state summary strip on list views

The workflow state summary card strip above module lists is not rendered in the rebuilt list views. Workflow state is available as an ordinary column that can be sorted and filterxred.

3. Profile menu changes

The currency switcher, user links, Mailboxes, Registers and Add Register are not carried across into the rebuilt profile menu. The currency switcher can be accessed via account settings while user links, mailboxes and register management is available from the admin area.

Download Documents

Videos