Overview of Preparing for HCM Application Users

During implementation, you prepare your Oracle HCM Cloud service for application users. Decisions made during this phase determine how you manage users by default. Most such decisions can be overridden.

However, for efficient user management, you're recommended to configure your environment to both reflect enterprise policy and support most or all users.

Some key decisions and tasks are explained in this chapter and introduced in this table.

Decision or Task	Topic
Whether user accounts are created automatically for application users	User Account Creation Option: Explained
How role provisioning is managed	User Account Role Provisioning Option: Explained
Whether user accounts are maintained automatically	User Account Maintenance Option: Explained
Whether user accounts are created for terminated workers that you load in bulk	User Account Creation for Terminated Workers Option: Explained
Ensuring that the Employee, Contingent Worker, and Line Manager abstract roles are provisioned automatically	Provisioning Abstract Roles to Users Automatically: Procedure

Some decisions affecting application users were made when the Security Console was set up. These decisions include:

• How user names are formed by default

• How passwords are formed and when they expire

• How users are notified of their sign-in details and password events, such as expiration warnings

You may want to review these settings for each user category on the Security Console before creating application users.