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	`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 Netcool/OMNIbus users	See Netcool/OMNIbus V8.1.0 documentation: users
Default Runbook Automation users	See Administering users for Runbook Automation
Default Web GUI users	See Netcool/OMNIbus V8.1.0 documentation: Default IBM® Tivoli® Netcool/OMNIbus users
Default Web GUI users	See Netcool/OMNIbus V8.1.0 documentation: Supplied roles
Default Web GUI users	See Netcool/OMNIbus V8.1.0 documentation: Web GUI users and groups
Supplied Netcool/OMNIbus users	See Netcool/OMNIbus V8.1.0 documentation: 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.