# Version 4.1.6

> Change logs general updates and new features (Change logs)

- Page: https://dashboard.nizu.io/knowledge_base/view/286-version-4-1-6
- Part of: [Knowledge base](https://dashboard.nizu.io/knowledge_base/llms.txt) on NIZU — https://dashboard.nizu.io/llms.txt
- Updated: 2026-10-25T11:50:03Z

Change Log

---

| ## 4.1.6 | #### 30-08-2026 |
| --- | --- |

**New**

- Support tickets are now available to your AI: it can list what is open, read a ticket with its whole conversation, open new ones, assign them, change their status and report on how support is doing. Replies default to an internal note, so nothing reaches a customer unless you ask for it.
- Your AI can search your knowledge base before answering, so it uses what your team has actually written down. It can also look up the workspace's own lists — VAT rates, payment methods, labels, ticket types and more.
- Notes and announcements are now available to your AI. A note it writes is private to you unless you say otherwise, and an announcement always asks who it is for rather than assuming the whole team.
- Your AI can now see and add to your calendar, and manage your to-do list — add items, tick them off, and put them back. A calendar entry it creates is private to you unless you ask for it to be shared.
- Your AI can now draw up contracts and list the ones you have. A contract is created as a draft with its client-facing link ready, and it asks you when the contract runs out rather than guessing.

**Updates**

- The database update for this release is now safe to run more than once. Every schema step checks whether it has already been applied, so re-running an update can no longer stop partway or alter a workspace that was already up to date.
-

**Fix**

- Fixed database updates that could quietly lose data on re-run: two settings storing a list of allowed values (item types, and label categories) were being reset to an older, shorter list, discarding items or labels that used a newer value. They are now left untouched unless the change is provably safe.
- Hardened how your AI reads OrderLemon data: filters and sorting can no longer be used to reach sensitive fields like payment tokens or bank details, even indirectly.
- Expense and support reports now say when records have no date on them. Those entries belong to no month or year, so they never appeared in a period total — on some workspaces that is a large share of the value, and it is now stated rather than silently left out.
- Support tickets that were never closed no longer carry a closing date of their own. They previously stored an empty zero date, which would have counted as a real closure in any report on how long tickets take to resolve.

**Deprecated**

-