Tightknit Release Notes (July 1, 2026)
🧱 Richer Slack Layouts, Now In Your Community
Slack recently introduced new Block Kit layouts: containers, cards, carousels, and tables, for richer and more visual messages. Tightknit now fully supports these newer layouts, so any Slack post built with them renders correctly on your companion forums site, with its text, links, and mentions captured so the content stays fully searchable. Whether a message uses a swipeable carousel, stacked cards, or a data table, your members see it the way you see it in Slack.
🛠️ Improvements and Fixes Companion Forums Site
Search perf improvement - Optimized performance of most searches.
Search Result tabs fix - Fixed a bug where Resources tab may be shown for filtering even when content resources are turned off for the site.
Studio
Members list shows full names - The members list and CSV export now additionally show each member's Full Name and slack Display Name columns.
Members Export button fix - The Export button no longer disappears on narrower screens, and a new Cmd+K action lets you export the members CSV from anywhere in Studio.
Datatable display columns button fix - Fixed a bug where the column display configuration button was not appearing over data tables.
Slack
Redesigned Community Home for members - The non-admin Slack App Home has a fresh layout. Upcoming events, awards, and achievements appear in carousels and cards.
Configure Your Feed prompt clears after you finish - The feed setup onboarding prompt no longer lingers with stale buttons after you configure it or skip the step.
Salesforce Integration 1.8.0.1
Setup: assign the Tightknit Users permission set - Step 1 of the Salesforce Setup wizard now includes an optional step explaining how to grant end users the read-only Tightknit Users permission set group, so they can see Tightknit data on Contact and Account record pages.
Component permission warnings - the LWC components now warn users they lack permission to see data if they do not have access to the underlying objects, instead of displaying a "no data" state.
