Conversations beside files
Keep the discussion with the file it explains.
Use a connected channel for each file or folder, discuss reviewed material beside its preview and keep internal comments outside external sharing links.
Feedback is more useful when the file stays identifiable.
A standalone chat message can lose the document it refers to. Drive gives each file and folder a connected communication channel. Colleagues with access can keep discussion close to the material, while the access boundary remains the file's boundary. A thread helps explain the work; it is not a substitute for explicit approval, task ownership or specialist annotation tools.
Put the discussion where the material lives.
Open the file or folder channel to discuss a proposal, budget or shared working material. Keep the question specific enough for another colleague to understand its purpose. The preview can help readers orient themselves, but refer clearly to the relevant version or content when precision matters. A comment beside a file does not automatically apply the requested change.
- Connected channels for files and folders
Continue the thread as the file develops.
A new file version can remain part of the same internal conversation, preserving the reasoning behind revisions. State what changed and whether the discussion concerns the current or an earlier version. The thread is useful for continuity, while the team should still assign concrete follow-up work to a responsible person instead of expecting a message alone to guarantee completion.
- One continuing thread with explicit version references
Keep the conversation within file access.
People need file access to read or join the internal thread. If that access is removed, the conversation closes to them too. External file links do not reveal the chat. Review the audience before posting sensitive feedback and do not assume that giving someone a file link enrolls them into the internal discussion or grants access to the workspace.
- The same access boundary for file and discussion
A concrete workflow
Open the material
Check the file and version relevant to the review.
Ask clearly
Explain the question and identify the relevant content.
Agree action
Assign the agreed next step rather than relying on discussion alone.
Share separately
Review the external delivery version without exposing internal comments.
An illustrative working example
Illustrative scenario: a budget question beside a proposal
A colleague opens the proposal file and asks a budget question in its channel. The reviewer answers beside the material, and the owner assigns a follow-up check. When a new version arrives, the thread records what was changed. The customer receives only a reviewed file link. In the pilot, the team checks that a person without file access cannot enter the discussion and that the external recipient does not see internal comments.
Questions about this topic
Does every file have a conversation?
Files and folders have connected communication channels. Reading and participating depend on the relevant file access.
Does removing file access also remove chat access?
Yes. The internal conversation follows the file's access boundary, rather than remaining a separate back door to the material.
Can an external recipient see the thread?
Not through an external file share. That link opens a specific version and does not expose the internal conversation.
Is a comment a formal approval or assigned task?
No. Record the actual decision and assign the required work explicitly. Discussion supports that process but does not establish it automatically.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Slack
Application concept: Prepare a focused Slack handover to the file's internal discussion rather than copying an entire private conversation.
Microsoft Teams
Application concept: Identify a Teams decision that belongs in a reviewed file note, checking who can read the file first.
Confluence
Application concept: Link a maintained Confluence explanation as discussion context without assuming the external page inherits file permissions.