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

# Account, space and users

Everything in {inject-brand-name} is organised in a simple hierarchy: **users** log in, **accounts** hold the contract, and **spaces** are where the daily work happens. Understanding this structure once makes the whole portal intuitive.

```
User (person or system)
 └─ Account — plan, billing, invoices, user management
     └─ Space — transactions, payment methods, terminals, settlements, settings
         └─ Space view — shared configuration, separate presentation
```

### The building blocks

| Level          | Purpose                                                                                                                                                                      | Typical questions answered here                       |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| **User**       | Personal login for people (human users) or systems (application users for the API). One user can access several accounts.                                                    | Who can log in? Who has which role?                   |
| **Account**    | The contractual container. Holds your plan and features, billing information, invoices and financial balance. Each account has a unique ID used by our support team.         | What am I paying? Who is on my team?                  |
| **Space**      | The data container for operations. All transactions from all sales channels, terminal configurations, e-commerce integrations, settlements and manual tasks live in a space. | Where are my payments? How is my checkout configured? |
| **Space view** | A view on a space with shared configuration but separate presentation (e.g. translations, currency display).                                                                 | How do I run country variants of the same shop?       |

{% hint style="info" %}
By default, one account is linked to exactly one space — most merchants never need more. Additional spaces can be created under **Account > Spaces > Spaces**, space views under **Space > Customize > Space Views**.
{% endhint %}

### One space or several?

{% tabs %}
{% tab title="Use space views" %}
**Use space views when your shops share the same configuration.**

Example: a multi-country webshop selling identical products, but with country-specific currency and translations. One space, one set of connectors — separated by space views. Specific configurations such as connectors or payment methods can still be applied per view.
{% endtab %}

{% tab title="Use separate spaces" %}
**Use separate spaces when the setups are truly independent.**

Example: an online shop selling products plus a call centre selling services, with different databases and processes. Spaces are completely isolated — data and configuration cannot be shared between them. Note: running multiple spaces can increase monthly fees.
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
**Limitations:** there is a default limit on the number of spaces and space views per account. If you need more, contact our support team and we will check whether the limit can be raised.
{% endhint %}

### Dive deeper

* [**User, Account and Space**](/documentation/readme/account-structure/user-account-and-space.md) — what you find on each level of the portal, step by step.
* [**Space Views**](/documentation/readme/account-structure/space-views.md) — setting up views for multi-shop scenarios.
* [**Users, Roles and Invites**](/documentation/readme/account-structure/permission-concept.md) — human users vs application users, roles, permissions and invites.
* [**Manual Tasks**](/documentation/readme/manual-tasks.md) — how the platform asks for your decision when automation stops.