How Fireflies Channels Organize Meetings (Not Privacy) (Full Transcript)

[00:00:02] Speaker 1: Channels turn your meetings into organized, searchable knowledge. A channel is a folder, a way to group related meetings so people can find them later. That's all it does. Think of channels like folders on a shared drive. Sales calls in one folder, customer interviews in another, and recruiting calls in a third. When someone needs something, they know where to look. Here's the question we get most often. Do channels control privacy? No. Moving a meeting into a channel does not change who can see it. The meeting's privacy setting still determines access. This trips up a lot of admins. You create a sales calls channel, add the whole sales team, move a meeting in, and wonder why some people can't see it. The answer? That meeting's privacy is set to only owner, or participants only. The channel doesn't override that. Let me be very clear. Adding someone to a channel does not give them access to every meeting inside. They can browse the channel and see meeting titles. But they can only open meetings their privacy settings allow. If a meeting is set to only owner, adding the whole company to the channel changes nothing. Fireflies gives you three default channels you can't delete or rename. My meetings shows every meeting you hosted or recorded. All meetings shows everything in your workspace you have permission to see. Below these, you create custom channels. Yours to name, organize, and manage. That's where the real organization happens. When you create a channel, you choose public or private. Public channels are visible to everyone in your workspace. Anyone can browse them and access the meetings they have permission to view. Public means the channel is visible. Not that everyone can see every meeting inside. Private channels are visible only to members you add. The channel itself is hidden. Others won't know it exists. Use private channels for sensitive types like HR investigations, legal calls, or board meetings. Same rule applies inside. Meetings still follow their individual privacy settings. A private channel adds organization, not access control. Before adding someone to a channel, look at the meetings inside. If most are participants only, and the person wasn't a participant, they'll see an empty channel. There are a few ways to move meetings into channels. For a single meeting, click the three-dot menu and select move to channel. For multiple, use checkboxes. A bulk action bar appears at the bottom. You can also work from inside a channel. Click add meetings and search. Most companies should organize by team function first. Sales, recruiting, product. Then add topic-based channels as needed. This matches how people think. I need that sales call, not I need that Q3 thing. A structure that works for most teams. Sales calls, customer feedback, recruiting interviews, product research, leadership meetings as a private channel, internal knowledge for all hands and training, and support escalations. Sales calls, discovery calls, demos, negotiations, your revenue team's library, customer feedback, customer interviews, support escalations, feedback sessions. Product and success teams reference these. Start with five to seven channels. You can always add more, but too many up front creates confusion. Channels also connect to rules engine. Create a rule that says, if a title contains demo and an external participant is present, route to sales calls. Or, if the host is in the recruiting group, route to recruiting interviews. Every meeting organizes itself. Manual organization is fine when starting out. Rules engine is how you scale without the busy work. Channels need maintenance. Without it, you end up with sales calls, sales calls to, sales dash old, and three empty channels no one uses. Rename channels when their purpose evolves. Delete unused ones. They create clutter and make it harder to find the right place for meetings. Audit quarterly. Is anyone using this? Are meetings actually going there? Does the name still make sense? Use channels for organization, not access control. Start simple. Connect them to groups and rules engine. Next up, integrations overview.