Sharing and Report Distribution
Share reports securely with internal and external stakeholders using scoped access policies.
Use controlled distribution to balance transparency with security.
Sharing modes
- Internal team sharing: collaborators with direct entity access
- Selective follow access: a user, entity, or organization principal with scoped artifact access
- Time-bound or revocable sharing: access that can be removed when the workflow ends
Recommended flow
- Confirm report quality and approval status.
- Decide whether the recipient should be a direct collaborator or a follower.
- Grant the smallest viable artifact scope.
- Verify whether linked artifacts should be hidden, derived-only, or fully accessible.
- Review and revoke access when the diligence or operating need ends.
Access policy guidance
Use follow-access presets when possible:
- All reports for trusted, ongoing stakeholders
- Goals only for execution-oriented diligence
- Press releases only for announcement-driven audiences
- Custom when the stakeholder only needs a specific set of reports, tags, or source types
Linked artifact access
When a report links to other artifacts, decide how much the recipient can open:
- None keeps linked artifacts private
- Derived only exposes execution-facing summaries without opening the entire artifact
- Full artifact allows the underlying document when policy permits it
Execution-specific sharing
Execution access and report access are related but not identical.
- A user may request access to an entity's execution record.
- The founder can approve or deny that request.
- Separate follow-access policies determine which underlying artifacts that follower can see.
This separation lets you share the execution narrative without over-sharing the full report library.
Validation checklist
- Report approval status confirmed before sharing
- Recipient is assigned to the correct principal type
- Access scope matches the real need
- Linked artifact behavior is intentionally chosen
- Revocation path is clear and tested