Tightknit Release Notes (Apr 14, 2026)

Content resource library page redesign - The content library on the companion site now has a dedicated Resources page that lists every content resource across every collection, so members don't have to drill into each collection one at a time. Collections still live at their own /collections route and link to the new flat Resources view.

Fixed spacing between post headers - Posts authored from the site now render proper vertical spacing around headings instead of collapsing them into the surrounding paragraphs, matching how they look in the editor.

OG preview images now use a consistent canvas - Home and feed pages with custom banner images now render their Open Graph preview image on the standard 1200x630 canvas, so Twitter and other platforms no longer truncate them.

Fixed AI title generation - AI-suggested post titles had been failing since April 8 after a dependency upgrade. Title generation is back up and running.

Auto-slugify Content Collection slugs - When creating a new Content Collection, the slug field now auto-fills from the collection name as you type, until you customize it yourself.

Full audit trail for Slack post and comment edits - Editing or deleting a Slack message that is synced to the site now produces the same activity log entries (and preserves the same version history) as edits made on the companion site. Moderators can track edit and delete actions via activity logs in the Studio.

Featured Groups button replaced with per-group visibility - The standalone Featured Groups button is gone. In its place, every Group now has a Companion Site Visibility setting inside the Edit Group modal, so you control surfacing on a per-group basis alongside the rest of that group's configuration.

New deactivate member API endpoint - You can now programmatically deactivate a member so they can no longer log in or participate. Currently available for Tightknit-only members.

New API key introspection endpoint - GET /admin/v0/api_key/me returns the authenticated API key's type, associated community, and granted permissions. Helpful for debugging 403s and for integrations that need to reason about their own scope.

Clearer 403s when an API key is missing a scope - Permission-gated admin endpoints now return a structured INSUFFICIENT_SCOPE error that lists the required permission alongside the caller's granted permissions, so you can diagnose scope issues directly from the response.