Default users

The following table describes users that are present after installation, along with their groups.

Users and their groups

The following table describes users that are present after installation, along with their groups.
Note: impactadmin will not exist by default if you installed with LDAP mode: proxy, and must be manually created. For more information, see Creating users on an external LDAP server.
Table 1. Users present after installation

User name

Roles

Group

Description

icpadmin

Inherited from the group. Includes the following roles:
  • noi_operator: This role can open the Incident Viewer from the Event Viewer, but cannot click-through on the seasonality and grouping icons in the Incident Viewer. The Temporal group or Seasonal event panels are not available with this role. The See more info option is not available on individual events with this role. Also, policies cannot be approved or rejected with this role. This role can view alerts and run the runbooks that are linked to those alerts. This role does not have read access to the Runbook Library or other Runbook Automation pages.
  • noi_engineer: This role can perform all operations on the UI, except for managing policies. This role can view alerts and run the runbooks that are linked to those alerts. Also, this role has full read/write access to the Runbook Automation pages (Library, Execution, Automations, Triggers).
  • noi_lead: This role can perform all operations on the UI. With the noi_lead role, you can manage policies in Temporal policies. This feature is not available to other roles. This role can view alerts and run the runbooks that are linked to those alerts. This role has full read/write access to the Runbook Automation pages. Also, this role has full access to the administration of automation connections and API keys, and full access to the Runbook Automation settings.

icpadmins

Sample administrator user for Operations Management on a container platform.

icpuser

Inherited from the group

icpusers

Sample end user for Operations Management on a container platform.

impactadmin

Netcool/Impact-specific roles:
  • impactAdminUser

  • impactFullAccessUser

  • impactOpViewUser

  • impactMWMAdminUser

  • impactMWMUser

  • impactSelectedOpViewUser

  • impactUIDataProviderUser

  • impactWebServiceUser

  • ConsoleUser

  • WriteAdmin

  • ReadAdmin

  • impactRBAUser

icpadmins

Administrator user for Netcool/Impact.

smadmin

Dashboard Application Services Hub-specific roles:
  • iscadmins
  • chartAdministrator
  • samples
  • administrator
 

The administrator for Dashboard Application Services Hub. In a new installation, this user has permissions to administer users, groups, roles, and pages.

Default topology management users

  • inasm_operator: A user with this role can access the topology UI, and use it to search for and visualize the resources.
  • inasm_editor: A user with this role has the same permissions as the inasm_operator role. In addition, a user with the inasm_editor role can add comments to resources from the Topology Viewer Context (right-click) menu. A user with the inasm_operator role can view comments, but not add new ones.
  • inasm_admin: A user with this role has the same permissions as the inasm_editor role. In addition, a user with the inasm_admin role has access to a number of administrator tools, where they can define custom UI elements for the Topology Viewer.

For more information, see Configuring DASH user roles.

Default Runbook Automation users

For more information, see Administering users for Runbook Automation

Default DASH users

For more information, see DASH roles.

Default Netcool/OMNIbus and WebGUI users

For more information, see Default Netcool/OMNIbus users.

Default WebGUI roles

For more information, see Supplied roles.

Default WebGUI users and groups

For more information, see Supplied users and groups.

Warning: If you receive an error System goes into maintenance mode when trying to add roles to a user, see the troubleshooting topic System goes into maintenance mode.