In the right part of the Settings section the Users table will be displayed.
Click the Add user button and set the parameters as described below.
Name (required)—enter the user name. The length of the string must be 1 to 128 Unicode characters.
Login(required) – enter a unique user name for the user account. Must contain from 3 to 64 characters (only a–z, A–Z, 0–9, . \ - _).
Email (required)—enter the unique email address of the user. Must be a valid email address.
New password (required)—enter the password to the user account. Password requirements:
8 to 128 characters long.
At least one lowercase character.
At least one uppercase character.
At lease one numeral.
At least one of the following special characters: !, @, #, %, ^, &, *.
Confirm password (required)—enter the password again for confirmation.
Disabled—select this check box if you want to disable a user account. By default, this check box is cleared.
In the Tenants for roles settings block, use the Add field buttons to specify which roles the user will perform on which tenants. Although a user can have different roles on different tenants, the user can have only one role on the same tenant.
Select or clear the check boxes that control access rights and user capabilities:
Receive email notifications—select this check box if you want the user to receive SMTP notifications from KUMA.
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.
Can interact with RuCERT—select this check box if you want the user to be able to export incidents to RuCERT.
Only a user with the General Administrator role can select this check box.
Disable notifications about RuCERT messages—select this check box if you do not want the user to receive notifications about the messages in the incidents exported to RuCERT.
General administrators group—select this check box if you want to assign the main administrator role to the user. Users with the general administrator role can change the settings of other user accounts. By default, this check box is cleared.
Access to CII facilities—select this check box if you want the user to be able to assign CII categories to the assets and to interact with alerts and incidents related to the assets that are CII objects.
The user can assign a CII category to assets if the asset settings can be edited.
The user can view all alerts and incidents.
The user can access the CII column in the KUMA web interface sections that indicate whether CII objects are related to the displayed alerts and incidents.
If a user does not have access to CII objects:
The user cannot assign a CII category to assets. The user can still view and search CII category values and assets that have a CII category.
The user cannot access alerts and incidents that are related to assets with CII categories. The CII column is not displayed in the list of alerts and assets.
For assets with a CII category, the user cannot view statistics on alerts and incidents related to these assets.
If an asset did not yet have the status of a CII object when an alert or incident was generated but the CII status is added to it later, a user without access to CII objects will see that an asset is related to an alert or incident in the asset details area but will not be able to interact with the alert or incident in any way.
Click Save.
The user account will be created and displayed in the Users table.