
Studio Sections
The Studio interface is organized into the following sections:- Overview: Analytics and charts about your community’s performance and engagement
- Members: View and manage community member profiles
- Discussions: View discussions with the community
- Website: Monitor companion site traffic and performance
- Activities: Monitor user activity feeds
- AI Insights: AI-powered analytics about your community’s conversations
Members
Use Members to search, filter, and manage your community members.Discussions
Use Discussions to view and monitor Slack messages from your activated channels. You can search messages by content or author, filter by specific channels, and sort by newest or oldest messages. Click a message to view the complete discussion thread with participant insights.
Activities
Use Activities to track all community interactions in a chronological feed. You can search activities by content or participant, filter by activity type, and sort by newest or oldest activities. Click any activity to view the full discussion.
Website
Use Website to monitor your companion site traffic and performance. You can view visitor counts, pageviews, bounce rates, and geographic data. The dashboard shows traffic sources, page performance, and device analytics to help you understand how your companion site performs.
AI Insights
Use AI Insights to surface and act on the most important patterns and signals within conversations in your community — emerging topics and themes, predictors of low and high engagement, questions members are repeatedly asking or that go unanswered, and other insights that can help shape programming, content, FAQs, moderation, and product feedback.AI Insights is currently in open pilot.
Cmd+K Command Menu
Press Cmd+K (or Ctrl+K on Windows) from anywhere in the Studio to open the command menu. Use it to quickly navigate to any page, search for members, or perform actions like creating a new event or content resource.Limitations
- The join date of members that joined the community before Tightknit was installed may not be accurate. In these scenarios, the join date may be reflected as the date Tightknit was installed.

