Repository navigation
Tenancy
Version 3.6.0 supports multiple independent organizations in one Kendo Tournament Manager installation. An organization is called a tenant.
Each tenant has its own users, clubs, participants, tournaments, teams, fights, results, statistics and uploaded images. Everything the application creates belongs to exactly one tenant, and no tenant can read or modify another tenant's records.
The feature is enabled with enable.tenancy=true, which is the default. With enable.tenancy=false, the whole installation uses the single Default organization and organization management is not available.
On an empty installation, the first successful login creates the Default organization and an account with the SUPER_ADMIN role. If an active organization already exists but there are no users, the first account is instead added to that existing organization. In both cases, the first account is a SUPER_ADMIN.
SUPER_ADMIN includes every permission available to ADMIN, plus platform-level organization management.
Users do not select an organization on the login page. The application opens the organization last used by that user.
If the account is available in more than one organization, open the profile menu in the upper-right corner and select an organization from the Organization list. The selection immediately refreshes the session and becomes the organization used on the next login.
The selector is not shown when the user only has one available organization.
An ADMIN or SUPER_ADMIN creates users for the organization currently selected in their session. New users are therefore initially associated with that organization and start there when they first log in.
An account is global and can be assigned to several organizations. Its password, profile data and roles are stored once; only the account-to-organization memberships vary. Each assigned organization becomes available from the profile menu after the user has authenticated.
Only SUPER_ADMIN users can manage organizations. Open Administration -> Tenants to:
- Create an organization and its first
ADMINuser. - Rename an organization or enable or disable it.
- Delete an organization.
Deactivating a tenant prevents new logins and rejects requests made with existing tokens, but retains its data so it can be reactivated later.
Deleting an organization permanently removes its tournaments, clubs, participants, fights, teams, statistics, images and every other organization-scoped record, then removes the tenant registration itself. User memberships in that organization are removed. A global account that belongs to another organization is preserved; an account that belonged only to the deleted organization is removed. This action cannot be undone; make a verified database backup first.
The reserved Default organization cannot be deleted.
A single-organization installation can disable tenancy with:
enable.tenancy=falseIn the Docker .env file this is the enable_tenancy variable. All users then work in Default; the organization selector and Administration -> Tenants are hidden.
Guest access through a tournament QR code remains tenant-safe. The backend derives the tenant from the referenced tournament; QR payloads and browser requests do not select a tenant themselves.
The 3.6.0 migration moves all data from an existing single-tenant installation into Default (tenant ID 1). Follow the backup and migration procedure in Updating Versions: 3.5.x to 3.6.0.