> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/applications/my-applications-tab.md).

# Use the My Applications Tab

A tour of the My applications tab and the application page in Kilo: every column, button, tab, and card, plus how to create, edit, and delete an application.

**My applications** is home base for everything you run. It lists the applications you installed from solutions and the ones you built yourself, because Kilo treats them as the same thing. This guide describes every element of the list and of an application's own page.

## How do I open My applications?

1. In the left sidebar, select **Applications**.
2. Select the **My applications** tab (the second tab).

The heading is **Applications**, with the introduction: your applications are the solutions you installed and the ones you built yourself, each with its devices, rules, alarms, and dashboards, running in your organization.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-0722d837875a2bd26c32ce01db29f35c1f65dada%2Fkilo-solutions-my-applications.jpg?alt=media" alt="The My applications tab with a search box, a Status filter, a Create an application button, and a table of applications with Photo, Name, Description, Status, Dashboards, Devices, Rules, and Alarms columns"><figcaption><p>The My applications tab of a demo organization. This organization publishes the catalog (Kilo), so it also shows the Photo and Status columns.</p></figcaption></figure>

## What is in the application list?

Above the table:

* **Search.** Filters the list by name as you type.
* **Status: All.** A filter with the options **Status: All**, **Status: Published**, and **Status: Not published**. Only the organization that publishes the catalog sees this (that is Kilo).
* **Create an application.** The blue button in the top-right corner. See below.

The table columns:

| Column                                             | What it shows                                                                                                                                                                                                                                   |
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Photo**                                          | The picture of the application, if one was added when publishing. Only the organization that publishes the catalog sees this (that is Kilo).                                                                                                    |
| **Name**                                           | The application name.                                                                                                                                                                                                                           |
| **Description**                                    | A short description of its purpose. A dash means none was written.                                                                                                                                                                              |
| **Status**                                         | Only the organization that publishes the catalog sees this (that is Kilo). **Published**, **Not published**, **Published in landing**, **Published in AI**, or **Published in landing & AI**. The last three describe where Kilo has listed it. |
| **Dashboards**, **Devices**, **Rules**, **Alarms** | How many of each the application holds.                                                                                                                                                                                                         |

At the end of each row are one or two icon buttons. The **arrow** opens the application. For the organization that publishes the catalog, the **gear** opens the publish dialog (**Publish application** for an unpublished application, **Update publication** for a published one); see [How do I publish a solution?](/applications/publishing-a-solution.md). Selecting anywhere else on the row also opens the application.

If your organization has no applications, the tab invites you to create your first one.

## How do I create an application?

1. On the **My applications** tab, select **Create an application**.
2. In the dialog, type an **Application name** (for example, Building Monitoring).
3. Optionally type a **Description**.
4. Select **Create application**. Select **Cancel** to close without creating.

The dialog explains the idea in one line: organize everything for one use case in one place, including devices, rules, alarms, and dashboards, and add or remove items anytime.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-1759c3d5d2e667b495998b0955264ed2f9c5835d%2Fkilo-solutions-create-application.jpg?alt=media" alt="The Create an application dialog over the My applications tab with fields for Application name and Description and Cancel and Create application buttons"><figcaption><p>The Create an application dialog. Only the name is needed to start.</p></figcaption></figure>

A new application is empty until you add things to it. Assign devices, dashboards, rules, and alarms to it using their **Application** field. See [Creating an Application](/applications/creating-an-application.md) and [Organizing Content](/applications/organizing-content.md).

## What is on an application's page?

Select an application to open it. The title reads \*\*Applications / \*\* followed by the name, with the description under it and a back arrow on the left. In the top-right corner you will find, depending on your role:

* **Publish application**, or **Unpublish** and **Update publication** for a published one. Only the organization that publishes the catalog sees these (that is Kilo).
* A **pencil** icon that opens the **Edit application** dialog.
* A **trash** icon that starts deletion.

Two tabs sit under the title: **Dashboard** and **Content**.

### What does the Dashboard tab show?

It shows the application's dashboards in one place. A chip row names each dashboard (here **Site Conditions**), and **Go to the dashboard** at the right opens the full dashboard. Every widget and device fed by the Emulator carries an **Emulator** badge, so you can always see what is still virtual.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-3ee467868273970bac96fe8e310979290c40987b%2Fkilo-solutions-application-detail.jpg?alt=media" alt="The Building Monitoring application page with Unpublish and Update publication buttons, a pencil icon, a trash icon, Dashboard and Content tabs, and widgets with Emulator badges"><figcaption><p>The page of a published application in a demo organization. Only the organization that publishes the catalog (Kilo) sees Unpublish and Update publication; other members do not.</p></figcaption></figure>

### What does the Content tab show?

**Content** lists everything behind the application, in cards you can open:

* **Devices**, with a count. Each row shows the device name, an **Emulator** badge if it is emulated, and an arrow that opens the device.
* **Dashboards**, with a count.
* **Rules**, with a count and a short explanation: rules are where the conditions live, and a rule can send a command back to a device and raise one or more alarms.
* **Alarms**, with a count and their severity label (for example **Low**). An alarm here is the notification, not the trigger; a rule raises it when its condition is met.
* **Emulator.** Shown only while the application holds at least one emulated device. Explains how virtual devices run on the Emulator connector, with a **Go to connectors** button for when you are ready to use real hardware. See [How do I swap the Emulator for real devices?](/applications/swapping-the-emulator-for-real-devices.md)

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-75943fce363735bc76d62f71aec258615496aa6d%2Fkilo-solutions-installed-content.jpg?alt=media" alt="The Content tab of an installed Building Monitoring application with cards for Devices, Dashboards, Emulator, Rules, and Alarms"><figcaption><p>The Content tab of an installed application in a demo organization.</p></figcaption></figure>

Counts show how many items are in each category. A **0** means it is empty. A dash means the count is unavailable, for example because you lack access to that category.

## How do I rename an application?

Select the **pencil** icon. The **Edit application** dialog shows the **Application name** and **Description**, with **Cancel** and **Save**.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-d58b9024cc70300d4363c8cb08ff780ecb92b4b2%2Fkilo-solutions-edit-application.jpg?alt=media" alt="The Edit application dialog with Application name and Description filled in and Cancel and Save buttons"><figcaption><p>The Edit application dialog for a demo application.</p></figcaption></figure>

## How do I delete an application?

Select the **trash** icon. Kilo asks **Are you sure you want to delete the application?** and warns that the devices, rules, alarms, and the dashboard linked to the application will be permanently removed from the platform. In practice rules are stopped and moved to Trash, where you can restore them; devices, dashboards, and alarm definitions are removed for good. Details: [What happens when I delete an application?](/applications/deleting-an-application.md) Select **Yes, delete** to confirm, or **Cancel**.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-83a86cb88d0877e73ecbd23537d62810b67cd509%2Fkilo-solutions-delete-application.jpg?alt=media" alt="A confirmation dialog asking whether to delete the application, warning that its devices, rules, alarms, and dashboard are permanently removed, with Cancel and Yes, delete buttons"><figcaption><p>The delete confirmation. Deleting an application removes the resources inside it.</p></figcaption></figure>

Deleting an installed application affects only your copy, never the solution in the catalog. Read [Deleting an Application](/applications/deleting-an-application.md) before you retire anything that holds real data.


---

# 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.kiloiot.io/applications/my-applications-tab.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.