> 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-5.6/settings/advanced/data-flow.md).

# Data Flow

The **Data Flow** section allows administrators to enable or disable the Dataflow module across the Tellius environment.

<figure><img src="https://content.gitbook.com/content/VXyBWnsg0T2tHBl87viA/blobs/zbZLb46Wb6WQcB3HcMSP/image.png" alt="" width="563"><figcaption><p>Data flow settings</p></figcaption></figure>

***

#### 🔄 Enable Dataflow (Toggle)

* **Purpose**: This toggle controls access to the Dataflow module, which lets users design and execute transformation pipelines between datasets.
* **When Enabled**: Users will be able to:
  * Access the **Data Flow** tab.
  * Create and manage transformation flows.
  * Perform operations like joins, filters, aggregations, derived column creation, etc.
* **When Disabled**:
  * The Dataflow tab will be hidden for all users.
  * Existing flows will not be editable or executable until re-enabled.

***

#### 🔐 Admin Access

Only users with admin privileges can see or modify this setting.

***

#### ✅ Best Practice

Enable Dataflow if your organization requires in-platform data prep and ETL (Extract, Transform, Load) workflows without external tools.

Let me know if you’d like an example use case included too!


---

# 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-5.6/settings/advanced/data-flow.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.