Skip to content

Brief Connect v2.3.5 Release Notes

Release date - 3rd December, 2025

Package version: 2.3.5

Changes

In the v2.3.5 release, we have addressed several bugs. We'd like extend a special thanks to the WA Department of Water for their assistance in helping us identify and debug some of the issues in this release.

  • Resolving frequent user reauthentication requests Some end users recently found Brief Connect would force them to log in more frequently, following an upgrade to version 2.3.2 or higher. We've implemented a fix for this, so login prompts should return to their normal frequency
  • Limiting notifications to users who don't have record access We've made a change to the default behaviour of notifications - now, a user will not receive notifications for a record if they don't have access to view that record in the first place.

Context

Most system notifications from Brief Connect are triggered from different types of activity on a record - such as role assignments or workflow task changes. For these types of notifications that are triggered from record activity, to receive the notification you either needed to be assigned a role on that record, or be a proxy to another user assigned on that record. Some customers have recently been exploring different types of configuration that would allow small teams to prepare a record collaboratively, but limit any role-based access to that record until it progresses out of an initial drafting stage. The previous challenge with this approach was that activities like role assignments would often trigger notifications to end-users that - due to the permissions configuration - lacked access to the record despite being assigned a role. With this change, it tightens security and access to record information, as well as enabling use cases like a 'drafting-mode' for records.

  • Incorrect links to Original Correspondence We've implemented a fix to records where there were some cases of links to 'Original Correspondence' files being incorrect.