> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/application-packages.md).

# Application packages

All applications are groped into application packages, similar to folders in the file system.  Packages contains applications, components, permissions and more.

## Create application package

1. Select **Apps** in Hub menu and select **Create Package**.

   <figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FN17NbxPOBtdQhq5HvMtH%2Fimage.png?alt=media&amp;token=b8c59734-aa4e-4488-9c8b-6b64614c678c" alt=""><figcaption></figcaption></figure>
2. Enter the name of the package.
3. Set the icon and color.
4. Select **Add developers** to add one or more groups. Members of the groups will have full access to the package and its content.&#x20;
5. **Save**.

   <div align="left"><figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FGe20rrAgfJWR3qZdutry%2Fimage.png?alt=media&amp;token=49f517f2-2f1b-49ae-b039-79f3443af168" alt="" width="263"><figcaption></figcaption></figure></div>

{% hint style="info" %}
At least one access group needs to be assigned to the package.
{% endhint %}

## Edit application package

1. Hover over the app package card and the context menu will appear, click on **Edit**.
2. You can now change the title, icon, color and the assigned groups.&#x20;

## Delete application package

1. Hover over the app package card and the context menu will appear, click on **Delete**.

{% hint style="danger" %}
Deleting a package will also delete all of its content. This operation can not be undone.
{% endhint %}

## Application Library list view

The Application Library can be displayed as cards or as a sortable list. Use the view toggle in the top-right corner to switch between them.

In list view, your packages are shown in a table with the following columns:

* **Name** – sort packages alphabetically by selecting the column header.
* **Created** – who created the package and when.
* **Last Modified** – who last changed the package and when.

Search and the filter button are available in both views.

<div align="left" data-with-frame="true"><figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2Fcv8KXZpE6fA23ahG1KS6%2FCleanShot%202026-06-15%20at%2014.29.34.png?alt=media&amp;token=b3c10741-8706-4f70-90d1-909c1439d9f5" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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://docs.novacura.com/flow-connect/working-with-connect/create-and-design/application-packages.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.