🔔 Choose What Your Slack Team Gets Notified About
You can now customize which notifications your team receives in the Tightknit Hub channel in Slack. In the Studio settings, admins can toggle alerts for a number of different admin operations and events in the community, including:
New user joined
Award received
Journey completed
Channel activated
Poll created
Group created
Journey created
Award created
Content collection created
Content resource created
Tag created
Tag group created
Milestone created
Member added
Site created
Feed created
This gives admins the power to switch off whatever is noise for your team and keep the alerts that actually matter. You can update your notifications at https://studio.tightknit.ai/~/integrations/slack#notifications.
⚠️ Upcoming Change (8/12): Standardized Site Banner Dimensions
We will be standardizing our page banners on the community site to use a 4:1 shape and have updated the recommended dimension in the branding guide. This is a part of an effort to standardize the aspect ratios and support larger images. ⚠️ Existing banners using the previous dimensions will be slightly cropped on the sides. Please re-export at 2560 x 640 for the crispest result. The cut over will be performed for next release on 8/12/2026. The following images are affected: Home page banner, Events page banner, Groups page banner, Content Library page banner, Feed page banners. You can update these settings in the Studio or through our MCP server.
👥 Add Members To A Private Feed From Studio
Private feeds keep a conversation limited to the right people, but until now the only way for members to join was by joining the corresponding private channel in Slack, leaving out the community site-only users out of the party. Now, admins can also add site-only community members to a private feed, from the feed's page in Studio; someone who only uses your community site can take part without ever joining Slack.
Private feeds are available to Enterprise customers in our pilot. Interested in joining? Leave a comment in the thread.
🛠️ Improvements and Fixes Community Site
Upcoming change (8/12): Sharper, standardized page banners - Starting 8/12, every page banner will be switched to a 4:1 shape, and the community site will utilize a full-resolution variant. ⚠️ Existing banners may be cropped slightly at the sides to fit, so it is worth checking on yours. Re-export at 2560 x 640 for the best result.
RSS feeds no longer resurface old posts - Your feed's RSS output is now ordered and dated by when content was actually written rather than when the row was last updated, so manual actions of publishing to the site will no longer float old posts to the top with fresh dates and make connected readers re-announce them as new. One reshuffle occurred as the new ordering takes effect.
Studio
Site-only discussions in the Discussions list view - Fixed a bug where a site-sourced post wouldn't show up in the Discussions list view table.
Honest delete warnings for content - The delete-collection dialog now describes what actually happens, and deleting an event correctly removes the library card pointing at it instead of leaving a dead resource object behind.
Bots stay out of event people pickers - Every bot type is now filtered out of the host, speaker, and attendee selectors on an event.
Slack
⚠️ Deprecating the /tightknit-poll command - Polls are now created with /poll only. The duplicate alias /tightknit-poll shortcut has been removed.
Bugfix: profile picture milestone on member join - Fixed bug where milestone progress may not award progress to members who joined the workspace with a custom avatar.
MCP
New deletion tools - New MCP delete tools added for groups, group members, events, journeys, milestones, awards, content collections, content resources, and tags. Each destructive tool requires an explicit confirmation before it runs.
Codex / ChatGPT web client connection - Fixed a bug where the ChatGPT web client failed to connect to the MCP due to mismatch in oauth protocol versions.
Hey folks, a quick note on an RSS feeds malfunction yesterday.
If you have a Slack channel connected to a Tightknit RSS feed, you may have seen a batch of older posts arrive overnight as though they were just published. This was an oversight on our part during an internal data migration. We apologize for the noise. Nothing in your community changed. No posts were duplicated, edited, or lost.
What happened: our feeds originally ordered and dated posts by when the record was discovered by the site, rather than when the post was originally published in slack. While migrating to a more robust platform for posts & comments we shifted the internal timestamps, and that made old posts look brand new to feed readers.
