We’re committed to keeping you fully up to speed with all of the features, enhancements and fixes we ship at Root. Here are all of the updates and improvements we shipped over the last month 🛠️

Features

We’re working on new features to expand what you can do on Root:

• Root Node 24 stack now available: The Node 24 stack is now available on Root, giving you access to the latest runtime features when building and managing product modules. Read the docs.
• Support for restricted data in product module responses: Product module hooks can now return an optional restricted_data object, allowing sensitive information to be stored separately with visibility controlled by permissions. This feature will be rolled out in March. Read the docs.
• Extending user group controls: Work is being done to ensure users within a user group only see policy data belonging to their group. This includes:
  • Webhooks: Webhooks can be scoped to a user group, so only entities within that group trigger the webhook. This feature will be rolled out in March. Read the docs.
  • Claims: User group controls now extend to claims, so users only see claims linked to policies within their group.
• Pending alteration packages: Work is being done to support pending alteration packages on Root. Users will be able to save an in-progress alteration and return to it later, with a dedicated view to manage all pending packages for a policy. This feature is not yet available to clients. Read the docs .
• Disable organisations: The Root team can now disable specific organisations on request, hiding them from Dashboard and pausing platform activity. This can be useful for managing test or inactive organisations. Reach out to your Root contact if you'd like to make use of this.
• Check for floating promises on push: Code pushed with rp push is now analysed for floating promises, and any detected cases are flagged to help catch un-awaited async behaviour early. Detection will continue to improve over time, with stricter enforcement planned for a future release.

Platform Enhancements

• Performance Enhancements

  We’ve introduced enhancements to improve stability, efficiency, and visibility across Root:

  • Platform infrastructure improvements: Internal updates were made to streamline platform resources and improve database performance.
  • Improved bulk file upload reliability: Uploading multiple files to a policy at once could occasionally cause errors. Files are now processed in batches to prevent this, ensuring bulk uploads complete reliably.

• Billing Enhancements

  We’ve made several improvements to increase reliability, accuracy, and automation across Root’s billing processes.

  • Improved efficiency of daily billing processing: Work was done to optimise the daily billing process, helping payments be marked and processed more efficiently and reliably.
  • Payment reversal notifications: Policyholders can now be notified when a payment reversal is created during payment processing, such as when a debit order is reversed. This feature can be enabled on request.
  • Retry reversed payments setting: This new billing setting allows a pending payment to be automatically created when a previously successful payment is reversed, such as a debit order returned by the bank. Retry behaviour can be configured per product module, including the number of retries and days between attempts. This feature can be enabled on request. Read the docs .
  • Ongoing improvements to collection modules: Work is continuing on collection module infrastructure, including support for local development and execution, as well as improved logging and log querying. These updates are still in development and not yet available for client use.
  • Continued improvements to the new policy ledger: Work is continuing on the policy ledger, including improvements to how balances are calculated and updates to the Dashboard interface. These changes remain in development and are not yet available for client use.

• Bug fixes

  We’ve addressed key issues to improve system reliability:

  • Improved CSV import validation: Resolved an issue where CSV imports did not correctly flag missing or unexpected columns, improving the reliability of the import process.
  • Bug fixes to improve billing accuracy: Several updates were made to improve the reliability and accuracy of billing processing:
    • Resolved an issue where certain notifications were not being delivered due to legacy data. All valid notifications are now processed correctly.
    • Fixed an issue where the default billing provider setting could be unintentionally overridden during updates.
    • Improved handling of policy numbers in Nedbank response files to ensure accurate processing across different reference formats.

If you have any suggestions or feedback, please share them with your Client Success Manager or submit them via the Root product roadmap to make sure we always know what’s top of mind for you.