Changelog#

Changes to this documentation. Newest first.

2026-08-21 — English version#

The documentation is now available in Norwegian and English. Norwegian remains the default; switch language in the sidebar.

2026-08-17 — Several disciplines per user#

A user can now be linked to several disciplines: one main discipline plus up to four more — five in total.

  • The main discipline still governs time registration — that is the rate used
  • The other disciplines govern what the user gets to see

If permissions are set so a user only sees work orders for their own disciplines, they now see work for all the disciplines they’re linked to. That makes it possible to handle people who work across trades without giving them full visibility.

Described in Users and permissions and Access and roles.

Version 1 — 2026-08-16#

The first edition of the documentation. Built on the user guide, internal clarifications, and a walkthrough of Carrotz as it actually looks.

Structure — two tracks by role:

  • Getting started — what Carrotz is, terminology, desktop and mobile, installing the app, access and roles
  • For field users — home screen, finding and carrying out work orders, one-off jobs, deviations and cases, the app in the field, good practice, clocking
  • For administrators — locations, objects, checklists, maintenance plans, measuring points and triggers, users and permissions, JSA and risk assessment, documents and signing, planning/projects/hours, reports and statistics
  • Quick reference and Frequently asked questions

Key things documented:

  • The work model — a work order consists of tasks, and a checklist task consists of sub-items. Each task is tied to either an object or a location
  • Statuses — Registered, In progress, Completed and Cancelled, plus Awaiting approval, Approved and Rejected when approvals are enabled
  • Work types — preventive, corrective, internal control, condition check and one-off job
  • Completion rules — how they are set as defaults and overridden per maintenance plan
  • JSA — must be completed before a work order can be started, and is valid for 24 hours
  • User types and permissions — Admin, Superuser and Regular user, with granular permissions by domain
  • Departments — access to several, but one at a time
  • Risk assessment — P × C = R before and after actions, revisions with validity dates, approval with signatures
  • Installing the mobile app as a PWA, since it isn’t in the App Store

Screenshots: the first ones are taken from the demo environment. Pages without an image show an orange placeholder with the expected filename.

How to record changes here#

Put the newest at the top, with the date as the heading. Write what changed for the reader, not what changed in the files — “Added an explanation of criticality on objects” is more useful than “updated objekter.md”.

Gather several small changes into one entry rather than recording each individually.

Backward Frequently asked questions