Stop chasing files across shared drives and inboxes

What this module does

A purchaser preparing a supplier package needs the latest drawings, the rev 2 spec, the inspection criteria, and the customer-specific requirement document, all on the lines of the purchase order going out today. Without a way to pull them by record, the purchaser emails the document handler who walks the registry, picks the files, drops them in a folder, and emails them back two hours later, blocking the order. With documents tagged to the records they belong to, the purchaser selects the BOM lines, combines the attached PDFs into one download, and sends the package the same hour the line is approved.

Key pages

Documents is the central registry for every drawing, certificate, procedure, and record. Files are tagged to the records they belong to (projects, items, production orders, routing lines, purchase orders, NCRs) and appear inline on every page that shows those records. Upload goes from the browser straight to the company's own Azure Blob Storage account, so large files are not held back by the limits of routing them through Business Central. Business Central keeps the reference and the storage key; the file itself stays in storage the company controls. If the company ever leaves, there is nothing to extract from a vendor.

Purchasers stop waiting on the document handler for a supplier pack. Operators see the drawing for the operation they are running, not the drawing for the operation done two months ago. A QA lead assembling a customer trace combines all certificates on a BOM into one PDF instead of recompiling from scratch. The Business Central administrator answers the careful sponsor's question about data ownership with a simple statement: the files are in the company's own Azure account, scoped to private containers and signed download links, and Visual Tracking holds no copy.