What's New: Week of 13 July 2026

Documents and premises records both picked up useful depth this week: files that sit with the block they belong to, lease detail on the assets you already manage, and cleaner public sharing.

Keep files with the block they belong to

Insurance certificates, warranty PDFs, and right-to-work scans usually belong to a specific block, not the whole asset, location, or person. Until now those files sat at entity level, so you scrolled the attachment list hoping the right certificate was the one you meant.

You can attach files on the block itself when you create or edit it. The files show inside the block card, inherit the block's scan visibility, and still appear in the entity-level attachment list with a jump back to that block. This covers asset blocks (including insurance, warranty, and UK vehicle), location blocks (insurance and lease), and personnel blocks such as DBS, right to work, and employment details.

Insurance block on an asset with Insurance Certificate.pdf attached under Files

Keep lease detail with the asset

Leased plant, vehicles, and kit often left commercial detail in a folder or against a location only. Provider, cost, and renewal sat apart from the asset itself, and rolling leases either needed a fake expiry date or cluttered expiry insights.

You can add a Lease block on an asset instance: provider, reference, amount, frequency, lease type, and auto-renew. Turn auto-renew on and you leave the expiry date blank for a rolling lease; turn it off and the date picker returns. Location leases carry the same commercial fields. Auto-renewing leases stay out of expiry-driven insights, so your reminders track fixed-term renewals only.

Add Lease form on an asset with provider, payment, dates, and Auto-Renew

Link straight to a document in a shared collection

Sharing a controlled pack of documents often meant sending the collection link and hoping people found the right item, or using an awkward address that exposed an internal id. Embedding that pack on another site was similarly blunt: you could hide the header, but not much else.

Each document in a shared collection now has its own public URL. When you edit the collection, set or accept a URL slug per document, copy the link from the detail view, and send people straight to that file. Old links that used a document id still work; they redirect to the new address. When you embed a collection, you can hide the title, description, or back button independently, and those choices stay put as readers move between the list and a document.