Link a Shortcut Doc to an Epic with Two-Way Relationships
Insert an Epic reference into a Shortcut Doc to create a relationship visible from both the Doc and the Epic. A plain explanation beside the link gives delivery work its decision context.
Docs must be available in your workspace. Check the Doc’s sharing permissions separately; a relationship does not make a private document readable by everyone.
Example: connect a checkout Epic to its rollout specification, including success criteria, exclusions and unresolved deployment decisions.
Step-by-step guide
Open the authoritative Doc
Use the Doc that actually owns the specification. Update its title and remove competing stale instructions before connecting it to delivery tracking.
Insert the Epic entity
Type / in the editor, search for the Epic and insert it. You can also paste its Shortcut URL directly into the Doc; confirm the resulting entity is the intended Epic.
Explain why the link matters
Add a short section stating what the Epic delivers and which decisions the Doc controls. Keep acceptance criteria near the relationship so the link is useful to a new contributor.
Check relationship and access
Inspect the Doc Relationships sidebar, then open the Epic and confirm the reciprocal relationship. Review the Doc permission dropdown with the intended readers in mind.
Common mistakes
Assuming an entity link grants access
Private or selectively shared Docs keep their own permissions. Set sharing intentionally rather than treating the Epic link as an access grant.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.