# Account Structure

The Heisenware platform is organized in a clear hierarchy. Understanding this structure is key to managing your projects effectively.

An Account holds all your organization's [Members](https://www.google.com/search?q=../app-manager/members) (users) and contains at least one Workspace. It can, however, have [multiple workspaces](broken://pages/x2eB0zfDuhUxnsn8Dhov) to separate apps, data, and resources of different teams or locations.

By default, every new account has a single `Default Workspace`. This Workspace acts as a container for your applications and all their shared resources.

Within this Workspace, you can build an unlimited number of Apps. All apps built inside a Workspace share access to that Workspace's resources, which include:

* **Databases**: An [InfluxDB](broken://pages/WbN12C0jrmgbmfoePmC2) for time-series data and a [PostgreSQL](broken://pages/KnP2ytrxx6Z18AeLCpks) database for relational data.
* [**File Server**](/app-builder/build-backend/file-explorer.md): For storing and managing files used in your apps.
* [**Integrations**](/app-manager/integrations-inbound-connections.md): Shared connections to external systems.

This structure is illustrated below:

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

## Multiple Workspaces

For organizations with complex needs, such as managing projects for multiple clients or separating distinct departments, Heisenware supports multiple Workspaces within a single account. Each Workspace provides a completely separate environment with its own set of resources, ensuring data and apps are fully isolated from one another.

{% hint style="info" %}
This is an advanced feature that is not enabled by default. If you have a use case for multiple Workspaces, please [contact us](mailto:hello@heisenware.com) to discuss your requirements.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.heisenware.com/account/account-management/account-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.