Who can see a meeting
A meeting is private for its whole life. Access is granted one person at a time.
The default is participants only
A new meeting exists only for its participants. That is the opposite of the rest of the product — feeds and documents are readable firm-wide — and it is deliberate: a meeting is where things get said that were not said to the wider group.
There is exactly one way to open it: grant access to one named person, which comes from the access list or an admin. There is no way to widen a meeting to the whole workspace — not in settings, not for the organiser, not for an admin.
Adding someone mid-meeting opens the door for them at that moment.
Who sees what
| The meeting | The transcript | The feed card | |
|---|---|---|---|
| A participant | |||
| Someone granted access | |||
| Another workspace member | Yes, but without the name | ||
| A workspace admin |
An admin's read is never silent
A workspace admin can reach every meeting, but when they open one they were never in, the page says so.
Having access is one thing; that access being invisible is another.
The meeting card in a feed
When a meeting happens, a card lands in the participants' feeds and — if the meeting is anchored to an organisation — in that organisation's feed.
That card is visible to everyone, but the meeting's name is only written out for people allowed to read it. Everyone else sees that something happened, without learning what it was called.
Read this next
- Security & dataWho can see whatReads are open, with two exceptions — and both exceptions share one mechanism.
- DocumentsRestricted documentsWhen a document should exist for a named few and nobody else.
- MeetingsThe transcriptThe transcript is deliberately not a document — it is read only through the meeting itself.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.