> 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/sales-materials/logicnets-knowledge-center-run-time-user-ln-kcu.md). # LogicNets Knowledge Center (Run-Time User) (LN-KCU) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-86434bfe175285d1f7bdc1e371160285da9af9cf%2Fc3bd9530-70e7-4f24-95de-4563e8097bfd.png?alt=media) ### License: per user of Knowledge Center end-user applications Notes: 1. Supports use of both named and concurrent user licenses ### LN-KCU Description The Knowledge Center Framework is a traditional knowledge base and management system designed in LogicNets. For an end-user community, the Knowledge Center Framework Run-Time option is a standalone, pre-configured application that end-users can use to create, organize, and maintain any sort of rich content for other users to reference as needed, separate other LogicNets components. The application allows “curator” end users to organize their 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. The Knowledge Center can then be accessed by non-curator users to browse and perform content searches. The application supports collaboration between content creators, curators, and consumers with interactive features to enable content review and approval cycles and to allow users to react to and communicate within LogicNets about the content. ### Services and Deployment Considerations LogicNets recommends Knowledge Center delivery for end-users in conjunction with additional Pro Services (LN-DS, LN-TS) including: * Application-level user and role management setup * High-level styling customization * Training for content management These services usually require development and acceptance by customer of a formal SoW. PG-FR5-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/platform-documentation/sales-materials/logicnets-knowledge-center-run-time-user-ln-kcu.md?ask=&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.