Who can actually see your AI meeting notes? A guide to locking them down by default

In most AI notetakers, meeting notes default to org-wide or share-link visibility, so colleagues can often see them without you sharing. Reline is private-by-default: a workspace role alone grants zero access to any note or recording. Every viewer needs an explicit grant, and web-publishing is a separate, deliberate action.

Who can see your AI meeting notes is decided by one architectural choice your tool made before you ever clicked record. There are two camps. Visible-by-default tools open a note to your whole org, or mint a share link that works for anyone who holds it, the moment the meeting ends. Private-by-default tools — Reline among them — require an explicit grant before anyone but you can see a thing. Same recording, opposite blast radius.

This is not a theoretical preference. The stakes are the most sensitive conversations you have: 1:1s, performance reviews, layoff planning, legal and HR matters, client and vendor calls, and fundraising discussions. With a visible-by-default tool, those notes are discoverable by default and locked down only if you remember to act. With private-by-default, the secure state is the resting state — you have to deliberately open access, not deliberately close it.

Visible-by-default comes in two flavors, and both are designed for frictionless sharing — which is exactly why they backfire on sensitive content.

In this model, every note you create lands in a shared space your whole org or workspace can browse and search. Nobody has to send you a link; a colleague just opens the notes directory, types a name, and your 1:1 transcript surfaces. It feels collaborative until the content is a candid review of a teammate or a number you discussed with one investor. The note was never "leaked" — it was always reachable, and you simply never narrowed it.

Here, finishing a meeting generates a link that works for anyone who has it — no login, no membership check, sometimes no expiry. This is the failure mode that lands AI notetakers in the press: meeting recaps and transcripts indexed by search engines or forwarded one hop too far, exposing private calls to strangers. An AI notetaker whose notes are effectively public by default turns a single careless paste into a data incident.

These defaults exist for a reason — they remove friction, and for a low-stakes status sync that is genuinely convenient. The problem is that the tool applies the low-stakes default to every conversation, including the ones where the cost of over-sharing is someone's job, a contract, or a regulator's attention. Convenience that you cannot opt out of is a liability.

Private-by-default means a note is invisible to everyone but its creator until you explicitly grant someone access. There is no silent reach. Here is exactly how Reline's model behaves, so you can verify it rather than take it on faith.

• A workspace role alone grants nothing. Being an Owner, Admin, or Member of the workspace does not let you open, search, or even discover a note or folder you weren't granted. Role is membership, not a master key.
• Every viewer needs an explicit grant, on every note or folder. Access is something you add to a specific person or role for a specific resource — never something they inherit just by being in the building.
• An "open" teamspace grants Members Edit only. Setting a teamspace to open visibility lets workspace Members edit its content — but Owners and Admins get no silent reach into that content on the strength of their title. There is no "admin sees all" backdoor.
• Web-publishing is a completely separate concept. A public web link is something you deliberately create, and it lives outside normal workspace browsing. No amount of clicking around the workspace surfaces a published page, and publishing one does not change who can see the original note inside Reline.

In short: restrict who can view meeting notes is not a setting you hunt for in Reline. It is the starting condition. Opening access is the action that takes intent.

Role based access for meeting transcripts in Reline is built on grants that attach to a scope. A positive grant flows down to everything inside that scope; the absence of a grant means no access at all — not even the ability to know the resource exists. Read this table as the literal rulebook.

Because grants attach per scope, you can split visibility along the exact line your situation requires. A common pattern: publish the AI summary to the team so everyone gets the decisions and action items, while the raw recording and full transcript stay grant-only for the two people who were on the call. The team gets the outcome; the unedited source never leaves the room.

Use the three tools deliberately:

1. Reach for a folder when one group needs everything inside a body of work — for example, a per-client folder that no other account team can reach. Grant the client's pod access to the folder once, and every note inside inherits it; everyone else gets nothing, including discovery.
2. Reach for a teamspace when a standing group collaborates continuously and you want shared editing to be the norm for that group's content — an open teamspace gives its Members Edit without per-note grants.
3. Reach for a web-publish link only when you intend something to be readable by people outside Reline entirely — a public changelog or a customer-facing recap. It is the one path that puts content on the open web, and it never touches the visibility of the source note.

You should never have to guess. To confirm who can see my AI meeting notes for any given note, do three quick checks.

1. Open the note's share panel and read the explicit grant list. This is the authoritative answer for the note itself — every name and role with access is listed, along with whether they can view, edit, or share. If the list is just you, only you can see it.
2. Check the parent folder and teamspace for inherited grants. A note can be reachable because someone was granted the folder around it. Walk up one level: if a folder grant exists, everyone on that grant can see this note too.
3. Confirm whether a web-publish link exists. This is a separate state from sharing, so check it separately. If a public link has been created, the note's content is readable outside Reline by anyone holding that URL — revoke it if that isn't intended.

Private-by-default access control is one layer; it works alongside the rest of how Reline captures and records meetings.

• Bot-free capture. Reline records from your microphone and system audio locally on the device — no recorder bot joins the call. Nothing announces to the room that a meeting is being captured, so you control disclosure instead of a third-party bot doing it for you. Transcription itself runs in the cloud on Soniox across 60+ languages, under a data-processing agreement, and your meetings are never used to train models.
• Citation-backed summaries keep the record defensible. Every line of the AI summary links to the exact transcript moment behind it, so a recap you share is one you can verify. The model can still make mistakes, but you can catch them in seconds rather than trusting an unsourced claim.
• Enterprise adds org-wide enforcement. The private-by-default architecture protects individual notes on every plan. For teams that need to prove and lock that posture across the whole org, the Enterprise tier adds an audit log, policy locks, and a DPA — controls for the security-minded buyer who has to answer to more than themselves.

If your team handles 1:1s, reviews, candidate conversations, or anything an employee would expect to stay confidential, the default visibility of your notetaker is a people-and-trust decision, not just an IT one.

Pick a tool where the secure state is the default state. With Reline, locking down sensitive notes isn't a checklist you have to remember after the fact — it's where every note starts.