Settings, operations & compliance
Software updates
On a managed deployment the software keeps itself current. The deployment checks in with Naxis every quarter of an hour, and when a new version is announced a Software updates card appears at the bottom of Settings → General — when nothing is waiting, there is no card and nothing to do. The card only shows on managed deployments in the first place; it's absent by design everywhere else.
| When it installs | Automatically, on the coming Sunday at 02:00 in the deployment's own local time — unless you pick an earlier moment or press Update now. Each update also carries a mandatory-by date: the picker refuses anything later, so an update can be brought FORWARD to any time you like, never postponed past that date. Update now hands the release to the updater, which picks it up within a minute or two. That's how every deployment stays on supported, patched software without anyone having to remember to click anything. |
|---|---|
| What it feels like | The assistant is unavailable for a few minutes while the update applies, and the card reads “Installing now”. If an error page appears during that window, wait ten minutes and open it again. |
| Your data | Documents, settings, users and history are untouched. A backup of the database is taken before every update and kept — the last five are retained — and if the backup itself cannot complete, the update is not attempted. |
| If an update fails | A release that cannot be downloaded leaves the assistant running on its current version. A new version that fails to start, or does not come up healthy within five minutes, is rolled back — the previous version is brought back and the card says so in plain words, never in technical detail. The update retries by itself after a quarter of an hour, or press Retry update now. |
| What changed | The card shows the release's own notes next to the installed and available versions. |
| Who is told | When a release is booked, every administrator with an email address receives one message — the version, the moment it installs, the notes and the mandatory-by date — provided email is configured. |
A newly announced release is booked onto the coming Sunday the moment it appears, and that date is pinned as the release's own deadline; Naxis can set an earlier one for an urgent release, and the earlier date wins. Picking another moment in the scheduler never pushes the deadline itself, it only moves your own install earlier within it — and once the deadline has passed, the update simply installs at the first opportunity, with no date left to choose.
Self-hosted deployments outside the update channel, with no licence link of their own, show no card; updates there follow whatever process you put around it.
Last updated 20 Sep 2026