> 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.1/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="/files/ySvBRumVJEwWVGNHMIPw" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.tellius.com/tellius-6.1/settings/advanced/data-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.