Organize Project Documents in Linear
Attach a concise set of documents and named external links to the project. Keeping an index in the overview helps readers find decisions without reading every issue.
Step-by-step guide
Check access and scope
Project access and permission to edit its resources are required. External documents retain their own access rules.
Inventory source documents
Inventory the current brief, designs, decision record and rollout plan.
Create a project document
Create a project document for information best maintained beside the work. In project Resources, use + and Create Document; give it a title that distinguishes current scope from a historical decision.
- Worked example: Use Brief: invite-flow scope, Decision log: expiry rules, and Rollout: rollback owner. Put superseded alternatives in the decision record rather than presenting multiple competing current specifications.
Attach external references
Add external resources through the project Resources section. The same Resources control accepts external links; add a descriptive label instead of leaving only the source domain.
Label authoritative resources
Give links descriptive labels and state which document is authoritative.
Test reader access
Ask a reviewer to open every resource with their normal permissions.
Verify the result
A new collaborator can locate the approved scope and rollout instructions without asking the author.
Common mistakes
Avoid the main failure mode
A link does not grant permission to its destination. Avoid assuming a project member can open a private design file.
Check the handoff edge case
Adding resources without descriptive labels forces readers to open every link to discover which specification is current.
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.