Back to the changelog

v0.88.6

September 23, 2026

**Restricted folders stay restricted, always.** Removing the last access rule no longer reopens a folder to everyone, the side doors flagged by the security audit are closed, and an activity log that fails to write now stops the operation instead of pretending it succeeded.

  • Security

    A restricted folder no longer reopens by accident

    Until now, removing the last access rule from a folder (even just because a colleague left the company) made the folder visible to everyone again. It now stays restricted: with no rules, only administrators can see it, and reopening it to everyone is an explicit action, with confirmation and an entry in the log. Folders that already had rules have been marked as restricted automatically.

  • Security

    The side doors are closed

    Features that read flows through secondary routes, such as related cases, the browser extension, map analyses and comparisons, saved templates, operating guides, event usages and assignee reconciliation, now follow the same folder visibility rules. If you cannot see a flow, you cannot see it anywhere.

  • Security

    The activity log no longer lies

    When writing to the activity log fails during a sensitive operation, such as a legal hold, deleting a case or correcting a closed task, the operation is now cancelled with a clear error instead of replying "done" while leaving no trace. This also applies to login attempt protection.

  • Improvement

    On iPad and in Settings

    Vertical scrolling on Chrome for iPad works again on every screen; the Settings icon is now a gear; switching section in Settings starts the page from the top.

  • Improvement

    Dependency maintenance

    The build components flagged by security advisories have been updated in a targeted way, without changing the frameworks. The automated check now also covers development dependencies.