Sharing and Report Distribution

Use controlled distribution to balance transparency with security.

Use this guide after a report has been generated and reviewed. If the report was created with a reporting intent and Golden Documents, confirm those references are correct before sharing.

What recipients see

When you share a report or collection, recipients only see the artifacts they have access to. A share does not automatically reveal every source document, linked artifact, or entity workspace item.

If a linked artifact is restricted, the recipient may see the report without being able to open the underlying document. This protects sensitive source material while still letting you distribute the approved reporting output.

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

1. Confirm report quality and approval status.
2. Confirm any Golden Documents used by the reporting intent are the right references for this audience.
3. Decide whether the recipient should be a direct collaborator, follower, or one-time report recipient.
4. Grant the smallest viable artifact scope.
5. Verify whether linked artifacts should be hidden, derived-only, or fully accessible.
6. Ask the recipient to confirm they can see the expected report or collection.
7. 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

Golden Documents used by a reporting intent are treated as controlled source references. Share them only when the recipient needs to inspect those references and policy allows it. In most cases, share the reviewed report output rather than every reference document used to create it.

Revoking access

Use revocation when a diligence process, review window, or operating need ends.

After revoking access:

1. Ask the recipient to reload the report or collection URL.
2. Confirm the report no longer appears in their shared surfaces.
3. Confirm any related feed or dashboard surface no longer exposes the revoked artifact.

Revocation should remove access on the next request. If a recipient still sees a revoked report after reload, treat that as a support issue.

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
• Golden Documents and reporting intent references confirmed
• 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