FSManager 1.1

FSManager 1.1 introduces task claim permissions — control over which workers are allowed to claim time against which job tasks — along with a safe way to trial the rules before switching them on.

This page documents what shipped in 1.1 and any patch updates on the 1.1.x line.

Highlights

Claim permissions built around departments. Each department is granted the departments it may claim work for. Sensible defaults are configured for you.
A trial mode. Run the rules in Warn for a fortnight, review what they would have blocked, then switch to Enforce with confidence.
A new Claims Outside Scope report showing exactly who has been claiming outside their remit, and why.
A tidier job part screen, with actions grouped into clearly-named menus instead of a wrapping row of buttons.

1.1.0 — 26 August 2026

For all users

Job tasks now know who’s allowed to claim them. Previously any worker selected on the Job Manager could claim any task — a glazier could book time against invoicing, a salesperson against factory work. Claims are now checked against the worker’s department.
Out-of-scope tasks stay visible. The Job Manager exists to show the whole picture, so nothing disappears from view. It’s the claim control that goes dead — greyed out, with a tooltip naming who is allowed: “Glazing is Manufacturing work — Site Work isn’t allowed to claim it.”
A tidier job part screen. The job part toolbar had grown to around eleven buttons and wrapped onto a second row on smaller screens. Related actions are now gathered under a handful of clearly-named menus. Everything that was there is still there.

For admins

Set who can claim for whom. Each department carries a grid of the departments it may claim work for. A department can always claim its own work; everything else is explicit. Defaults are configured for you: Administration and Production can claim anything, Manufacturing and Delivery cover each other and Site Work, Sales can claim Administration work, and Site Work claims only its own.
Every task type has an owning department, so the rules have something concrete to check against.
Two exceptions are set up for you. Project Managers can claim Site Measure even though it is Administration-owned, and Invoicing is restricted to office positions so it doesn’t fall to sales reps.
Three modes, in Job Settings → Task Claim Enforcement: Enforce (the default — out-of-scope claims are refused), Warn (allowed, but recorded), and Off.
A new Claims Outside Scope report (Reports → Manufacturing, Administrators only) lists every claim that broke the rules, with the reason, over a date range you choose. It defaults to the last 30 days.
The recommended rollout is Warn → review → Enforce. Run Warn for a fortnight and print the report. Every row is either something to correct in your configuration — a worker in the wrong department, a task pointed at the wrong owner, a missing grant — or a genuine exception worth allowing. Then switch to Enforce knowing nobody gets locked out on the Monday.
The report explains an empty page rather than leaving you guessing. Empty on Enforce means claims are being refused so there is nothing to record; empty on Warn means your configuration already matches how people actually work.

Fixes

Merged documents file themselves correctly. Documents produced by a document merge could be saved with no attachment category at all, making them harder to find later. They now file under the category configured for that document type — including three new ones for maintenance, variations and credit applications.
The accounting entry task is configured out of the box. This setting was blank on every site, which quietly left part of the accounting hand-off unconfigured.
A multi-quote comparison no longer previews an empty table. Previewing a comparison document showed no options; it now shows the real ones.
Re-importing suppliers no longer fails when your catalogue holds two entries that resolve to the same supplier.

Behind the scenes

Substantial continued work on upcoming capability — progress claims, invoicing, site works scheduling and delivery execution — ships in this release but stays out of sight until those plans launch.
The demo site now carries a sample document on every surface that produces one, so an evaluation matches what you actually get.
Document template identities are now stable across system rebuilds, removing a class of failure when pushing templates out to sites.

Patches

1.1.1 — 1 September 2026

A maintenance patch. Nothing changes on screen and there is nothing you need to do.