> 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/how-to-customize-a-kaiya-app.md).

# How to customize a Kaiya App

Learn how to customize a Kaiya App in Tellius using natural language: modify charts, KPIs, filters, and layouts with version control and real-time updates.

Kaiya Apps are not static once created. You modify them the same way you built them: through conversation. There is no drag-and-drop editor or configuration panel. All changes are made through natural language instructions in the Kaiya conversation.

{% hint style="info" %}
In Tellius 6.4, you change an App in its own conversation, with the App in a panel beside it. Your changes collect in one draft, which the **Version** list shows with the next version number and a **Draft** badge. People you share the App with keep seeing the published version until you publish. Apps built before Tellius 6.4 work the same way. See [Apps built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-apps/apps-built-before-tellius-6-4), [How to create a Kaiya App](https://help.tellius.com/kaiya/kaiya-apps/how-to-create-a-kaiya-app) and [Plans and versions in Kaiya Apps](https://help.tellius.com/kaiya/kaiya-apps/plans-and-versions-in-kaiya-apps).
{% endhint %}

1. Open the app you want to modify.
2. Select **Open app assistant**, the chat icon at the left of the **Plan**, **Analysis** and **App** tabs. You can also select **Open in chat** from the app's three-dot menu. The app's conversation opens, with the app in a panel beside it.
3. Type your modification request in natural language at the bottom of the conversation panel.
4. Kaiya processes the instruction, and updates the app in the right panel. It saves the change as a draft and tells you which version is still live.

If the app changes while you have it open, a banner at the top of the panel says so. Select **View latest** to load the newest version.

#### What you can change

* Remove or add KPI cards
* Swap chart types (for example, change a bar chart to a line chart)
* Add or remove dimension filters
* Change time ranges or date filters
* Add, remove, or reorder sections (tabs)
* Change the theme or visual styling of the app
* Modify the insights or summaries

{% hint style="info" %}
Your changes collect in one draft, listed under **Version** with a **Draft** badge, for example **V2**. The published version stays live until you publish the draft. To review earlier versions, select **Version** at the top right of the app. To go back to one, select **Set as active** on that version. See [The version menu](https://help.tellius.com/kaiya/kaiya-apps/plans-and-versions-in-kaiya-apps#the-version-menu).<br>
{% endhint %}

### How versioning works in Kaiya Apps

Kaiya Apps use a versioning system to track changes and control what other users see.

* **Draft:** When you customize an app, your edits collect in one draft. An app has at most one draft. People you share the app with keep seeing the published version until you publish again.
* **Publishing**: Once you are satisfied with your changes, publish the draft. Ask in the conversation, for example *"publish the App"*, select a publish suggestion under **Actions**, or select **Publish** from the app's three-dot menu. Publishing turns the draft into a published version, and it becomes the **Active** version that everyone with access sees. Tellius keeps 10 versions for each app by default.
* **Published, Draft and Archived:** The Apps library groups apps by status on three tabs: **Published**, **Draft** and **Archived**. To archive an app, select **Archive** from its card's three-dot menu. See [The Apps library](https://help.tellius.com/kaiya/kaiya-apps#the-apps-library).

{% hint style="success" %}
**Change the app or Remix it?** Change the app itself when everyone who uses it should get the change: they see it once you publish. Select **Remix** when you want your own variation and the original should stay as it is. A remix is a separate copy that links back to the app and version it came from.
{% endhint %}

### Permissions and Sharing

Kaiya Apps use the same explicit user and group permission model as Vizpads. When you create an app, you are its owner. You can share it with specific users or groups, granting them view/edit access.

Modifications made affect all users who have access to that app once the changes are published. There is no per-user customization layer; the published version is the same for everyone with access.

### Refreshing data on a schedule

In addition to refreshing manually (select the refresh icon in the app's header, then **Refresh Now**), you can configure automatic refresh on a schedule. Select **Schedule Refresh** in the same menu to choose a frequency, day and time, and **Refresh History** to see what ran. While you look at a draft in the panel beside the conversation, the refresh icon is greyed out, because a refresh updates the published version. Switch to the published version to refresh. See [Anatomy of a completed app](https://help.tellius.com/kaiya/kaiya-apps/anatomy-of-a-completed-app). Schedules can also be set in natural language inside the app conversation. Examples:

* *"Refresh this app every day at 6 a.m."*
* *"Update the data every Monday morning."*
* *"Refresh hourly."*
* *"Stop the scheduled refresh."*

**When the Business View changes**

A Kaiya App is bound to the Business View it was built from. When the Business View is updated with new data or refreshed aggregations, those changes appear in the app on the next refresh (manual or scheduled).

If the schema of the Business View changes after the app was built (columns added, removed, renamed, or retyped), the existing app's refresh is rejected because the app's data bindings no longer match. In that case, recreate the app to pick up the new schema.


---

# 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/how-to-customize-a-kaiya-app.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.