What Got Shipped Today - 3/9/26 - Approvals can be switched off where they were never wanted, the Invoice Register respects who you are, retention agrees with itself

3 September 2026 Features Turn off approvals for the entity types you never wanted them on "We don't run a delegation of authority on purchase orders. Every time someone submits one, the platform invents an approval step and emails half the business. We just want it to go through." Before If no approval workflow was configured for an entity type, the platform did not let the submission through. It fell back to a safety net: a synthetic workspace-admin approval, where every role with Admin access had to approve. For a builder who deliberately does not run a delegation of authority on that entity, this was pure friction. The submission stalled, notifications went out to people who had no interest in the record, and the only way around it was to build an approval workflow nobody wanted, just so the record could pass through it. AfterThere is now a workspace-level setting, sitting in Admin under Approval Workflows, called "Skip approval when no workflow is configured". Switch it on, and any entity type with no active workflow (at workspace or project scope) goes straight to approved. No approval instance is created. No notification is sent. The record lands where it was always meant to land. Where a real workflow does exist, nothing changes. A configured approval is never bypassed. The setting only affects the gap. For subcontract payment schedules, the skip path also carries the full downstream behaviour with it: the schedule is auto-accepted and pushed to Xero, exactly as a real approval would have done. Impact Builders who run approvals on some things and not others no longer have to fake a workflow to get a clean submission. The delegation of authority becomes a deliberate choice per entity type rather than an all-or-nothing gate, which is how it works on a real site. Known limitations The setting is off by default and stays off for every existing workspace, so nothing changes for anyone until it is deliberately switched on. It is admin-gated, and it is per workspace, not per project. Improvements The Invoice Register only shows you the projects you can actually open "Our site-based commercial guy opened the Invoice Register and could read every invoice and every claim across the whole business. He is on one job." Before The Invoice Register loaded every project in the workspace regardless of the projects a user was assigned to. Someone who could only open one project in Horizon could still sit in the Invoice Register and read supplier invoices, claim values and payment positions across every job the business was running. Commercially sensitive, and not what anyone assumed was happening. After The Invoice Register now defaults to the projects the signed-in user can access. If you are on one job, you see one job. Project access in Horizon is now the same answer everywhere, including the money. Impact Commercial information stops leaking sideways. A project engineer, a site-based CA or a subcontract administrator sees the invoices belonging to their work and nothing else, which is what most builders assumed the register was doing already. The Invoice Register in Deep Space, showing only the projects the signed-in user can open. Someone assigned to one job no longer sees supplier invoices and claim values from every other job in the business. The starter scope library is reachable once your library has scopes in it "The preset scopes were supposed to give us a head start. By the time we went looking for them, the offer had vanished." Before New workspaces ship with a preset library of basic, region-appropriate scopes of works. The offer to load them only appeared while the scope library was completely empty. The moment anyone saved a single scope, which happens within minutes of a workspace going live, the starter set became unreachable. The customers most likely to want a proven starting point, the ones already using the platform, were exactly the ones who could no longer get to it. After The starter scope library is now reachable from a library that already has content in it. You can pull in the preset scopes at any point, not only on day one. Impact Estimators and contract administrators get a credible baseline scope to build from instead of writing from a blank page, whether they went looking for it on their first afternoon or three months in. Fixes Retention on the payment schedule now matches the retention register "The retention card on the payment schedule says one number. The retention register says another. Which one do I certify against?" Before The retention figure shown on the subcontractor payment schedule did not agree with the retention held in the register for the same subcontract. Two screens, two answers, on a statutory document. Anyone certifying a payment schedule had to leave it, check the register, and work out by hand which figure was right before they could sign anything off. After The retention value on the payment schedule is calculated from the same source as the register, so the card and the register read the same number. Impact A payment schedule is a statutory document. The person certifying it can now trust the retention shown on the face of it, without a side quest through the register to confirm the platform agrees with itself. A subcontractor payment schedule in Deep Space. Retention this period reads $2,090.00 at 5%, the same figure the retention register holds against that subcontract, so the person certifying can see the whole position without leaving the schedule. Spotted something, or want to tell us what to build next? Every entry here started as a piece of customer feedback. Drop yours in the feedback portal inside the platform, we read all of it.