What's New — Week of 11 May 2026

Groups sit with people and companies

Groups moved out of User Management settings into Contacts, next to People and Companies. Site managers create, browse, and manage groups in the same area they already use for the rest of their directory, instead of digging through settings.

The group detail page adds context next to the member list. Where you have the relevant modules on, a compliance summary rolls up how members are doing on documents, risks, and forms (the same idea as a single person’s view, but for the whole group). A recurring distributions card lists any distribution policies that target the group. A comments panel keeps notes scoped to each site, so threads on a child site stay separate from the parent.

Groups in Contacts with detail, compliance summary, distributions, and member management

Member management is simpler: add and remove people in one form instead of a separate add-only flow. Memberships inherited from a parent site appear as locked rows, so you can see what you own locally and what comes from above.

Companies House on company records

Company records now support structured blocks, starting with UK Company Registration and Address. The registration block holds company type, status, jurisdiction, registered office address, and accounts metadata. You can fill it by hand or use Companies House search to find a company and prefill the block.

UK Company Registration block with Companies House search and sync options

If you turn on Companies House sync on a registration block, CalmCompliance refreshes that data weekly from the Companies House API. You can also suspend the company record automatically when Companies House reports a non-active status, which helps contractor and supplier lists stay accurate without someone checking by hand.

Sensitive company details can sit behind a reveal control; each view logs to the audit trail under the view-sensitive-company permission.

Work orders and service desk tickets stay in step

When someone starts a work order that links to a service desk ticket, the ticket moves to In Progress on its own. You do not need a manual status tick. The behaviour runs through the event system, no matter who starts the work order or where they start it (work order page, calendar, inbox card, or QR scan).

Ticket automation for linked work orders and expandable linked rows

The start rule (to In Progress) and the existing completion rule (to your chosen status) sit together in one automation card on the ticket. Both default to on for new tickets.

Linked work order and service desk rows are expandable. Opening a linked work order from a ticket shows status, priority, schedule, assignment, checklists, risk assessments, and costs inline, and the same applies when you open a linked ticket from a work order.