Release Notes

v0.7.589

Location fields, role permission controls, and activity panel fix

This release introduces custom fields for locations, giving practices more flexibility to manage and extend location information. It also strengthens role management by ensuring administrators can only assign permissions within their own access level, and fixes an error that caused the activities panel to fail for practices that had edited location details before this update.

Features

  • Custom fields for locations: practices can add, reorder, and manage their own field sets for location information, in the same way as staff, clients, and services already supported custom fields.

  • Custom field columns: the locations list can now display custom fields as optional, sortable columns, giving front-desk staff a clearer overview at a glance.

  • More flexible location data: address, contact details, and other location information are now stored in a more flexible structure, making it easier to add country-specific or practice-specific fields in the future without requiring a system update.

  • Editable social media links: social media links for a location are now a user-owned field set that practices can freely edit, rename, or remove to suit their own needs.

  • Safer role permissions: when creating or editing a role, administrators can now only assign permissions that fall within their own access level — preventing accidental escalation of rights.

  • Clearer role controls: staff role controls are hidden or disabled when the acting administrator does not have sufficient rights to manage the target role, making the interface clearer and safer.

  • Standalone admin labelling: administrators who are not linked to a staff member are now clearly labelled as a standalone administrator in the role overview.

Fixes

  • Activities panel fix: fixed an error that caused the activities panel to show a failure for practices that had created or edited a location before this update — the panel now correctly displays the full history of those changes.

Security and reliability

  • Stricter role boundaries: role management now ensures an administrator cannot grant another role permissions that exceed their own, reducing the risk of unintended privilege escalation.

  • More reliable release notes: the release note publication process now automatically retries and corrects itself when generated content does not meet quality standards, improving the reliability of release communications.