> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/nodes-parts-and-resources/linking-content-references.md).

# Linking Content References

## Description

Whether you have created content references within the Designer in *resources/content* of a project or created articles in a KnowledgeCenter application, the process of linking one or more of these information assets to a logicnet, node, answer option, or project is similar.

## Link a Content Reference to a Node

Once you have created content references in the content folder or in the Knowledge Center you can then link that content to specific nodes in your logicnets.

1. Select the node in your logicnet where you would like to link a reference.
2. Click the ***Resources*** tab for that node.
3. Using the ***Select the source*** dropdown menu, select whether you are using content in the content folder or from the Knowledge Center.
4. With v8.2, you can filter for specific types of content reference; for example, a content.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1876fda29898fb5f3073cc18ed4f78f2a41c5b63%2F39edd9fa-8e92-40fc-9929-c0806387ed82.png?alt=media)
5. Click on the content you want to link and click ***Add*** to add the content to the node. The system will show the selected content in the *content linked to this element* table.
6. Click ***save*** to save your changes.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-677b83bed027e167b29675e13ed172edb389c07e%2F03ee7a07-1eb2-4b13-aeec-30019cb9e225.png?alt=media)

## Link a Content Reference to a Logicnet

The process is the same for linking a content reference to a logicnet. Navigate to the ***References*** tab of your logicnet, and repeat the linking instructions above.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-63c1d0df49070f73fbbe3d997d55c98a6830a34d%2F5ec71f98-f969-4933-834c-9ff41ed7e3b4.png?alt=media)

## Link a Content Reference to a Answer Option

In addition to linking references to a node or a logicnet, you can also link them to answer options. Locate the ***References*** button for any answer option and repeat the steps above to associate a content reference with an answer option.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8965b5468fb5c34e91b3e6e1f2c92a033eb6a37f%2Fde87523c-8109-4d31-b325-4811124e89b9.png?alt=media)

## Link a Content Reference to a Project

On the ***Resources*** tab at the project level, you can add and/or delete resources for the project. The resources here are project-specific, rather than tied to a particular logicnet. The process of linking a content reference to a project is the same as linking to a node or logicnet. Click the name of your project and click the ***References*** tab at the project level and follow the linking steps above.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7a43836052094a15d332efe42d0686904bca7052%2Fd1e8bd72-01e9-4549-b553-6c290803de51.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/nodes-parts-and-resources/linking-content-references.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.