2 User roles

2 User roles

Overview

In the Users → User roles section you may create user roles.

User roles allow to create fine-grained permissions based on the initially selected user type (User, Admin, Super admin).

Upon selecting a user type, all available permissions for this user type are granted (checked by default).

Permissions can only be revoked from the subset that is available for the user type; they cannot be extended beyond what is available for the user type.

Checkboxes for unavailable permissions are grayed out; users will not be able to access the element even by entering a direct URL to this element into the browser.

User roles can be assigned to system users. Each user may have only one role assigned.

Default user roles

By default, Zabbix is configured with four user roles, which have a pre-defined set of permissions:

Guest role
User role
Admin role
Super admin role

These are based on the main user types in Zabbix. The list of all users assigned the respective role is displayed. The users included in disabled groups are stated in red. The Guest role is a user-type role with the only permissions to view some frontend sections.

The default Super admin role cannot be modified or deleted, because at least one Super admin user with unlimited privileges must exist in Zabbix. Users of type Super admin can modify settings of their own role, but not the user type.

Configuration

To create a new role, click on the Create user role button at the top right corner. To update an existing role, click on the role name to open the configuration form.

Available permissions are displayed. To revoke a certain permission, unmark its checkbox.

Available permissions along with the defaults for each pre-configured user role in Zabbix are described below.

Default permissions

Access to UI elements

The default access to menu sections depends on the user type. See the Permissions page for details.

Access to other options

Parameter		Description	Default user roles
			Super admin role	Admin role	User role	Guest role
Default access to new UI elements		Enable/disable access to the custom UI elements. Modules, if present, will be listed below.	Yes	Yes	Yes	Yes
Access to services
	Read-write access to services	Select read-write access to services: None - no access at all All - access to all services is read-write Service list - select services for read-write access The read-write access, if granted, takes precedence over the read-only access settings and is dynamically inherited by the child services.	All	All	None	None
	Read-write access to services with tag	Specify tag name and, optionally, value to additionally grant read-write access to services matching the tag. This option is available if ‘Service list’ is selected in the Read-write access to services parameter. The read-write access, if granted, takes precedence over the read-only access settings and is dynamically inherited by the child services.
	Read-only access to services	Select read-only access to services: None - no access at all All - access to all services is read-only Service list - select services for read-only access The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.			All	All
	Read-only access to services with tag	Specify tag name and, optionally, value to additionally grant read-only access to services matching the tag. This option is available if ‘Service list’ is selected in the Read-only access to services parameter. The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.
Access to modules
	<Module name>	Allow/deny access to a specific module. Only enabled modules are shown in this section. It is not possible to grant or restrict access to a module that is currently disabled.	Yes	Yes	Yes	Yes
	Default access to new modules	Enable/disable access to modules that may be added in the future.
Access to API
	Enabled	Enable/disable access to API.	Yes	Yes	Yes	No
	API methods	Select Allow list to allow only specified API methods or Deny list to restrict only specified API methods. In the search field, start typing the method name, then select the method from the auto-complete list. You can also press the Select button and select methods from the full list available for this user type. Note, that if certain action from the Access to actions block is unchecked, users will not be able to use API methods related to this action. Wildcards are supported. Examples: `dashboard.` (all methods of ‘dashboard.’ API service) (any method), `*.export` (methods with ‘.export’ name from all API services). If no methods have been specified the Allow/Deny list rule will be ignored.
Access to actions
	Create and edit dashboards	Clearing this checkbox will also revoke the rights to use `.create`, `.update` and `.delete` API methods for the corresponding elements.	Yes	Yes	Yes	No
	Create and edit maps
	Create and edit maintenance				No
	Add problem comments	Clearing this checkbox will also revoke the rights to perform corresponding action via `event.acknowledge` API method.			Yes
	Change severity
	Acknowledge problems
	Suppress problems
	Close problems
	Execute scripts	Clearing this checkbox will also revoke the rights to use the `script.execute` API method.
	Manage API tokens	Clearing this checkbox will also revoke the rights to use all `token.` API methods.
	Manage scheduled reports	Clearing this checkbox will also revoke the rights to use all `report.` API methods.			No
	Manage SLA	Enable/disable the rights to manage SLA.
	Invoke “Execute now” on read-only hosts	Allow to use the “Execute now” option in latest data for items of read-only hosts.			Yes
	Change problem ranking	Allow to change the problem ranking from cause to symptom, and vice versa.
	Default access to new actions	Enable/disable access to new actions.