Subtenants

Subtenants allow large organisations to create isolated sub-organisations — branches, departments, faculties, or franchise locations — within a single Kiwire tenant. Each subtenant has its own admin users, roles, and WiFi user groups while sharing the same database and infrastructure.

'alt' => 'Dashboard overview', 'caption' => 'The default Kiwire dashboard layout', 'screenshot' => true, 'class' => '', ]) Drop images into: public/assets/img/docs/{page}/{filename} --}}

Image not uploaded yet public/assets/img/docs/subtenants/overview.png

What Is a Subtenant?

A subtenant is a logical sub-organisation within the main tenant. Unlike a full tenant (which has its own isolated database), a subtenant shares the same tenant database but uses subtenant_id scoping to separate its data. Subtenant admins can only see and manage resources tagged to their subtenant.

Common Use Cases

• Hotel chain — each property is a subtenant; property managers can manage their own guests without seeing other properties' data.
• University — each faculty or department is a subtenant; IT staff can manage their faculty's WiFi users independently.
• Retail franchise — each store location is a subtenant; store managers handle their own WiFi vouchers and user accounts.

Subtenant Fields

Field	Description
name	Display name of the sub-organisation (e.g., "East Wing Property", "Faculty of Engineering").
code	Short identifier code used in reports and exports (e.g., EAST, FoE).
is_active	Enable or disable the subtenant. Inactive subtenants block their admin logins.
description	Optional notes about the subtenant's purpose or location.
admin_count	Number of subtenant admin accounts assigned to this subtenant (computed).
user_count	Number of WiFi user accounts belonging to this subtenant (computed).

Data Isolation

Subtenant admins log in to the same Kiwire admin panel URL but see a filtered view of data. They can only:

• View and manage WiFi users with their subtenant_id
• View portal logs and sessions for their subtenant's zones
• Run reports filtered to their subtenant

Global configuration (connectors, portal templates, system settings) is managed by the main tenant admin and is not accessible to subtenant admins.

Zone Assignment

Zones (access points) can be restricted to a specific subtenant. Users who connect through a subtenant-assigned zone are automatically tagged with that subtenant's ID at registration or login.

Actions

• Create — add a new sub-organisation with name, code, and optional description.
• Edit — update name, code, description, or active status.
• Deactivate — immediately blocks all subtenant admins from logging in.
• Delete — blocked if the subtenant has associated users. Reassign or remove users first.

Required Permissions

view-subtenants · create-subtenants · update-subtenants · delete-subtenants