Tenants and organizations

Tenants

A tenant is a separate customer area. Data and permissions do not cross from one tenant into another.

Open Tenants to see the customer areas available to you. Platform administrators can create tenants. Select a linked tenant name to open its detail page with status, key, IDs, metadata, timestamps, and the current user’s access context. Editing, disabling, and reactivation live on that detail page. Tenant administrators can update the name and metadata of their own tenant. Other roles have read-only access and role-appropriate links.

The list and detail page show the public number as #17 or Tenant no. 17. Browser workspace URLs use that number. The internal UUID may still appear in technical details and remains the identifier used for permissions and audit.

The tenant table offers Previous and Next navigation and page sizes of 25, 50, or 100 entries. It shows the exact number of tenants matching the current search, status filter, and access scope. Search, status, and page size remain in the URL. Changing one starts again on page 1; the browser retains the cursor history needed to return to an earlier page.

The tenant selector searches every authorized tenant on the server in pages of 50. Select Load more tenants to request the next page. If that request fails, the existing options remain available and the same action retries it. From the search field, use the arrow keys to reach an option and Enter to select it.

Disabling a tenant removes access to its customer data. Treat this as a major administrative action and confirm the selected tenant carefully.

Organization units

Open Organization after selecting a tenant. The tree can represent sites, regions, branches, departments, customers, or any other structure that fits the tenant.

The page initially loads only root entries. Expand an entry to load its direct children. Entries with no visible children have no expand control. Large root or child lists expose an explicit load-more action; repeated requests converge without duplicate entries. If a request fails, already loaded entries remain available and the retry action reloads only the failed page.

Search runs on the server across your complete visible hierarchy, including branches that have not been expanded. Each result shows its complete visible ancestor path. Changing or clearing the search never inserts a partial search page into the navigation tree.

When the tree has keyboard focus, use Up and Down to move between visible entries, Right to expand or enter a branch, Left to collapse or return to the parent, and Home or End to jump to the first or last visible entry.

To add an entry, select Unit anlegen or add a child below an existing entry. Enter a stable key, a clear name, a parent when needed, and simple metadata. The parent finder searches the complete visible hierarchy and can load additional result pages, so a target does not need to be expanded first.

You can edit an entry or move it to another parent. A move changes which users can reach that part of the tree, so check the target before saving. The platform rejects moves that would create a loop or exceed your permission scope.

An inactive parent also makes its children unavailable, even when a child is still marked active. The tree shows this as the effective status. Deactivation keeps the structure and history so it can be reviewed or reactivated later.