Share Dovetail Findings with Stakeholders
Share the Doc and verify both its own visibility and the evidence readers need. A copied URL does not by itself grant access, and workspace, project and folder contexts can behave differently.
Before you start: Have authority to share the Doc and an intended recipient list. Review sensitivity and consent before making research available beyond the original team.
Worked example: A product lead can read the summary but cannot open its supporting interview. Decide whether the source needs appropriately scoped access or whether a sanitized explanation is sufficient.
Step-by-step guide
Define the audience
Choose who needs the finding and what decision they will make. Avoid broad sharing merely because the summary is concise.
Review the Doc location
Check whether it is a workspace, project or folder Doc. Inspect actual permissions instead of assuming every location inherits access identically.
Set visibility deliberately
Use the Doc’s sharing controls for the intended people or groups. Review project permissions when the Doc lives inside a project.
Check evidence access
Verify that linked highlights or data can be opened by authorized recipients. Do not broaden raw-data access unnecessarily to fix a summary link.
Test the recipient view
Ask an intended reader to open the exact link. Confirm they can see the decision context and only the material they should access.
Close with a useful brief
Include the main finding, limitation and requested decision alongside the link. Record temporary access that should end after review.
Common mistakes
URL equals permission
Access still needs to be granted.
Folder assumed inherited
Current Doc visibility rules require checking.
Raw interviews shared to fix a summary
Use the minimum appropriate evidence access.
Tips
Test with a real recipient account.
Keep sensitive context out of link previews where possible.
State the decision requested in the sharing note.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.