> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/account/account-management/account-structure.md).

# Account structure

The Heisenware platform follows a clear hierarchy, and understanding it is key to managing your Apps effectively.

An account holds all your organization's [members](/app-manager/members.md) and contains at least one workspace. It can also have [multiple workspaces](#multiple-workspaces) to separate Apps, data, and resources across different teams or locations.

By default, every new account has a single `Default Workspace`. This workspace is a container for your Apps and all their shared resources.

Inside it, you can build an unlimited number of Apps. Every App in a workspace shares access to that workspace's resources:

* **Databases**: A [timeseries database](/app-builder/build-backend/functions/storage/timeseries-database.md) (InfluxDB) for high-frequency sensor data, and a [relational database](/app-builder/build-backend/functions/storage/relational-database.md) (PostgreSQL) for structured data.
* [**File Explorer**](/app-builder/build-backend/file-explorer.md): Stores and manages the files your Apps use.
* [**Integrations (inbound)**](/app-manager/inbound-integrations.md): Shared connections to external systems.

The diagram below illustrates this structure:

<figure><img src="/files/psl5gT4dD0YPCo1XOjLQ" alt=""><figcaption></figcaption></figure>

## Multiple workspaces

For organizations with more complex needs, such as running separate Apps for multiple clients or separating distinct departments, Heisenware supports multiple workspaces in a single account. Each workspace is a completely separate environment with its own resources, keeping data and Apps fully isolated from one another.

{% hint style="info" %}
This is an advanced feature, off by default. If you have a use case for multiple workspaces, [contact us](mailto:hello@heisenware.com) to discuss your requirements.
{% 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 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://docs.heisenware.com/account/account-management/account-structure.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.