> 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/data/preparing-your-business-views/create-a-new-business-view.md).

# Create a new Business View

Learn how to create a new Business View to organize datasets, configure advanced settings, and optimize performance for analytics.

* **Business View Name:** Provide a user-friendly name for your Business View.
* **Description:** A text field (up to 200 characters) for documenting the BV’s purpose or context.
* Click on **Show Advanced Settings** to view the following options.
* **Save to Fast Query Engine:** When enabled, stores the Business View in a high-performance query engine within Tellius. Improves data retrieval speed, especially for complex querie**s** on large datasets.
* **Hide in Search Engine:** When enabled, this Business View will be not be considered for natural language queries in Search and Assistant.
* **Enable deduplication:** Automatically identifies and removes duplicate rows in Snowflake Live and Redshift Business Views. Helps maintain data integrity and ensures “live” queries return unique rows.
* Click on **Create** to finalize the process and create a new Business View.

### Best Practices

* Enable **“Save to Fast Query Engine”** to get quick responses from heavily used or large BVs. Ideal if performance is critical and data changes can be periodically synced.
* If you’re testing or building a BV that’s not ready for general use, hide it from the search engine to avoid confusion.


---

# 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/data/preparing-your-business-views/create-a-new-business-view.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.