KUMA has a multitenancy mode in which one instance of the KUMA application installed in the infrastructure of the main organization (main tenant) enables isolation of branches (tenants) so that they receive and process their own events.
The system is managed centrally through the main interface while tenants operate independently of each other and have access only to their own resources, services, and settings. Events of tenants are stored separately.
Users can have access to multiple tenants at the same time. You can also select which tenants' data will be displayed in sections of the KUMA web interface.
In KUMA, two tenants are created by default:
The main tenant contains resources and services related to the main tenant. These resources are available only to the general administrator.
The shared tenant is where the general administrator can place resources, asset categories, and monitoring policies that users of all tenants will be able to utilize. Access to a shared tenant can be restricted to individual users.
If in user settings, the Hide shared resources check box is selected, the user cannot gain access to the Shared folder belonging to the shared tenant in the KUMA web interface in the Resources → <resource type>. This means that the user cannot view, edit, or otherwise use shared resources. The user is also unable to export shared resources and resource sets that incorporate resources from the shared tenant, either through the web interface or through the REST API.
If any of the services available to the user use shared resources, the user can see the names of these resources in the service settings, but cannot view or modify the resources. The content of active lists is available to the user even if the resource of this active list is shared.
The limitation does not apply to shared asset categories. Shared resources are also always available to users with the general administrator role.