User groups allow to group users both for organizational purposes and for assigning permissions to data. Permissions to monitoring data of host groups are assigned to user groups, not individual users.
It may often make sense to separate what information is available for one group of users and what - for another. This can be accomplished by grouping users and then assigning varied permissions to host groups.
A user can belong to any amount of groups.
To configure a user group:
The User group tab contains general group attributes:
All mandatory input fields are marked with a red asterisk.
|Group name||Unique group name.|
|Users||To add users to the group click Select button.|
|Frontend access||How the users of the group are authenticated.
System default - use default authentication
Internal - use Zabbix authentication. Ignored if HTTP authentication is set
Disabled - access to Zabbix GUI is forbidden
|Enabled||Status of user group and group members.
Checked - user group and users are enabled
Unchecked - user group and users are disabled
|Debug mode||Mark this checkbox to activate debug mode for the users.|
The Permissions tab allows you to specify user group access to host group (and thereby host) data:
Current permissions to host groups are displayed in the Permissions block.
If current permissions of the host group are inherited by all nested host groups, that is indicated by the including subgroups text in the parenthesis after the host group name.
You may change the level of access to a host group:
Use the selection field below to select host groups and the level of access to them (note that selecting None will remove host group from the list if the group is already in the list). If you wish to include nested host groups, mark the Include subgroups checkbox. This field is auto-complete so starting to type the name of a host group will offer a dropdown of matching groups. If you wish to see all host groups, click on Select.
Note that it is possible for Zabbix Super Admin users in host group configuration to enforce the same level of permissions to the nested host groups as the parent host group.
The Tag filter tab allows you to set tag based permissions for user groups to see problems filtered by tag name and its value:
To select a host group to apply a tag filter for, click Select to get the complete list of existing host groups or start to type the name of a host group to get a dropdown of matching groups. If you want to apply tag filters to nested host groups, mark the Include subgroups checkbox.
Tag filter allows to separate the access to host group from the possibility to see problems.
For example, if a database administrator needs to see only "MySQL" database problems, it is required to create a user group for database administrators first, than specify "Service" tag name and "MySQL" value.
If "Service" tag name is specified and value field is left blank, corresponding user group will see all problems for selected host group with tag name "Service". If both tag name and value fields are left blank but host group selected, corresponding user group will see all problems for selected host group. Make sure a tag name and tag value are correctly specified otherwise a corresponding user group will not see any problems.
Let's review an example when a user is a member of several user groups selected. Filtering in this case will use OR condition for tags.
|User group A||User group B||Visible result for a user (member) of both groups|
|Host group||Tag name||Tag value||Host group||Tag name||Tag value|
|Templates/Databases||Service||MySQL||Templates/Databases||Service||Oracle||Service: MySQL or Oracle problems visible|
|Templates/Databases||blank||blank||Templates/Databases||Service||Oracle||All problems visible|
|not selected||blank||blank||Templates/Databases||Service||Oracle||Service:Oracle problems visible|
Adding a filter (for example, all tags in a certain host group "Templates/Databases") results in not being able to see the problems of other host groups.
A user may belong to any number of user groups. These groups may have different access permissions to hosts.
Therefore, it is important to know what hosts an unprivileged user will be able to access as a result. For example, let us consider how access to host X (in Hostgroup 1) will be affected in various situations for a user who is in user groups A and B.
“Read-write” permissions have precedence over “Read” permissions starting with Zabbix 2.2.