Manage Dovetail Research Permissions
Build the access model around the sensitivity of the research and the work collaborators must do. This is the broad governance setup; a separate sharing checklist should validate each outgoing artifact.
Before you start: Have authority to manage the relevant resources and an agreed research-handling policy. Identify external collaborators and sensitive participant material.
Worked example: A researcher needs to edit transcripts while a product stakeholder only needs reviewed findings. Avoid giving both the same raw-data access merely because they work on the same initiative.
Step-by-step guide
Classify the material
Separate raw recordings, identifiable metadata and reviewed findings. Decide which audiences need each category.
Map responsibilities
List who analyzes, reviews, administers and consumes findings. Grant capabilities based on the work rather than job title alone.
Configure resource access
Apply the supported project and Doc permissions deliberately. Check group and workspace context rather than relying only on a direct invitation.
Verify effective access
Test representative editor and reader accounts. Confirm both visibility and editing behavior for sensitive sources and findings.
Plan lifecycle changes
Record how access changes when a study ends or a collaborator leaves. Assign ownership for periodic review.
Document exceptions
Keep a reason and review date for broader access. If the required boundary cannot be achieved, move or sanitize material instead of assuming the link is private.
Common mistakes
Everyone needs raw data
Findings consumers may not need recordings.
Role name trusted alone
Verify actual resource access.
No lifecycle owner
Temporary collaboration can become indefinite access.
Tips
Use separate access reviews for raw data and findings.
Test permissions with non-owner accounts.
Record external access expiry where relevant.
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.