Hey everyone! I'm pretty new to Fireflies.ai, and I've been using it to transcribe my client meetings, which has been a game-changer for my notes. I'm still figuring out all the features though.
Here's my situation: I work with several clients on different projects, and I want to share the meeting transcripts with them so we're on the same page. But I don't want to add each client as a "teammate" to my Fireflies account—that seems messy, and I don't need them to see all my other meetings or have any sort of login.
Is there a clean way to share just a specific transcript? I see there's a "Public link" option when I look at a note. If I share that, can the client only see that one transcript? Can they download it or comment on it without me having to invite them properly?
Also, if there's a better way to handle this, maybe even using a Notion or Asana integration to share the key parts, I'd love to hear how you all manage it. I just want it to be simple and secure for the client.
Thx!
I'm a consultant running a one-person shop, and I handle all my client meeting transcripts with Fireflies before sharing them out.
Here's a breakdown of the sharing options you actually have:
1. **Public Link Access:** Yes, it shows only that one transcript. Anyone with the link can view the full transcript, the audio, and the AI summary. They can add comments and highlights **without an account**, which is perfect for client feedback. They can also download the transcript as a text or SRT file.
2. **The Security Catch:** That public link is not password-protected. If someone gets the link, they have access. I only use this for low-sensitivity client calls. For anything with an NDA, I avoid it.
3. **The Organized Alternative (Notion/Asana):** I use the Notion integration for high-touch clients. The transcript exports as a clean, readable page in a shared client workspace. This lets me keep all project docs together. Setup takes about 10 minutes to connect Fireflies and set the Notion destination.
4. **The Manual Control Method:** For full control, I download the transcript as a text file and paste the relevant sections into a project email or a shared Google Doc. It's an extra 2-minute step, but there's zero link-sharing risk and I can edit out any off-topic chatter before sending.
My pick is the **Public Link** for most cases. It's the fastest and clients like the interactive player. If your meeting contains sensitive business or personal data, go with the **Manual Control Method** to be safe. To decide, tell us if your contracts require strict confidentiality and how tech-comfortable your clients are.
Containers are magic, but I want to know how the magic works.
You've identified the core feature correctly. The public link does indeed provide view-only access to that single transcript, and clients can comment or download without any login, which solves your immediate problem.
However, the security model for that link is a critical consideration user58 mentioned. It operates on a "shareable secret" principle. Once generated, that link is a static access token. If a client forwards it, or if it's indexed by a search engine, the transcript is exposed. For routine project updates, this is often fine. For discussions involving sensitive data, it's a genuine risk.
You asked about a "better way" using integrations. The workflow I've settled on is using Fireflies' Zapier integration to push transcripts to a client-specific Google Doc. The automation creates the doc, applies a template, and shares it only with that client's email via Google Drive's permission system. This gives you audit trails and revocable access. It's a few hours to set up the Zap initially, but it scales cleanly across multiple clients without them ever touching your Fireflies workspace.
Oh okay, so the public link does just show the one transcript. That's great to know, and the comment/download thing is perfect for what I need.
The security part makes me nervous though. A link someone could just forward... yikes. I'm not usually talking top secret stuff, but still.
I'm curious about that Zapier to Google Doc idea user1205 mentioned. Is that something you can set up to run automatically for specific clients? Or do you have to trigger it manually each time? I'm trying to avoid extra steps per meeting.
Containers are magic, but I want to know how the magic works.
The Zapier automation can be fully automatic, but it depends on how you trigger it. If you set it to fire for every new transcript, you'll need a way to route it, like using the meeting title to match a client name and a specific Google Drive folder.
An even simpler workaround is to use the built-in "Send to Email" action after the meeting. You can send the transcript as a PDF directly to your client's inbox without a public link ever being created. It's not as interactive for comments, but it avoids the link-forwarding risk entirely.
null
Yeah, the public link is the easiest way for exactly what you described - it shows just that one transcript, and they can comment or download without logging in.
But since the security bit makes you nervous, I'd split your approach based on sensitivity. For general project syncs, the public link is fine. For anything confidential, I use the "Send to Email" as a PDF like user443 said. It's one click after the meeting and it lands right in their inbox, no link to forward.
If you do want to use an integration for the "better way" you mentioned, the Notion one is pretty clean. You can set a rule to auto-add transcripts with a specific keyword (like the client's name) to a shared Notion page. They get a nicely formatted page, and you can lock down the sharing on Notion's side.
The Notion workflow works until your client's security team bans Notion.
If you're worried about link forwarding but want something more durable than a PDF in an inbox, generate a unique public link and then password protect it with a simple tool like Privnote. You send the password separately. It's clunky, but it makes the shared secret model explicit.
Prove it.
You've nailed the core use case for the public link. It does create a single-access, view-only page for that transcript where clients can comment or download without logging in.
But I need to push back slightly on the security framing others have used. Calling it a "shareable secret" undersells the risk. It's a static URL that, if compromised, provides persistent access. The real vulnerability isn't just a client forwarding it, it's that the link could leak from your own email or messaging system. For true confidentiality, the "Send to Email" as a PDF is statistically safer because it's a one-time delivery with no persistent access point.
The integration method to Notion or Asana is viable, but adds complexity. You're now managing permissions in two systems, not one, and the failure modes multiply. Simple often wins.
p-value < 0.05 or bust
You're right about the static URL being the real risk, but the PDF-by-email solution creates its own audit trail problem. Now you've sent a static document to an inbox you don't control. If you ever need to recall or update that transcript, good luck.
The failure mode for integrations is real, but the bigger issue is that you're just moving the permission problem downstream. Now Notion's "Anyone with the link" setting becomes your new security vulnerability.
Data over dogma.