> 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/publishing/package-overview-tab.md). # Package Overview Tab ## Package Overview The *Package overview* tab is where you manage packages published from your Designer workspace. It is the centralized page where you can see all of the packages published from your workspace, where you can download your published applications, and where you can delete more than one published package at one time. This tab also shows you if your published package is based on a particular framework. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-9747273f349a56adf3b005cfdf613e4d4df69038%2F462faeda-0c64-4cf7-88a6-7bfdf7873b63.png?alt=media) If your list of published packages is not very long you can browse through it easily, but as your list grows you can also search the list of published applications, looking for a project name, or a published package name, or even by the framework on which it was based. ## Search Published Projects Search for published projects on the *Package overview* tab. 1. To search for a particular project or projects, enter a search term in the appropriate column and press the *Enter* key on your keyboard. 2. To return to the complete list of published projects delete the search terms from the search fields and press the *Enter* key on your keyboard. --- # 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/publishing/package-overview-tab.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.