Week of 30 March 2026

Issues, requests, and incidents now support multiple locations and assets

Until now, a ticket could only link to a single location or asset. That works for straightforward requests, but plenty of real jobs don't: a report covering several rooms, an issue that touches one piece of equipment in more than one place, a contractor working through a list of assets in a single visit.

Issues, requests, and incidents can now include multiple locations and assets. Add them when you raise the ticket, and during triage you can add or remove items as the picture becomes clearer. When a work order is created from the ticket, it picks up every linked location and asset.

Service desk ticket with multiple locations and assets linked

Embed document metadata and version history directly in your documents

Documents now support two new content blocks you can insert anywhere in the editor.

The Document metadata block embeds a table with the document name, version, and identifier in the body. The Version history block is a running list of published versions—numbers, dates, and what changed—updated each time you ship a new version.

Document metadata and Version history blocks embedded in the document editor

Both blocks work in the editor, in shared public links, and in PDF exports. If you live in a document library where version history actually matters, that history is now in the document, not something you stitch together from breadcrumbs elsewhere.

Request document approval without a predefined workflow

Document approvals used to need a configured approval template. That's a good fit for processes you run again and again; it's less helpful for one-off reviews—a new policy that needs a manager's eyes before it goes live, or a document reviewed outside the usual cycle.

You can request approval ad hoc: choose individual approvers or groups when you ask, with no template required. Documents with pending changes also show a draft indicator in lists and detail views, so you can see at a glance what's still waiting on someone.

Requesting document approval ad hoc with approvers selected

See all your distributions in one place

Documents, forms, and risk assessments each have a dedicated distributions page at site level. Before, you mostly saw distributions by opening each record. Now there's one view per module for everything that's been sent, to whom, and where it stands, with a link straight back to the source when something needs attention.

You can start new distributions from those pages too, so when you need to send several documents, it's one place to work from instead of hunting through individual records.