> 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/administration/usage-and-support.md).
# Usage & Support
Turn live chat support, usage telemetry and session recording on or off for your workspace, each with its own switch.
Under **Settings → System → Administration → Usage & Support**, super users decide what support and usage data the workspace shares with Tellius. The page has three switches, and each one can be set on its own.
### The switches
**Live chat support:** lets the in-product live chat load for signed-in users, so they can reach Tellius Support from inside Tellius. With it off, the chat isn't offered. This is the same setting as **Live chat support** on the **Help & Support** page, so changing it on either page changes both. See [Help & Support](/tellius-6.4/settings/preferences/help-and-support.md).
**Enable Usage Telemetry:** sends product usage events and logs to Tellius. Session recording can stay off while this is on.
**Enable Session Recording:** records user sessions, so Tellius Support can follow the interactions that led to a problem. Session recording works through usage telemetry, so this switch is unavailable while **Enable Usage Telemetry** is off.
### Defaults and upgrades
* **New deployments:** **Enable Usage Telemetry** and **Enable Session Recording** are both on.
* **Upgraded deployments keep what they had.** In releases before Tellius 6.4, one setting, **Enable Session Recording**, controlled both product usage tracking and session recording. When a deployment upgrades, **Enable Usage Telemetry** takes the value that **Enable Session Recording** had, and **Enable Session Recording** stays as it was. If **Enable Session Recording** was never set, both switches stay off, as before.
{% hint style="info" %}
**You can change either switch at any time.** A super user can turn **Enable Usage Telemetry** and **Enable Session Recording** on or off here and select **Save**. Session recording works only while **Enable Usage Telemetry** is on.
{% endhint %}
{% hint style="success" %}
**Which switches to turn on?** Use **Enable Usage Telemetry** to share how the product is used, without recording anyone's screen. Turn on **Enable Session Recording** as well when you want Tellius Support to be able to follow the steps that led to an issue, and leave it off if your organization doesn't allow session recordings. Turn off **Live chat support** when your users should go through your own help desk instead.
{% endhint %}
### Save your changes
**Cancel** and **Save** at the top right become active once you change a switch. Select **Save** to apply the changes, or **Cancel** to go back to the saved settings.
### Who can see this page
Only super users see **Usage & Support** in Settings.
---
# 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/administration/usage-and-support.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.
