> 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/system-administration/package-installation/package-installer.md). # Package Installer ## Introduction The Package Installer is a package management tool that centralizes your ability to manage published packages. It allows those users with access to view and manage all packages that are available on a LogicNets installation, and you can use it to install install new packages and make them available to users. It also allows you to create new start codes for an application as well as active or deactivate packages. ## Description When you create applications using LogicNets you publish them to create packages. If you are managing packages centrally, you can export a published package from any LogicNets Designer account and use the Package Installer application to install it and make it available to users. The Package Installer is located on your LogicNets dashboard. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-50ba62a20e02b9d884286170a25a907c4ddc365e%2Ffc0f5ed2-3296-423a-8a71-c04b454886c0.png?alt=media) When you open the Package Installer you see that the screen is divided into different sections: Categories, Packages, and Start Codes. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-df9f903d104f485ae5b86cb171c9afd162d3eba7%2F1f812fe2-a47e-4d82-8836-57b18cfcef73.png?alt=media) ## Categories The top section of the page displays a list package categories available on that installation of LogicNets and their scope if they have one. These are the categories into which the packages are divided. The category is the name of your project. So, for example, you could have *How To Build a House v1*, *How to Build a House v2*, and *How to Build a House v3* and all three would be in the category *How to Build a House*. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-08e85d76f3d44ec53416651dfa734baf5962db28%2F949d0b5c-90dd-4d43-8f1a-5ec723785e2d.png?alt=media) ## List of Packages When you click on a category, the Packages section displays the published packages associated with the selected category. In this section of the screen you can activate, deactivate, or uninstall a package. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-91a95b65d24da94018a3dc5d76a6292374ea5f97%2F91f74f96-c09a-468b-9d0d-3f93ad6ef19d.png?alt=media) Some published packages can be configured to allow an administrative user to start a package in admin mode. If you have administrative privileges and there are packages that allow administrators to open a package in admin mode you will see that option. ## Start Code The Start Code section displays the start codes associated with a selected package. In this section you can add, delete, activate, or deactivate a start code. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f7a777eef8b1098ca450a1a3e9c8892f6ebdd679%2Fdbf12e03-5dd2-42a2-ab86-1028dac498cf.png?alt=media) ## Tag Some companies use tags to more specifically manage their applications. For those users, the Tag tab in the Start Codes section displays all tags associated with a selected package. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7a789e4e7ea979044004a446b1a5467ac4b04d92%2F6b933baf-0b09-4f40-827f-675dc77189cf.png?alt=media) ## Install Package To manage your packages, start codes, and tags you must first install a package. 1. To install a package click the ***Install Packages*** button at the top-right of the screen. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8277dc9aa2d1fdc95f2dfee1632832cab023491d%2F7a618e33-7239-414b-a023-7bdcabdb5815.png?alt=media) When you click this button the system displays a popup window where the user can chose a package to be installed. 2. Click ***Choose Files*** and select the package you want to install, which can be any published LogicNets package. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0bb499d1d3af4ae66d059ed5fbdf48a20a5295d1%2F78cd2044-c13a-49ea-8f3f-f8adb4d10162.png?alt=media) 3. Once you have selected the zip file of the package you want to install, click the ***Install*** button. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-684a5b1d0f51d0de89df18da07f5df4aba6df4c1%2F304c5d96-9ca0-437f-b816-b4331cacd913.png?alt=media) The system will display any errors encountered while trying to install a package. Otherwise, it will display the following popup message. 4. Click ***Ok*** to complete the installation. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3fcbc326c88b422432603c0d7cc1153b572d8bb0%2F970e9c96-e8e4-41bf-80e9-d0e514128001.png?alt=media) ## Activate a Package Once you have installed a package, you can activate it so users can access it. 1. Select the name of your package or the category it is in from the *Category* list. Your package or the packages that are in the selected category display in the *Packages* section of the page. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ea50505af437e9f08b5658f894379aa6de3febfb%2F51a04f00-fe44-41ef-9b5d-8c02f02921af.png?alt=media) 2. Click the checkbox next to the package you want to activate and click the ***Activate*** button. 3. Once you have activated your package you can enter a start code for it. Go to the *Start Codes* section of the page and click ***Add new***. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4bd1962b8c797768c8c3f27a3697974653cd2dd6%2F6424ea51-0b2f-499b-8aea-79916aa04e48.png?alt=media) 4. Enter the start code in the *Startcode* field and click ***Save***. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-eaa3781eb108b9b8e041514dffbdeff55ea8c575%2F8bc9c5ad-e1e6-4b33-846e-2b1c02f9c505.png?alt=media) 5. To see any other start codes associated with your project, click the checkbox next to your project in the *Packages* area of the installer. --- # 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/system-administration/package-installation/package-installer.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.