> 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/settings/enabled-modules.md).
# Enabled Modules
Under **Settings → Modules → Enabled Modules**, admins can control which parts of Tellius are available in your workspace and which of them users land on first.
Turning a module off does more than hide it. The module stops appearing in the sidebar and becomes inaccessible, and Tellius adjusts navigation around what remains. If **Search** is disabled, for example, **Home** redirects to **Kaiya** instead. Disabling does not delete any content the module holds.
{% hint style="info" %}
**Turn a module off or limit it by role?** Turning a module off here removes it for everyone in the workspace. To keep a module on but hide it from some people only, set it to **No Access** in the custom role they hold. Check that none of their groups' roles gives it back, because **No Access** in one role never takes away access that another role gives. See [Custom roles](https://help.tellius.com/settings/users-and-access/custom-roles).
{% endhint %}
Each module has two independent controls:
**Enabled:** a toggle deciding whether the module is available and visible in the workspace at all.
**Primary:** a checkbox that decides whether the module appears in the main sidebar. Primary modules sit at the top of the sidebar with their icons, visible as soon as it opens. Everything else is collapsed under the **More** dropdown at the bottom, and users click it to reach the rest. You can select up to six primary modules. Modules keep the same order in the sidebar whether they are primary or under **More**, and **New Chat** always sits at the top. See [Navigating around Tellius](https://help.tellius.com/getting-started/say-hello-to-tellius/navigating-around-tellius).
When a module's **Enabled** toggle is off, its **Primary** checkbox greys out and cannot be ticked, because a module that isn't available can't be an entry point.
{% hint style="warning" %}
Enabling Kaiya also enables its related modules listed in this group. Every module can be made primary except **Kaiya Architect**, **Monitor** and **Help**, which show a dash in the **Primary** column. Kaiya Architect does not appear in the left navigation.
{% endhint %}
{% hint style="info" %}
Turning **Context** off hides the Context module workspace-wide. To limit who sees **Context** while it is enabled, set the **Context** module for each role under **Settings → Workspace → Users & Access → Roles**. See [Custom roles](https://help.tellius.com/settings/users-and-access/custom-roles).
{% endhint %}
### Kaiya group
Core Kaiya capabilities. Enabling Kaiya also enables the other modules in this group.
* **Kaiya:** the conversational AI assistant.
* **Missions:** scheduled analysis that runs on its own and delivers finished work.
* **Context:** the workspace where you manage the Skills and Memory Kaiya draws on. Learnings that have not moved to Memory appear there read only.
* **Apps:** AI-generated Apps built through Kaiya.
* **Kaiya Architect:** conversational data preparation and modeling for Business Views and Kaiya context models. It is not shown in the left navigation.
### Platform modules
Analytics and platform features outside the Kaiya product suite.
* **Data:** datasets, connections, and Business Views.
* **Insight:** automated Insights, where Tellius surfaces drivers, trends, and comparisons from your data.
* **Vizpad:** Vizpads and visual analysis.
* **Feed:** the observations feed that detects anomalies and sends alerts.
* **Help:** in-product help and documentation links.
* **Monitor:** system health and resource utilization.
* **Predict:** machine learning models, including segments, predictors, and paths
* **Projects:** grouped collections of artifacts.
* **Search:** natural language search.
Click **Save** to apply your changes, or **Cancel** to discard them. Save stays inactive until something changes.
{% hint style="info" %}
Recheck the Primary modules once because a workspace with no reachable primary module leaves users with nowhere sensible to land.
{% endhint %}
---
# 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/settings/enabled-modules.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.
