Release Notes

v0.7.597

Admin portal navigation, invite data scope, and location branding

This release reorganises the admin portal's Configuration section, introduces explicit data-access scope selection when inviting admins, and adds per-location brand colour overrides. Status badges across client and staff pages now share a consistent visual style.

Features

  • Configuration section in navigation: API Profiles and Webhooks have moved from the Access section into a new Configuration section, alongside General settings, making it easier to find all setup-related tools in one place. Old bookmarks continue to work.
  • Explicit data-access scope for admin invitations: When inviting someone to the admin portal, you now choose upfront whether they get access to all locations or only specific ones. The selected scope is shown in the invitation email and saved to the account, so there is no ambiguity about which locations an admin can work in.
  • Per-location brand colours: Each location can now have its own primary, secondary, tertiary, and ghost brand colours for the admin portal. When an admin is working in a single location, the portal uses that location's colours; if none are set, it falls back to the organisation's branding and then to the default theme.
  • Staff public name pre-fill: When enabling public website visibility for a staff member who has no public name set, the form now automatically fills in their name so you do not have to enter it twice.
  • Consistent status badges: Account status, verification status, admin access, and public team page visibility badges now share a uniform look across all list, card, and detail views, making it easier to read staff and client status at a glance.

Fixes

  • Staff invite defaults to work locations: When opening the invite dialog for a staff member, the data-access scope now defaults to their active work locations, so you no longer have to select them manually.
  • Scoped invite without locations rejected clearly: Submitting an admin invitation with scoped access but no locations selected now gives an explicit error instead of silently creating an account with no location access.

Security and reliability

  • Dependency security update: A build-tool dependency has been updated to a patched version, resolving known advisories. The project now reports zero known vulnerabilities.