v0.83.3
August 17, 2026
A security-focused update. Two-step verification for administrators, secure one-time alert confirmations, stronger and rotatable at-rest encryption, sign-in links and keys kept out of logged URLs, and less sensitive data retained in history.
-
Security
Two-step verification for administrators
Admin and SuperAdmin accounts can now protect themselves with a second factor (a TOTP authenticator app), with recovery codes and guided setup. Where the installation sends email, verification becomes mandatory for these roles. Sign-in is never completed before verification, and enabling it ends sessions opened with password only.
-
Security
Secure one-time alert confirmation
The "acknowledge" links in alerts now use a unique, random, expiring token: each recipient gets a different one, the first confirmation deactivates the others, and the link can no longer be reused or triggered by mistake by scanners or previews.
-
Security
Stronger, rotatable encryption of sensitive data
Credentials and sensitive data at rest use a new encrypted format with a key identifier and random values for each record, allowing key rotation without losing access to earlier data. The old fallback to unencrypted data has been removed.
-
Security
Sign-in links and keys kept out of logged URLs
Password reset, sign-in link, and federation invite links carry the code in a part of the address that is never sent to servers, proxies, or logs. MCP integration keys are passed only via header, no longer in the address.
-
Security
Less sensitive data kept in history
Item history snapshots are minimized before being saved: fields declared sensitive are already redacted in the database, not just on screen, reducing exposure in backups and copies.
-
Improvement
Stricter filters and searches
List filters (items, tasks, automations, templates, assistants) validate names, values, and dates uniformly: an out-of-range or duplicate parameter is clearly rejected instead of silently widening results. Guides linked to processes flag inconsistent references as "broken" rather than hiding them.
-
Integration
Safer integrations by default
In production, requests from other sites are blocked unless explicitly authorized. New MCP keys have a default expiry, and connected automations (including n8n) run with tighter boundaries and separate credentials.