> 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/knowledge-center/linking-knowledge-center-content.md).

# Linking Knowledge Center Content

## Description

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

## Link a Content Reference to a Node

Once you have created content references in the content folder of your project 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. Click on the content to link and click ***Add*** to add this content to the node. The selected content should show in the content linked to this element table
5. Click ***save*** to save your changes.

Note: Content sorting will be part of a future build. To reorder content now select and delete articles and then re-add them in your desired order.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-da6095da1716d4291361020038a5724dfbe89241%2F0799905e-731e-423d-804a-6a02b776e9e8.png?alt=media)

## Advanced Options for Linking from the Knowledge Center

The LogicNets Knowledge Center provides an additional way to link content to a logicnet node:

* Through a collection with tag names.
* Using the value stored in the data object of the question as the tag name for a given tag category.
* Creating one or more rules to search for and select articles that meet the rule criteria (future functionality).

If you select *knowledge center* using the ***Select a source*** dropdown menu the system displays additional options.

1. Click the radio button to select the option you want.
2. Enter the collection name in the *Data object* field and enter the tag category in the *Tags category* field.
3. Click ***Add*** to add your selection. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2af6d09a8c1485b4195d315ef9bd8f8e2b050854%2F4c729ca4-f6f3-4364-9ad4-9f42096f7acf.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/knowledge-center/linking-knowledge-center-content.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.