> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/kaiya-apps.md).

# Kaiya Apps

Build interactive data applications from a conversation

Kaiya Apps lets you generate fully interactive, persona-scoped data applications directly inside Tellius, using only natural language. You describe what you need in a conversation with Kaiya, it generates a complete application: layout, data bindings, filter logic, navigation tabs, KPI cards, charts, tables, and written insights.

The resulting app is a live, multi-section application tied to a Business View. Data can be refreshed on demand, the app can be shared with other users, and modifications are made conversationally rather than through a configuration panel.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/Sf1FDM629es9zUC501gP/Kaiya%20APps.gif" alt="" width="563"><figcaption></figcaption></figure>

#### How Kaiya Apps differ from Vizpad

Vizpad is a general-purpose analytics canvas where users manually select chart types, configure axes, drag in dimensions, and arrange layouts. Kaiya Apps operates differently. You provide a business question or describe a persona and their recurring analytical needs. Kaiya then generates the entire application structure, chooses the appropriate chart types, selects relevant metrics and dimensions from the Business View, writes contextual insights, and produces a finished multi-tab application.

The key architectural distinction: Vizpad is designed for open-ended exploration. Kaiya Apps is designed for recurring, role-specific analytical needs where the same set of questions is asked repeatedly, potentially by multiple people across the organization.

#### Data behavior

Apps query the underlying Business View at creation time and store a data snapshot. This snapshot powers the app immediately, so there is no delay from live queries each time the app loads. When data needs to be updated, admins and app owners can trigger a manual refresh or schedule one. The refresh runs asynchronously in the background. While a refresh is in progress, the app remains fully usable, displaying data from the most recently completed refresh. An App can also query its data live instead. See [Live data in Apps](https://help.tellius.com/kaiya/kaiya-apps/live-data-in-apps).

### How to access Kaiya Apps

The **Apps** section is available as a dedicated item in the left navigation pane. The left navigation shows up to six primary modules, chosen by an administrator under **Enabled Modules**. When Apps is one of them, it appears below **New Chat** in the sidebar. Otherwise, find it under **More**. See [Navigating around Tellius](https://help.tellius.com/getting-started/say-hello-to-tellius/navigating-around-tellius).

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/hN5uwj3DenNzH4nWrcUj/image.png" alt="" width="257"><figcaption></figcaption></figure>

Click **Apps** in the left navigation to open the Apps library.

### The Apps library

The Apps library is the central hub for managing all applications. Apps are grouped on three tabs: **Published**, **Draft** and **Archived**. Each app card shows its type and status, for example **KAIYA APP · PUBLISHED**, the app name, a brief description, its owner and the date it was last updated. A long app name stays on one line and ends with an ellipsis, so the owner and the last-updated date stay in view.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/ryrvV2q3VgPd4AOU1Zhv/image.png" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FFAM0TgogJugEU6hW2oz7%2Fkaiya-apps-library-64.png?alt=media&amp;token=fc159762-80fc-415d-813e-fb9512573eeb" alt="The Apps library in Tellius 6.4, with the Sorting, Access and User filters and Reset highlighted, the Published, Draft and Archived tabs highlighted, and published app cards" width="563"><figcaption></figcaption></figure>

At the top of the Apps library, you have the following controls:

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FJV4xzBN7ubU4D9cwFTbP%2Fan-apps-library.png?alt=media&amp;token=10269d05-c51d-44e2-9b90-028e01fa385c" alt="The Apps library with the Sorting, Access and User filters, the Published, Draft and Archived tabs, and app cards" width="563"><figcaption></figcaption></figure>

* **Show tour guide:** the question-mark icon beside the **Kaiya Apps** title. It starts a two-step tour of the **Published**, **Draft** and **Archived** tabs and **Create New App**. Its second step also mentions **Import**, which is turned off in Tellius 6.4. See [Guided tours for quick onboarding](/tellius-6.4/getting-started/say-hello-to-tellius/guided-tours-for-quick-onboarding.md).
* **Search:** filter apps by name.
* **Sorting:** sort by **Creation Date** or **Last Updated Date**, in the order **Newest First** or **Oldest First**.
* **Access:** show **All** apps, the apps **Created by me**, or the apps **Shared with me**.
* **User:** show the apps that belong to one user. Search the list of users, or select **Clear Filter** to remove the filter.
* **Reset:** returns the sorting and filters to their defaults.
* **Published**, **Draft** and **Archived:** the tabs that group apps by status.
* **List:** switches between the card view and a list view.
* **Create New App:** opens the app creation interface. See [How to create a Kaiya App](https://help.tellius.com/kaiya/kaiya-apps/how-to-create-a-kaiya-app).

Each card has a three-dot menu. Its options depend on the tab:

* **Published:** **Open**, **Archive**, **Transfer ownership** and **Delete**.
* **Draft:** **Open**, **Transfer ownership** and **Delete**.
* **Archived:** **Open**, **Unarchive**, **Transfer ownership** and **Delete**.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2F4hqxJ2KC48HGKZWj2B8e%2Fkaiya-apps-card-menu-64.png?alt=media&amp;token=4b427ff1-1a4f-428d-8755-db2c14d98ef0" alt="The three-dot menu on a published app card in Tellius 6.4, with Open, Archive, Transfer ownership and Delete" width="563"><figcaption></figcaption></figure>

The conversations in which apps were built are listed with your other conversations in Kaiya's chat history. To pick up where you left off, open an app and select **Open app assistant**, or select **Open in chat** from the **Actions** menu (three dots) at the top right of the App. The card menus in the Apps library don't have **Open in chat**. See [Anatomy of a completed app](https://help.tellius.com/kaiya/kaiya-apps/anatomy-of-a-completed-app).

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/rzwFssPbNGw0FO3udOLB/image.png" alt="" width="375"><figcaption></figcaption></figure>

### Learn more

* [How to create a Kaiya App](https://help.tellius.com/kaiya/kaiya-apps/how-to-create-a-kaiya-app)
* [Plans and versions in Kaiya Apps](https://help.tellius.com/kaiya/kaiya-apps/plans-and-versions-in-kaiya-apps)
* [Anatomy of a completed app](https://help.tellius.com/kaiya/kaiya-apps/anatomy-of-a-completed-app)
* [Live data in Apps](https://help.tellius.com/kaiya/kaiya-apps/live-data-in-apps)


---

# 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://help.tellius.com/tellius-6.4/kaiya/kaiya-apps.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.