Summary
Extend meeting recording and conversation‑intelligence connectors (including custom connectors) to respect participant‑level access, so any entitled meeting attendee can discover and use call recordings and transcripts in Glean, not just the meeting host/recording owner.
Description
Organizations often connect meeting‑recording or conversation‑intelligence tools (e.g., Zoom, Teams, Gong, Chorus-like platforms) into Glean via native or custom connectors. These tools typically store recordings and transcripts under the account of the person who scheduled or “owns” the meeting (e.g., the host or whoever clicked “Record”), even though multiple other participants are granted view access in the source system.
In Glean today, indexed recordings/transcripts are often effectively visible only to that “owner” account, particularly for custom connectors that attach permissions to a single owner or service account. Participants who can open and listen to the same recording in the source system frequently cannot retrieve or reference that content in Glean search or chat, even when they explicitly ask for it. This creates a confusing mismatch: users know they can see the call in the source tool, but Glean either does not surface it or answers without using that content.
For custom or semi‑custom connectors that index meeting recordings, the default permission model tends to be built around the connector service account or content owner rather than the full set of entitled viewers/participants. This breaks the intuitive expectation that “if I can see the recording in the source system, I should be able to search and use it in Glean.”
This feature request is to introduce a participant‑aware access pattern for meeting/call connectors (including custom connectors) so that Glean can mirror the true set of entitled viewers instead of only the owner.
Customer Use Case(s)
- A user participates in many internal and external calls whose recordings are stored in a meeting‑intelligence / call‑recording platform.
- In that platform, the user has permission to view and listen to recordings that they did not personally schedule or host (for example, calls run by a colleague or recurring team meetings).
- They want to use Glean search and chat to:
- Ask questions like “What did we agree on in last week’s onboarding call with <customer>?” or “Summarize my last three calls with <customer>.”
- Quickly find the appropriate recording even when they were only a participant and not the organizer.
- Summarize calls, extract action items, and pull key details from the transcript directly in Glean.
Today, only the rare recordings that the user personally owns (e.g., the few Zoom/Chorus/other calls they themselves scheduled and recorded) are reliably discoverable in Glean. Other recordings they can access in the source tool are invisible or unusable in Glean, which:
- Makes it difficult for non‑hosts (e.g., individual contributors, cross‑functional partners) to rely on Glean for meeting recaps and follow‑ups.
- Causes users to distrust Glean’s coverage of meeting content (“Glean doesn’t know about my calls”).
- Forces users back into the source call‑recording tool any time they need to review a call they didn’t host.
A generalized participant‑aware permission model for meeting connectors would allow any attendee with view rights in the source system to discover and leverage that content in Glean, regardless of who technically owns the recording.
Business Impact
- Improves knowledge reuse from meetings: attendees can reliably find, summarize, and act on calls they actually joined, not just those they hosted.
- Reduces confusion and support tickets where users can see a recording in the source system but not in Glean.
- Increases productivity for sales, customer success, support, and internal project teams who depend on call recordings to track decisions, action items, and context.
- Encourages centralizing meeting‑related workflows (summaries, follow‑ups, Q&A) in Glean instead of fragmenting them across multiple tools.
