> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/news/october-2026/workspace-wording-change.md).

# Business vertical is now called workspace

Daxium-Air now says "workspace" everywhere the web app used to say "business vertical". Only the wording changes.

**Published on October 7, 2026**

**Improvement: "business vertical" becomes "workspace".**

The environment that holds your forms, lists, reports, submissions, groups and apps now goes by a single name: the **workspace**. In the web app, it used to be called a **business vertical**. Wherever you saw "business vertical", you now see "workspace".

This is the word this documentation already uses, so the platform and its help pages now speak the same language.

**Only the label changes.** Your workspaces, their content, their groups and their access rights are exactly as they were. There is nothing to reconfigure.

**Technical names are not renamed.** The names used by the API and other technical identifiers stay as they are.

**Update your own material.** If your internal procedures, training slides or support articles mention "business vertical", replace it with "workspace" so your teams find the same word on screen and on paper.

Available on: **Web**

{% hint style="info" %}
Learn more in the [Daxium-Air Glossary](https://www.center.daxium-air.com/user-documentation/components-concepts-terminology#workspace) documentation.
{% 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://www.center.daxium-air.com/news/october-2026/workspace-wording-change.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.