AI Assistant

The AI Assistant answers questions about your community without you having to build a filter or export a report. Ask it in plain language, and it looks up the answer using the same data you can already see in Studio. It knows which community you’re in and which page you’re looking at, so you can ask about “these members” or “this event” without spelling out what you mean.

​

Opening the assistant

There are two ways in, and both open the same panel on the right side of Studio:

• Click the sparkles icon in the Studio header, next to your profile menu.
• Press Cmd+K (Ctrl+K on Windows) and choose Ask AI Assistant.

The panel stays open as you move around Studio, and your conversation is kept while you navigate. Press Esc to close it, and use the + button in the panel header to start a fresh conversation.

​

What it can do

The assistant can read anything you already have permission to see, including:

• Members and groups — find members, check group membership, look up profiles
• Posts, comments, and discussions — search content, read threads, check what was published
• Events — list events, check attendees and RSVPs
• Journeys, awards, and milestones — check progress and assignments
• Feeds, channels, and tags — see how content is organized
• Site, branding, and content collections — check configuration
• Activity history — see what has happened in your community
• Tightknit documentation — answer questions about how a feature works, with a link to the relevant page

When an answer draws on the documentation, a Sources list appears beneath it with the pages the assistant read. That list is built from what it actually looked up, not from what it wrote — so if you ask how a feature works and no Sources appear, it answered from memory rather than checking, and is worth verifying. Good questions to start with:

• “Which members joined this week?”
• “What were the most active discussions last month?”
• “Who hasn’t completed the onboarding journey?”
• “How do I set up custom fonts?”

​

What it can’t do

If you ask it to make a change, it will explain that it can’t and point you at the Studio page where you can do it yourself. Write access is planned for a future release. Other current limitations:

• One community at a time. The assistant only sees the community you’re currently in. Switching communities starts a fresh conversation.
• Conversations aren’t saved. Reloading the page or switching communities clears the conversation. It is not stored between sessions.
• Long conversations reach a limit. A very long conversation, or one with several large lookups, will eventually stop accepting new messages. Start a new conversation with the + button.
• It can be wrong. Like any AI assistant, it can misread a question or summarize imprecisely. For anything you’re going to act on, check the underlying Studio page.
• Usage is rate limited to protect your community’s performance.

​

Who can use it

Access requires two things:

1. The feature must be enabled for your community.
2. Your Studio role must include the studio:assistant:use permission. Admins have it automatically; other roles need it granted. See Access & Roles.

If either is missing, the sparkles icon and the Cmd+K entry don’t appear. The assistant also becomes unavailable if a workspace’s billing is suspended. Everything the assistant does is checked against your permissions, not a shared service account. If your role can’t see a section of Studio, the assistant can’t see it for you either — a member manager gets member data, but not billing.

​

How your data is handled

Email addresses are redacted. Before any community data reaches the AI provider, email addresses are replaced with [REDACTED_EMAIL]. This means the assistant cannot tell you a member’s email address — you can still find it on the member’s page in Studio. Record IDs are sent as-is. Identifiers like prfl_Ab3dEf6hIj9k are not redacted, because the assistant needs them to follow one lookup with another — finding a member and then checking their group membership, for example. These IDs are meaningless outside your community and are not personal information on their own. Other community content is sent as needed. When you ask about posts, discussions, or profiles, the relevant content is sent so the assistant can answer. It only ever retrieves data you already have permission to view. Community data is treated as information, not instructions. Content written by your members is clearly separated from the assistant’s instructions, so a message containing something like “ignore your instructions” is read as text to report, not a command to follow. Nothing is sent until you ask. The assistant is idle until you send a message; it does not read your community in the background. If your organization has specific requirements about what may be sent to an AI provider, talk to your Tightknit representative before enabling the assistant.

​

Giving feedback

The assistant is in beta and we’re actively improving it. If it gets something wrong, misses data you expected, or you’d like it to do something it can’t yet, let your Tightknit representative know — including the question you asked helps us a lot.