3Oracle Loyalty Users and Role Provisioning

This chapter contains the following:

Oracle Loyalty Users
Tasks You Accomplish by Creating Oracle Loyalty Users
Provisioning Enterprise Roles to Oracle Loyalty Users
Steps for Setting Up Role Provisioning for Oracle Loyalty

Oracle Loyalty Users

After you have signed up with Oracle Loyalty, you receive the user name and password for one initial user. The initial user is provisioned with the job roles and privileges necessary to perform many implementation tasks, including creating other users. This topic describes the privileges assigned to the initial user and to each of the different types of user that the initial user can create.

Initial Users

The initial user is configured to perform many security tasks, including the creation of other users, however, the initial user can't perform all implementation tasks without assigning themselves additional privileges. For example, the initial user can't run scheduled processes.

The roles assigned to the initial user are:

Application Implementation Consultant job role

Provides access to all setup tasks across all products.
IT Security Manager job role

Provides access to security tasks, including the ability to assign other job and abstract roles.
Application Diagnostic Administrator job role

Provides access to diagnostic tests and data.

The initial user can create each of the following types of user.

Users and Security

You can create setup users and provision them with the same job roles as the initial user so that they can help to perform all the standard implementation set up tasks for your Oracle Loyalty implementation. Setup tasks include managing security, enterprise setup, and creating other users, including other users with the same privileges.

You also need to provision setup users with the following additional roles:

Loyalty Administrator job role

Permits the setup user to perform the same functional setups as a Loyalty Administrator.
Employee abstract role

Provides the ability to run and monitor background processes.

Setup users aren't part of the business organization so they aren't created as resources in Oracle Loyalty and aren't provisioned with the Resource abstract role. You can't assign work to them and they can't view transaction data or reports. However, setup users do have the privileges to assign themselves additional roles to make those tasks possible. For information about creating setup users, see Getting Started with Your Sales Implementation at http://docs.oracle.com/.

Loyalty Marketing Manager

Oracle Loyalty marketing managers, like other Oracle Loyalty application users, are created as resources and are provisioned with job and abstract roles on the basis of the resource role they're assigned.

Oracle Loyalty marketing managers are provisioned with the Loyalty Management Duty and from this duty they inherit the Partner Account Maintenance Duty and the Loyalty Management Duty. These duties include permissions to:

Manage programs
Manage promotions
Configure product catalog user interfaces
Manage product groups
Manage products
Manage members
Manage transactions

Loyalty Program Administrator

Oracle Loyalty program administrators are provisioned with the Loyalty Management Duty and the Loyalty Administrator Duty, which include permissions to:

Manage programs
Manage promotions
Configure product catalog user interfaces
Manage product groups
Manage products
Manage members
Manage transactions
Manage bulk membership administration batches
Set up Loyalty offerings
Configure the Loyalty user interface
Schedule Loyalty jobs
View Loyalty import and export object type data
View Loyalty import and export mapping object type data
View Loyalty import and export activity object type data

Loyalty Member Services

Service representatives are provisioned with Loyalty Member Services Duty, which includes permissions to:

Manage members
Manage referrals
Manage transaction disputes
Manage vouchers and membership cards
Manage members' promotion enrollment
Set up members' incentive choice for a promotion
Manage membership renewals and cancellations

Tasks You Accomplish by Creating Oracle Loyalty Users

When you create users in Oracle Loyalty, a number of other tasks are automatically performed. For example, users are sent e-mails with their user names and initial passwords, and the organization chart for your 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, Loyalty Administrators, or Loyalty Application users. These tasks are performed whether the user is created in the UI or if they're imported into Oracle Loyalty.

The following table describes the tasks that occur when a user is created.

Task Accomplished	Comments
Notifies a user when a user account is created and provides sign-in details.	You can prevent e-mails 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 CX Human Capital Management, 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.

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

You can prevent e-mails 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 CX Human Capital Management, 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, Oracle Loyalty 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.

The following table describes the tasks that occur when you create users as resources.

Task Accomplished	Comments
Create resources that can be assigned Oracle Loyalty work such as creating programs, creating promotions, and enrolling members.	Setup users aren't resources in your application and so can't view transactions or reports.
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 organization directory.

Provisioning Enterprise Roles to Oracle Loyalty Users

This topic describes how role provisioning is implemented in Oracle Loyalty.

About Provisioning Roles to Users

Oracle Loyalty users gain access to data and functions through the job and abstract roles they're assigned. Roles are provisioned to users through predefined role provisioning rules, or through provisioning rules you create using the Manage HCM Role Provisioning Rules task from the Setup and Maintenance work area. Each provisioning rule, also known as a role mapping, defines the following:

The job and abstract roles to provision
The conditions that must exist for the roles to be provisioned
Whether or not role provisioning is automatic

The provisioning rules use resource roles as the condition for provisioning job and abstract roles to Oracle Loyalty users. Each provisioning rule can use one resource role and you assign a resource role to each user you create.

Note: The resource role should not be confused with job or abstract roles, which provide the user's security permissions. The resource role merely describes the role the user plays in the organization and provides the job title which appears in the company resource directory for the user. Resource roles are used in provisioning roles to application users but not to setup users.

If you select the automatic role provisioning option for a rule, then roles are provisioned automatically when you create the user if the user matches the rule conditions. It doesn't matter if you create users manually in the user interface, or import them from a file.

Role provisioning rules work as follows:

When you create the Loyalty Program Manager user, you assign that user the Loyalty Marketing Manager resource role provided by Oracle, which is the user's title in the organization. You also create the user as an employee person type.
The role provisioning rules use the resource role and person type values as conditions.
When you create a user as an employee with the Loyalty Marketing Manager resource role, then the conditions are true and the rules automatically assign the user with the Loyalty Manager job role and the Resource abstract role, and with the Employee abstract role.

Note: Oracle provides a predefined rule which automatically assigns the Employee abstract role to all active users who are created as employees, including users who aren't resources, such as setup users. The Contingent Worker abstract role is automatically assigned to active non-employee users (users created as contingent workers).

Steps for Setting Up Role Provisioning for Oracle Loyalty

Before you create setup or application users, you must perform some role provisioning setup tasks, such as creating additional resource roles or role provisioning rules. These tasks are described in this topic.

Create Additional Resource Roles

Resource roles are provided for the most commonly used job roles included with the application. Review the predefined resource roles provided in Oracle Loyalty and determine whether or not you require additional resource roles.

You create additional resource roles using the Manage Resource Roles task from the Setup and Maintenance work area in the following circumstances:

You're creating users with job roles that aren't provided by Oracle, or your organization uses different job titles. For example, you must create a CEO resource role if you want to include the CEO title in your organization chart. It's not one of the resource roles created for you.
You want to provision a user or a subset of users with special privileges.

For information on creating additional resource roles, see the topic Creating Additional Resource Roles.

Create Additional Role Provisioning Rules

Role provisioning rules are provided for the most commonly used resource roles included with the application. You must create rules for all other resource roles you use.

When you're creating provisioning rules for users who are resources, each rule must provision both the relevant job role and the Resource abstract role. You can assign multiple job roles to an individual. For information about creating additional provisioning rules, see the topic Creating Rules to Automatically Provision Job Roles to Users.