# Version 9.1.150.1 (Support Release - 20 August 2026)

#### **People Management**

##### Ensure that the All People, People Group is recalculated when a person is appointed (#154414)

**Problem**

- When appointing a person, the All Employees people group is not always refreshed

**Solution**

- Ensure the people group is fetched when all types are requested without filtering

##### Ensure that users who are not authorised to edit appointments do not receive a 405 screen (#154695)

**Problem**

- When a user is not allowed to edit appointment history based on the people group access, the user receives a 405 error rather than getting notified of the not authorised exception.

**Solution**

- This change updates the way unauthorised access is handled in several actions within the PeopleController.
- Instead of returning a generic Unauthorised () response, the controller now provides user feedback via a localised error message and redirects the user back to the appropriate edit page or tab.
- This improves the user experience by making authorisation failures clearer and guiding users back to relevant pages

##### People with birthdays not available on the People dashboard. Unable to edit a user's profile when unique ID number is active (#154605)

**Problem**

- Birthday saved with a time component
- Filter criteria on people management dashboard incorrectly filter on birthday
- When a unique ID number is active, saving on the profile screen incorrectly validates for the user itself

**Solution**

- This change improves date handling and filtering logic across several user query endpoints and ensures consistent date-only comparisons in both application code and SQL queries.
- Additionally, it introduces a minor scheduling fix for bi-weekly notifications

---

#### **System Access**

##### Ensure that when absolute session expiry is reached, the user is redirected to the login page automatically. Prevent warnings from 30 to 1 minute from showing on every page loaded (#153089)

**Problem**

- When the session will expire 30 minutes before it shows on every page.
- When the session expires on an SPA file, the page breaks on click.

**Solution**

- Add checks to show the 5-minute warning only once every 5 minutes.
- Add an auto-redirect to the logout page when the user session has expired.

---

#### **Ruleset Management**

##### Implement usage of refresh token expiry as absolute session expiry. A warning to the user when the session is about to expire from 30 minutes before. Add session expiry to the Profile drop-down (#152563)

**Problem**

- User session never expires, and it is difficult to know when it will expire.

**Solution**

- This change introduces significant improvements to session management, token lifetime configuration, and user experience around session expiry.
- The changes ensure that session expiry is consistently enforced and communicated across the backend and frontend, and that refresh token lifetimes are configurable and respected throughout the application stack.

---

#### **Notifications**

##### Allow nullable Quartz simple trigger string props (#154089)

**Problem**

- Quartz simple-property triggers can store NULL string properties, but the generated Notification schema marked STR\_PROP\_\* columns as required.
- This made it so that the Notification service did not successfully do its part during ruleset/tenant creation

**Solution**

- Override the Quartz EF model so those string properties are nullable and future migrations align with Quartz runtime behaviour.

---