> 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/package-content-view.md).

# Package content view

When you open an application package, the package content view lists everything inside it: **Applications**, **Portal Pages**, and **Automations**. The package content view offers a more detailed list view, described below.

### Switch between card and list view

Use the view toggle in the top-right corner to choose how content is displayed.

* **Card view** groups content by type (Applications, Portal Pages, Automations) and shows each item as a card. This is the classic view.
* **List view** shows all content in a single sortable table with additional columns, making it easier to scan larger packages.

<div align="left" data-with-frame="true"><figure><img src="/files/0zVZ9mlqMkQcK0vuZgr3" alt=""><figcaption></figcaption></figure></div>

### Density modes

In list view you can choose how compact the table is. Open the density menu (the sliders icon) <img src="/files/p12cOfThjCMkFSEYj6Qw" alt="" data-size="line"> and select:

* **Regular** – more spacing between rows.
* **Dense** – tighter rows so more items fit on screen at once.

### List view columns

List view adds information that is not shown on the cards:

* **Name** – the item name and icon.
* **Type** – Application, Page, or Automation.
* **Deployed** – the version currently deployed to an environment.
* **Last Modified** – who last changed the item and when.
* **Latest Commit** – the most recent committed version and its commit message.
* **Visible** – whether the item is shown in the Client.
* **Tags** – any tags assigned to the item.

### Filter the content

The filter bar lets you narrow down what is shown. Combine filters as needed, then use **Reset filters** to clear them.

* **Name** – search by name.
* **Type** – show only Applications, Pages, or Automations.
* **Deployed** – show items by their deployment status to environments.
* **Tags** – show only items with the selected tags.

{% hint style="info" %}
The **All / Applications / Portal Pages / Automations** tabs and the **Type** filter both narrow content by type. Use whichever is quicker for your workflow.
{% endhint %}

### Tags

Tags help you organize and filter content. You can assign one or more tags to any Application, Portal Page, or Automation.

To add or remove tags:

* Open the item's settings (the **Edit** / settings panel).
* In the **Tags** section, select **Add Tag** to assign a tag, or select the **×** on a tag to remove it.
* Select **Save**.

Once assigned, tags appear in the **Tags** column in list view and can be used in the **Tags** filter to narrow the content shown.

<div align="left" data-with-frame="true"><figure><img src="/files/NlOvKMYAkDdKxYBJQf1V" alt="" width="379"><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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/application-packages/package-content-view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
