August 2026 Release — Attachments, Document Vault & Document Packs

The old Files & Links system on CRM Contacts has been replaced by the new Attachments panel. Files previously managed through Files & Links are now handled through the unified Attachments infrastructure.

Files can now be attached directly to bookings, leads, and CRM contacts (replacing the old Files & Links system) via a new Attachments panel. Supports folders and subfolders with rename, move, and delete operations. Deleting a folder lets you choose whether contents move up a level or are removed with it.

Clicking any attached file opens an in-place preview. Images, PDFs, and videos open instantly, and you can arrow through all attachments on a booking like a gallery.

Audio files play in a custom music player that renders a live waveform as the track plays, designed specifically for DJs and audio professionals.

Deleted files are recoverable by support for 30 days before permanent removal. A self-serve recycle bin is coming soon.

Executable and script files are rejected at upload time, including .exe, .msi, .bat, .cmd, .sh, .ps1, .vbs, .js, .jar, .scr, .com, .dll, .apk, .app, .deb, .rpm, and others. Files with blocked extensions embedded anywhere in the filename (e.g. document.exe.pdf) are also caught. After upload, file content is verified against its declared type so renamed files are detected and rejected automatically.

Individual files are capped at 1 GB. File names are limited to 500 characters.

The existing beta document vault has been completely rebuilt. Organisations can now maintain multiple vaults, each scoped to a purpose such as Compliance, Contracts, Insurance, General, or a custom type. Each vault is independently access-controlled with its own sharing policy. New organisations are seeded with Compliance, Contracts, Insurance, and General vault types.

Every vault belongs to a vault type that governs its icon and badge, default ACL template, external sharing policy (including whether links require a password, must carry an expiry date, and maximum link lifetime in days), and optional file expiry tracking for compliance-sensitive types such as Public Liability Insurance.

Each vault has its own access policy granting or denying permissions to individual org members or entire org roles. Three permissions are available: Read (files.read), Download (files.download, implies Read), and Write (files.write, implies Read). Permission resolution follows a strict precedence: admins and owners always have full access; user-scoped principals take precedence over role-scoped entries; within a scope, revoke always beats grant; and if a user-scoped principal exists but neither grants nor revokes the required permission, access is denied without falling back to role entries. Changes take effect immediately.

Vault files use the same S3-backed attachments infrastructure as booking, lead, and contact attachments, including the same upload lifecycle (presigned PUT then confirmed), content verification, blocked extension list, and 1 GB size cap. A thin vault_files metadata record associates each attachment with a specific vault and enables file expiry tracking. Files can be organised into folders and subfolders with the same folder operations as general attachments.

Document Packs provide a lightweight way to share a curated selection of files. Full details were not captured in this extract.