Tasks You Accomplish by Creating Users

When you create users, a number of other tasks are automatically performed. For example, users are sent emails with their user names and initial passwords, and the organization chart for your sales organization is built.

Whether or not a task is performed depends on the type of user created, as explained in the following sections.

Tasks Accomplished for all Users

The tasks in the following table are completed regardless of the type of user you create: setup users, sales administrators, or sales application users. These tasks are performed whether the user is created in the UI or through file import.

Task Accomplished	Comments
Notifies a user when a user account is created and provides sign-in details.	You can prevent emails from being sent either when creating individual users or by changing the default notification settings as described in the chapter Setting Up Applications Security. The application sends the user notifications only once, either on account creation or later, depending on the setup.
Automatically provision the job and abstract roles that provide the security settings users require to do their jobs.	Job and abstract roles are provisioned based on the autoprovisioning rules discussed later in this chapter.
Create rudimentary employee records. Employee records are used only if you're also implementing Oracle HCM Cloud, or if you implement it in the future.	You must specify each user either as an employee or as a contingent worker and enter the user's business unit and legal employer. When you create users, the application generates employee records for each user based on your entries.

Task Accomplished

Comments

Notifies a user when a user account is created and provides sign-in details.

You can prevent emails from being sent either when creating individual users or by changing the default notification settings as described in the chapter Setting Up Applications Security.

The application sends the user notifications only once, either on account creation or later, depending on the setup.

Automatically provision the job and abstract roles that provide the security settings users require to do their jobs.

Job and abstract roles are provisioned based on the autoprovisioning rules discussed later in this chapter.

Create rudimentary employee records. Employee records are used only if you're also implementing Oracle HCM Cloud, or if you implement it in the future.

You must specify each user either as an employee or as a contingent worker and enter the user's business unit and legal employer. When you create users, the application generates employee records for each user based on your entries.

Tasks Accomplished for Resource Users

When you create users as resources by entering resource information for the user, the application also performs the tasks shown in the following table.

Note: These tasks don't apply to setup users because they're not created as resources in the organization.

Task Accomplished	Comments
Create resources that can be assigned sales work such as leads, opportunities, and tasks.	Setup users aren't resources in your application and so can't be assigned to sales teams or view reports.
Create the resource reporting hierarchy used for reporting, forecasting, and work assignments.	When you create a resource, you specify a manager for that resource and build a resource reporting hierarchy.
Create resource records that individual users can update with personal information to complete a directory of your organization.	Setup users aren't resources and so their information doesn't appear in your sales organization directory.
Create a hierarchy of resource organizations.	Each resource is assigned to a resource organization, and the application builds a hierarchy of these organizations based on the resource reporting hierarchy. Setup users aren't resources and so aren't assigned to resource organizations.

Resource Reporting Hierarchy

You build a resource reporting hierarchy when you create sales application users by specifying the manager of each user you create, except for the user at the top of the resource hierarchy, for example, the CEO. If you're creating users in the user interface, then you must start by creating the user at the top of the hierarchy and work your way down. If you're importing users, then the order doesn't matter provided that all of your users are in the same file.

The resource reporting hierarchy doesn't have to mirror the formal reporting hierarchy, which is captured separately in the Oracle HCM Cloud application if it has been implemented. In Oracle CX Sales and Fusion Service, you can have only one resource reporting hierarchy reporting to one person.

Resource Organizations and the Resource Organization Hierarchy

You must assign each manager that you create as a user with his or her own resource organization. All direct reports who are individual contributors inherit their manager's organization. The application automatically builds a resource organization hierarchy, using the resource reporting structure. The resource organizations remain even if managers leave. You can reassign the resource organizations to their replacements.

In CX Sales and Fusion Service, resource organizations serve a limited purpose. The name of each resource organization appears in the application's Resource Directory, which users can access to obtain information about their coworkers, and in social media interactions. However, resource organizations aren't used in application security or for work assignments. You assign work to individuals rather than their organizations.

You access the Resource Directory from the Navigator menu. The resource organization names appear under each person's title. The resource organization names don't have to reflect the names of departments. Departments are tracked along with employee records in the Oracle HCM Cloud application if it has been implemented.