Skip to main content
A document explains the thinking behind one or more requests. Linking the two means anyone opening a feedback post can read the research or the decision behind it, without hunting for it. A link works in both directions and is not exclusive. One document can inform several posts, and one post can have several documents. You can create the link from either side.
Linking and unlinking requires the Starter plan or above, and an Owner or Admin role. Members can see linked documents but not change the links. See Team roles and permissions.

​
Link a post from the document

1

Open the document

Go to Documents and open the document. It has to be saved first, because a link needs something to attach to.
2

Click Link a post

In the right panel, under Linked posts, click Link a post.
3

Search for the post and pick it

Type part of the post’s title. Select a result to link it.
Linked posts appear in the panel with their feedback status and ID. Select one to open it. To remove a link, hover the row and click the unlink icon. Unlinking only removes the connection, and never touches the post or the document.

​
Link a document from the post

Every saved feedback post has a Documents block, between the metadata and the activity feed. It lists the documents that inform this request. From here you have one shortcut: New document creates a document named after the post, links it to that post, and opens it so you can start writing immediately. Use it when a request needs research and you want to start from the request. The block is not shown at all on workspaces whose plan does not include Documents. A link records one thing: this document informs this request. That is deliberate. A link carries no status, no assignee, and no progress. Attaching a specification to a post does not mark the post as being worked on, and does not move it on your roadmap. To signal progress to your users, change the post’s status. To track who is building it, use an integration with your issue tracker.
  • Research to the request it came from. Customer call notes belong on the post that prompted them.
  • A decision to every request it answers. If one decision settles four related requests, link it to all four. This is the cheapest way to stop the same discussion restarting on each post.
  • A specification to the request it implements. So whoever picks the work up finds the detail without asking.
If several posts are really the same request, merge them first, then link the document once.

​
Next steps

Version history and restore

See what changed in any version and go back to it.

Write a document

Create a document, format it, and set its type and status.

Merge duplicate feedback

Combine duplicate posts so votes and comments add up in one place.

Documents

What documents are for and how the Documents screen is organized.