---
title: "Overview"
description: "Learn how organizations in the walt.id Enterprise Stack group tenants and sub-tenants to keep services and data separate."
stack: "Enterprise Stack (commercial) — version 1.2.1"
stack_version: "1.2.1"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/enterprise-stack/administration/organizations/overview
generated: 2026-11-11
---
# Overview

The Organization is your account. Under the Organization you can group customers as tenants, sub-tenants, or create a tenant of your own. This way services and their data can be kept virtually separate, enabling you to easily manage different customers or services of your own under one roof. Also, this structure allows you to build and sell B2B2C products (e.g., you can resell to business clients who offer consumer products).

While the Enterprise Stack allows for multiple Organizations, on-prem Enterprise deployments should always have one Organization.

An organization identifier might be `waltid`

## Organization Hostnames

Every organization is reached through its own hostname, `{organizationId}.{baseDomain}`, for example `waltid.enterprise.localhost`. The [`baseDomain`](https://docs.walt.id/enterprise-stack/setup/configurations/config-files/enterprise.md) comes from `enterprise.conf`. Creating an organization registers this hostname automatically as a [host alias](https://docs.walt.id/enterprise-stack/administration/access-and-permissions/host-alias.md) named `{organizationId}.default_alias`, and deleting the organization removes it.

The Enterprise API reads the hostname of each request (the first `X-Forwarded-Host` value if a reverse proxy sets it, otherwise `Host`, without the port) and looks it up in the host alias table to find the organization. This is how public endpoints that carry no token and no `target`, such as the OpenID4VCI and OpenID4VP endpoints or a hosted trust registry, are mapped to an organization's configuration. A hostname that is not in the table is rejected with an `Unknown host alias` error. The bare `baseDomain` belongs to no organization and only serves global endpoints, such as the [super admin](https://docs.walt.id/enterprise-stack/setup/configurations/config-files/superadmin-registration.md) and `admin` endpoints.

Add [host aliases](https://docs.walt.id/enterprise-stack/administration/access-and-permissions/host-alias.md) to serve an organization or tenant from your own domain, for example `credentials.example.com`. The default hostname stays valid next to it.

**Note:**

The hostnames must be routable wherever the API is deployed: DNS and TLS for every organization hostname or alias, and a proxy that forwards the original host. Since on-prem deployments typically run one organization, that usually means a single hostname, `{organizationId}.{baseDomain}`, plus the base domain itself for global endpoints. A wildcard record is only needed to serve many organizations. For the local Docker Compose setup, see [Using custom organisation names](https://github.com/walt-id/waltid-enterprise-quickstart#using-custom-organisation-names).

## Get Started

- [Create Organization](https://docs.walt.id/enterprise-stack/administration/organizations/create.md) - Learn how to create an organization.
- [Import and Export](https://docs.walt.id/enterprise-stack/administration/organizations/import-export.md) - Move an organization or tenant to another installation.
