Twenty keeps chats share-only until private records are enabled

Twenty's sdk/v2.55.0 release keeps chats share-only while private records are disabled.

weekcrm news desk · 3 November 2026, 13:23 UTC · Source: github.com

Twenty's sdk/v2.55.0 release keeps chats share-only while private records are disabled. The fix addresses a bug in v2.54.0, where a Member could read other members' chat threads. The source reports that a Stage Member saw 18 chats on production right after deploy, not only their own 4.

The fix applies while the IS_PRIVATE_RECORD_ENABLED setting is off. Private-by-default objects, including chat threads, are now checked by the permission logic, and inserts follow the same rules. In the source's reproduction, the same member now sees 4 chats and a denied read on the others.

What it means

If you use Twenty. Chats in Twenty stay visible only to their owner and users they share with while private records are off.

What to do. After upgrading to 2.55, check that members see only their own and shared chats.

Watch for. Re-test chat access when you turn on private records, since this fix applies only while the setting is off.