> 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/logicnets-software-component-details/content-authoring-software-parts/logicnets-knowledge-center-ln-kc.md).

# LogicNets Knowledge Center (LN-KC)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-147022a9271696d5ec1959145c56c519e25985bc%2Fae1cc191-32b2-49f5-bbcc-d586014be68f.png?alt=media)

### License Basis: Per named content curator user

Notes:

1. Used in conjunction with the Designer (D) and the ASF (MDF), SAF, SCF, or VGN Use Case frameworks
2. Provides a structured content management environment for traditional content to be managed and integrated with modeled content in the LogicNets Designer
3. Supports run-time access by LogicNets applications to curated traditional content, independent of the number of application end-users
4. The KC part is intended for staff involved in creating and maintaining applications written in LogicNets. The KCU part should be used when the application end-users need to curate traditional content (see below).

### LN-KC Description

The Knowledge Center is a traditional knowledge base and management system designed in LogicNets. It provides a content management environment that organizations can use to create, organize, and maintain content in common digital formats so that the content can be selected and made conditionally available to users of the applications created with the LogicNets designer. LogicNets has integrated the Knowledge Center with the LogicNets Designer so that content maintained in the Knowledge Center can be dynamically and contextually linked by designer users to discreet steps in their logicnet decision trees. When end users of the application land on a linked step, the application displays the content or indicates that it is available.

A benefit of the Knowledge Center is that it allows for division of labor between different resources in the application development process. “Curator” staff that may not be experts in the decision logic, can use the Knowledge Center’s separate non-technical interface to organize content in a virtual file system where folders can be visually manipulated, and content can be classified with meta data and tagging. Curators can import pre-existing documents and files of all sorts into the system or create them within the application using the embedded HTML5 editor. Designer users can then easily search for the content articles and link them explicitly or through rules to the modeled content steps where they are to be displayed in the run-time application.

### Services and Deployment Considerations

No additional services are required for basic deployment of the Knowledge Center.

Optional LogicNets Training Services (LN-TS) are available to teach both designer and “curator” users how to create and manage content resources and how to work in the Designer to link that content to specific steps in a LogicNets application’s decision logic.

Note that LogicNets applications can be linked via web services to external content management and knowledgebase systems. LogicNets Design and Deployment Services can be acquired to enable this as an alternative to using the Knowledge Center.

PG-CO2-231127


---

# 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/logicnets-software-component-details/content-authoring-software-parts/logicnets-knowledge-center-ln-kc.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.