Types of Sales Users

After you have signed up with your Oracle cloud service, you receive the user name and password for one initial user. This topic describes the privileges assigned to the initial user and to each of the different types of sales user that the initial user can create.

Note: The user types outlined are suggestions. The privileges granted to any user are entirely dependent on the assigned job and abstract roles so, for example, you can create a sales user who's also a setup user if you want.

Initial Users

As an initial user, you can perform many security tasks including creating other users. But you can't perform all the implementation tasks without assigning yourself additional privileges. For example, as an initial user you can submit scheduled processes but can't monitor their status.

These are the roles assigned to the initial user:

  • 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.

Setup Users

You can create setup users and provision them with the same job roles as the initial user so that they can help to perform the setup tasks. Setup tasks include managing security, enterprise setup, and creating other users, including other users with the same privileges.

In order that setup users can perform all implementation tasks, then in addition to assigning them the same roles as the initial user, you must also provision them with these roles:

  • Sales Analyst job role

    Makes it possible to create Sales Predictor rules.

  • Sales Administrator job role

    Permits the setup user to perform the same tasks as a sales administrator, such as set up and administer sales territories and processes.

  • Employee abstract role

    Provides the ability to run and monitor background processes.

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

Sales Administrators

Sales administrators, like other sales application users, are created as resources and are provisioned with job and abstract roles on the basis of the resource role they're assigned. You must create at least one sales administrator user.

Sales administrators are provisioned with the Sales Administrator job role, which includes permissions to manage the import of data from legacy systems, to configure the application according to business needs, and to set up and administer the sales territories and sales processes.

Sales administrator users can view sales transactional data and reports but can't configure sales application security or perform tasks related to an enterprise setup. Sales administrator users are provisioned with these roles:

  • Sales Administrator job role

  • Resource abstract role

  • Employee abstract role

To create sales administrators, follow the procedure outlined in the topic Creating Application Users.

Sales Application Users

You create sales application users as resources. As resources, application users can be assigned work and appear in your sales organization directory.

Sales users are provisioned with job and abstract roles according to the resource role they're assigned. The provisioned job roles don't permit sales users to perform implementation tasks, but they can perform a functional setup within the application, depending on their role. Provision sales application users with these roles:

  • The job roles that they require to perform their job

  • The Resource abstract role

  • The Employee or the Contingent Worker abstract role, depending on the employee type of the user

Sales Restricted Users

To do their jobs effectively, users must be able to view all the data that's relevant to their role. In some cases, however, users don't require the ability to create, update, or delete that data. You can create sales application users who have extensive privileges to view sales data, but limited privileges to change data, by provisioning users with these roles:

  • Sales Restricted User job role

  • Resource abstract role

  • Employee abstract role

Users assigned the Sales Restricted User job role can:

  • View accounts, contacts, leads and opportunities.

  • Create and modify reports and analytics.

  • Update, create and manage service requests.

  • Create, update and delete notes, tasks and activities for the Activity object.

  • Edit forecasts.

  • Access content in Sales Lightbox.

Assigning the Sales Restricted User job role to the following types of users provides these users with the visibility into sales data that they require, without assigning them excess privileges.

  • Back office users can view reports, edit forecasts, and view activities.

  • Service representatives can view customer information and can see leads and opportunities.

  • Seasonal or administrative users can view leads and opportunities.

The Essential User license provides a user with a read-only subscription to Oracle CX Sales and Fusion Service. You must provision the Sales Restricted User job role to users who are assigned an Essential User license.

Note: Some users may require read-only access to application data but don't need any data update privileges. For example, an auditor who reviews application data for regulatory reasons but isn't authorized to change anything. You can assign read-only access to individual users using the Read Only Mode (FND_READ_ONLY_MODE) profile option. For information on how to configure this access for a user, see the topic Provide Read-Only Access for Individual Users.