Skip to content

Meetings

Who can read a meeting transcript?

It is the right worry: a meeting that gets written down becomes readable. Our answer is five rules — and two exceptions we state plainly.

5 min read

The right objection

"If every meeting is recorded and transcribed, can anyone in the company read the salary negotiation, the partner meeting, a client's unfinished sentence?" The objection is correct, and the answer cannot be "trust us". The answer has to live in the architecture.

The rest of this platform is deliberately one shared pool — that is what organisational memory means. Meetings are the one place that rule is deliberately broken, because a word-for-word transcript is a different kind of thing: evidence, not a summary.

Five rules

The access rule, in order of importance

  1. 1. Born restricted

    From its first moment, the transcript is readable only by the meeting's access list: the participants, and anyone later explicitly invited. Opening it to the whole workspace is a deliberate decision only the organizer or an admin can take — never the default.

  2. 2. To everyone else, it does not exist

    Someone off the list does not get "access denied"; they get "not found" — the same answer a wrong address gets. For a meeting only the partners should know about, even confirming it exists is a leak.

  3. 3. Search and the assistant see with your eyes

    A restricted meeting never appears in an unauthorised search result, and when the AI assistant searches on that person's behalf, it does not even know the document exists. There is no back door through "ask the bot".

  4. 4. Access is a ledger of disclosure

    Every grant is recorded with who gave it, and the ledger only grows — leaving the meeting never takes back the history of what someone has read. Who can grant? Only someone already on the list, or a workspace admin.

  5. 5. Two exceptions, stated plainly

    A workspace admin can always read — hiding things from the organisation's owner is not a feature, it is a risk. And on the other side: platform staff can never see restricted content; our support console has no route to content at all.

Why everything else stays open

Feeds, engagement status and weekly summaries deliberately stay open to the whole workspace — they are the firm's shared record, and closing them would bring back exactly the organisational forgetting this product exists to fix. The line sits precisely at word-for-word evidence: everyone sees the summary of the work; the recorded voice of the room, only the people it belongs to.

Common questions

  • Can a granted access be revoked?
    Not currently, and that is deliberate: the access ledger is a record of disclosure, and records don't get erased. Someone who has read a transcript has read it. If revocation is essential for your organisation, raise it in the deployment conversation.
  • Can a guest from outside the company read the transcript?
    Being in the meeting needs no account — a participant comes from the contact book. But reading the transcript in the platform does need one; an attendee without an account is on the participant list, not the reader list.
  • Do these rules hold on a self-hosted deployment?
    Yes — the rule lives in the software, not in the cloud service. And self-hosted, the audio and transcript never leave your network either.

Try it on your own data

The free plan has no time limit. Bring the hardest document you have.

Start freeCRM buyer's guide