> 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/anatomy-of-a-completed-app.md).
# Anatomy of a completed app
Explore the anatomy of a completed app in Tellius—understand its structure, components, and configuration to build, review, and optimize analytics workflows.
Once generated, a Kaiya App is a fully rendered, multi-section interactive application. The following elements are present in a completed app:
#### Header banner
Each app opens with a styled header banner that displays the app title, a description of what the app covers, and optionally, category or channel tags (for example, "B2B Channel" and "Retail Channel"). The banner provides immediate context about the scope of the application.
#### Navigation tabs
Apps are organized into multiple tabs, each corresponding to a page defined in the plan. Tabs appear below the header and allow users to navigate between different views of the data. For example, an app might have tabs labeled Overview, Drivers, Segments, Rankings, and Recommendations.
#### Section-level guidance
Each section within a tab can include a guidance callout at the top. This callout has a title and a brief explanation of what the section displays and how to use it. It orients the user before they engage with the metrics and charts below.
#### Insights and summaries
Kaiya generates contextual text within each section. It is analytical narrative that references the specific metrics and dimensions in the app, explains what the data shows, and highlights what the user should pay attention to. These summaries are generated based on the data at the time of creation and updates when the app data is refreshed.
#### KPI cards
Key metrics are displayed as prominent KPI cards at the top of relevant sections. Each card shows the metric name (for example, Total ACV, Quota Attainment, Accounts at Risk, Renewal Pipeline), the current value, and a contextual subtitle explaining the metric (such as "Active B2B Contracts ($M)" or "YTD Team Performance").
#### Charts and tables
Depending on the analysis set out in the plan, each section contains a combination of visualizations: bar charts, line charts, tables etc. Chart types are selected by Kaiya based on what is most appropriate for the data and the analytical intent of the section.
#### Interactive filters
The app includes user-adjustable filters based on the dimensions defined in the plan. These filters let viewers slice the data by region, time period, segment, product, or any other available dimension without modifying the app itself.
### Actions on the App
The top of an App's page holds the controls for working with it.
#### **The header**
* **Show tour guide:** the question-mark icon beside the App's name. It walks you through the page: the plan, the Analysis tab, the App, the conversation, data freshness, versions, refresh, and sharing and publishing.
* **Business View:** the chip names the Business View the App is built on.
* **Actions (three-dot menu):**
* **Open in chat:** opens the App's conversation, so you can keep changing the App by asking Kaiya. See [How to customize a Kaiya App](/tellius-6.4/kaiya/kaiya-apps/how-to-customize-a-kaiya-app.md).
* **Go to App Source:** opens the conversation the App was created from, at the answer it came from. For an App remixed from another App, it opens the original App's conversation, or the original App's page when that App has no conversation you can open.
* **Share:** gives specific people access to the App.
* **Transfer ownership:** makes another user the App's owner.
* **Remix:** shown on an App someone shared with you, never on your own Apps. It duplicates the App into a new, empty conversation. Kaiya keeps the earlier requests that shaped the App as background, so you can ask for changes right away, but they don't appear in the copy's chat. Other messages, files, Missions and Apps from the original conversation don't come along. Change anything you like in the copy. The original App and its active version stay exactly as they are.
* **Publish:** publishes the draft, so it becomes the active version that people see.
* **Copy:** **Copy Plan** copies the App's plan as text, and **Copy Code** copies its generated code.
* **Delete:** removes the App. Available to admins and App owners only.
#### **Above the App**
* **Open app assistant:** the chat icon at the left of the tabs. It opens the App's conversation, with the App beside it. See [How to create a Kaiya App](https://help.tellius.com/kaiya/kaiya-apps/how-to-create-a-kaiya-app).
* **Plan, Analysis and App tabs:** the **Plan** tab lays out the App's pages and sections, the **Analysis** tab shows the steps that produce its data, and the **App** tab shows the App itself. See [Plans and versions in Kaiya Apps](https://help.tellius.com/kaiya/kaiya-apps/plans-and-versions-in-kaiya-apps).
* **Data Refreshed At:** the date and time of the last successful refresh. Everything on screen comes from that refresh, which is why the App responds straight away when you move a control.
* **Version:** lists the App's versions. Each edit updates the draft. When you publish the draft, or ask Kaiya to publish it, it becomes the **Active** version. You can switch to any version from this list. See [The version menu](https://help.tellius.com/kaiya/kaiya-apps/plans-and-versions-in-kaiya-apps#the-version-menu).
* **Refresh:** the circular-arrows icon opens a menu:
* **Refresh Now:** reruns every query straight away.
* **Schedule Refresh:** keeps the App current on its own. Choose a **Frequency** (**Hourly**, **Daily**, **Weekly**, **Monthly**, **Quarterly** or **Yearly**), a **Day** and a **Time**. **Next Run** shows when the next refresh will happen. Select **Save Schedule** to save it, or **Cancel**.
* **Refresh History:** shows what ran and whether it succeeded. An App that hasn't been refreshed yet shows **No refresh history available**.
* **Open this app in a new tab:** the expand icon at the far right.
---
# 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/anatomy-of-a-completed-app.md?ask=&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.
