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.6 — 27 October 2026
A small release. Nothing in it changes how you use FSManager day to day.
Behind the scenes
- Groundwork for invoicing: when an invoice is issued, the amount recorded against the job part, variation or maintenance request is now stored excluding GST, the same basis as sales prices and everything else in FSManager. Invoicing isn’t switched on and isn’t part of your plan today.
- Security updates to some of the components FSManager is built on.
- Improvements to the tools FSM Developments uses to look after its customers and demos.
1.1.5 — 5 October 2026
Two changes you’ll notice: office and production staff can now set a task’s status straight from the Job Dashboard, and detail forms are much easier to read on laptops. There are also fixes to automatic sign-out, and one of them affected payroll hours.
For all users
- Set a task’s status from the Job Dashboard. If you can edit tasks (Administrators, Office and Production by default), you can mark a task Complete, In Progress or Not Started without anyone claiming time on it, including taking a completed task back off complete. Right-click a task cell on the main board (in Detailed view) to set it for every item on the job part. Inside a job, right-click one item’s task cell to set it for that item, or right-click a task’s column header to set it for every item. Everything that follows from the status moves with it: the part’s stage, delivery and install dates, and the site measure stage. FSManager refuses, and says why, if someone is clocked on the task or if it’s the task that tracks invoicing, which follows the job part’s Invoiced tick. See Setting a task’s status.
- Forms that fit your screen. Detail forms such as Employee and Quote Revision could be almost unusable on a typical laptop, or on a larger monitor with Windows display scaling turned up. Each field’s label took most of the width and left only a sliver for the box you type in. Labels now take only the space they need on every screen, and forms on mid-sized screens switch to a two-column layout.
- Still signed in from an earlier day? If someone is still signed in from a previous day and selects themselves on the Job Manager, FSManager no longer opens a second, empty session over the real one. It shows the time that has built up and asks whether the shift is still going.
For admins
- Edit Sign Out Time now takes a date as well as a time, so you can close a session left open from an earlier day. A new Sign Out At Scheduled Time button fills in the person’s scheduled finish for that day. See Closing a session left open.
Fixes
- Unpaid breaks are now deducted when FSManager signs someone out automatically. Before this release, a day closed by automatic sign-out could count an unpaid lunch break as paid time, unlike a day signed out by hand. If you use automatic break-taking with unpaid breaks, check any payroll weeks that are still open for automatically closed days.
- The “Dismissed Time” recorded for an automatically closed day is now the right size. It was measured up to whenever the sign-out happened to run, which could be the next day. This one didn’t affect payroll hours.
- Winning an opportunity a second time no longer creates a duplicate job. You get a message naming the job that already exists. A cancelled job doesn’t block a new win. See Win, lose or reopen.
- Re-winning a requote no longer wipes job details. The building consent number, legal description and R-value you entered on the job after the first win are kept.
- The Job Part Item screen no longer offers Save and New. It only ever produced a blank item outside the job’s numbering.
- Ticked boxes in pop-up grids are easier to see in dark mode.
Behind the scenes
- Groundwork for invoicing, progress claims and accounting integration. None of it is switched on, and none of it is part of your plan today.
1.1.4 — 7 September 2026
One change you’ll notice: you can no longer have a task running and be checked in on a site at the same time. Everything else is smaller fixes and behind-the-scenes work.
For all users
- A running task and a site check-in can’t overlap. If you have a task running on the Job Dashboard, FSManager won’t let you check in on a site job. If you’re checked in on site, it won’t let you start a task. Whichever you try second, a short message tells you which job you’re already on. Both were claiming the same hours, so the time showed up twice against two different jobs. To move between them, check out or stop the task first.
- You find out before you’re asked about unclaimed time. Previously you could answer how to account for the last few hours and only then be told you couldn’t start at all, losing the answer you had just given.
Fixes
- Maintenance: Send Documents now prepares the email. It saved the paperwork to Attachments but stopped short of drafting the covering email, because there was no default maintenance email template. There is now.
- Dark mode: some pop-ups were showing up white. The delivery scheduling dialog, the site work check-in and check-out dialogs, and the full-screen attachments view now follow your theme again. Light mode was never affected.
- Setting up a new site is more reliable. A single duplicate entry in your supplier catalogue no longer stops the whole load, and double-clicking the button can no longer run the setup twice.
Behind the scenes
- Better monitoring, so several kinds of problem now raise an alert instead of failing quietly. Nothing you see changes.
- Groundwork for maintenance job costing. It isn’t switched on and isn’t part of your plan today.
1.1.3 — 3 September 2026
Mostly behind the scenes. If your password doesn’t work the first time you sign in after this update, see the first item. One sign-in sorts it out.
For all users
- Your stored password is protected by a much stronger method. FSManager never stores your actual password, only a scrambled version, and the scrambling is now much harder to attack. Passwords scrambled the old way can’t be checked by the new method, so the first time you sign in after the update your password may not be accepted on your company’s own sign-in page. If that happens, sign in at
app.fsmanager.co.nzwith the same password you always use. It will work there, and that one sign-in re-secures your password with the new method. After that your company’s sign-in page works normally again. You don’t need to change your password or contact anyone. - Selection fields look a little different. Fields where you pick from a list, such as a customer, supplier or staff member, show their value as plain text until you click into them. Then they open as a dropdown as usual. Pages with many of these fields also open noticeably faster.
Behind the scenes
- General speed and memory improvements, most noticeable on screens with large toolbars or long lists. Signing in, moving between screens and opening records are all faster.
- A fix to our own monitoring of the demo site’s overnight refresh. No effect on customer sites.
1.1.2 — 2 September 2026
A maintenance patch. Nothing changes on screen and there is nothing you need to do.
Behind the scenes
- The framework upgrade listed under 1.1.1 is now in place. It was briefly rolled back after 1.1.1 shipped. Both causes have been fixed and the upgrade has been verified end to end before going live again.
1.1.1 — 1 September 2026
A maintenance patch. Nothing changes on screen and there is nothing you need to do.
Behind the scenes
- Dates and times no longer depend on a server setting. Everything FSManager displays is New Zealand time, and now stays that way however the underlying servers are configured. Nothing was wrong before — the setting was correct — but correctness no longer rests on it.
- The platform moved to the current long-term-support version of its underlying framework, ahead of the previous version’s end of support in November 2026. No functional change.
- Updates deploy more cleanly. An update can no longer leave a previous version still running behind the scenes.
Help and feedback
Questions about anything in this release, or something not behaving as described? Email support@fsmdevelopments.co.nz.
Related
- Who can claim which tasks — the full guide to the new rules
- Job Settings reference
- Branches, Departments & Positions