Adding a New User

You can add new users to the list of existing users in the Users dashboard.

Note:

Only Customer User Administrators can add new users.

To add a new user:

1. Sign in to Oracle Pulse as explained in the Accessing Oracle Pulse section in Introduction

   The Pulse dashboard is displayed by default.

2. From the navigation menu, click Users.

   The Users dashboard opens.

3. From the Users dashboard, select Create.

   The Create User popup is displayed.

4. Enter values in the following fields.

   Note:

   All fields are mandatory, and should not be left blank.
   • First Name
   • Last Name
   • Primary Email
5. Click Next.
6. From the Create User screen, go to the Assign Role section to add or remove roles from the user.
7. From Assign Roles, expand the Role Name dropdown, and select a role.

   Note:

   When the Windows Administrator for Non-Production Environments role is selected and added to a contact, and if the Windows Login For Cloud role is not added at the same time, then Pulse will automatically add the role Windows Login For Cloud after the contact is created.

   Role Name	Definition	Additional Information
   Linux Access for Prod and Non-Prod Middle Tier (custanalyst)	Assign this role in order to allow for the user to request login access to any of the non-production and production middle tier hosts. This role does not allow for requesting database hosts	Login accounts for the production and production support hosts are allowed after go-live. The pbrun commands no longer function to switch to the oracle target user after Go-Live.
   Linux Access for Prod and Non-Prod Database and Middle Tier (custdba)	Assign this role in order to allow for the user to request login access to any of the non-production and production database and middle tier hosts.	Login accounts for the production and production support hosts are allowed after go-live. The pbrun commands no longer function to switch to the oracle target user after Go-Live.
   Windows Login for Cloud	This role is required to be added prior to adding any Windows Administrator privileges.	This is for the login account. If only this role is assigned to the user, they will not be able to login into any Windows Servers.
   Windows Administrator for Non-Production Environments	Assign this role in order to allow for the user to be able to request login access privileges for all of the non-production Windows Servers.	This allows login access to any of the non-production Windows Servers, including Production Support. It does not allow for login access to any of the Production Windows Servers.
   Windows Administrator for Production Environments	Assign this role in order to allow for the user to be able to request login access privileges for all of the Production Windows Servers.	This allows login access to any of the Production Windows Servers, including Production Support. It does not allow for login access to any of the non-production Windows Servers.
   Linux Access for 3rd Party Prod and Non-Prod Hosts (cust3pp)	Assign this role in order to allow for the user to be able to request login access for any of the non-production and production database and middle tier hosts.	The Third Party Software services that are eligible for using the cust3pp privilege/role are defined as: 1. Third Party Software@OCI 2. OTO@OCI 3. OCI Infra Services Only@OCI 4. OPC Infra Services Only@OPC 5. Managed Database Cloud Service@OCI 6. Database and Weblogic ONLY@OCI
   Linux Access for 3rd Party Shared Prod and Non-Prod Hosts (cust3ppsh)	Assign this role in order to allow for the user to be able to request login access for any of the non-production and production database “Shared” Middle Tier hosts. Some Third Party software applications are directly installed onto the E-Business Suite or PeopleSoft middle tier servers.	The Third Party Shared services that are eligible for using the cust3ppsh privilege/role are defined as: 1. EBS@OCI 2. EBS@OPC 3. All PeopleSoft services @OPC 4. All PeopleSoft services @OCI
   Linux Restricted PHI - HIPAA compliance	Assign this role in order to allow for the user to be able to request login access for any of the Linux Server hosts that have the HIPAA regulation compliance requirement.	HIPAA – The United States Federal Government’s regulations designed to protect personal health information https://www.hhs.gov/hipaa/for-professionals/privacy/index.html
   Linux Restricted 21CFR11 - Food & Drug compliance	Assign this role in order to allow for the user to be able to request login access for any of the Linux Server hosts that have the Food and Drug Administration compliance requirement.	21 CFR Part 11 – https://www.fda.gov/regulatory-information/search-fda-guidance-documents/part-11-electronic-records-electronic-signatures-scope-and-application The United States Food and Drug Administration's Government Code applying to the Federal Regulations regarding the Electronic Records, and the Electronic Signatures
   Linux Restricted PHI and CFR11 - HIPAA and FDA compliance	Assign this role in order to allow for the user to be able to request login access for any of the Linux Server hosts that have the Food and Drug Administration and the HIPAA regulation compliance requirement.	Both HIPAA and 21 CFR Part 11 government compliance regulations
   Windows Restricted PHI - HIPAA compliance	Assign this role in order to allow for the user to be able to request login access for any of the Windows Server hosts that have the HIPAA regulation compliance requirement.	See the above three sections
   Windows Restricted 21CFR11 - Food & Drug compliance	Assign this role in order to allow for the user to be able to request login access for any of the Windows Server hosts that have the Food and Drug Administration compliance requirement.	See the above three sections
   Windows Restricted PHI and CFR11 - HIPAA and FDA compliance	Assign this role in order to allow for the user to be able to request login access for any of the Windows Server hosts that have the Food and Drug Administration and the HIPAA regulation compliance requirement.	See the above three sections

8. Expand the Service , then Instance dropdown, and then select a value.
9. Click Add Role.

   Note:

   The role will be added to Current Assigned Roles, but is not yet saved for the contact. You can remove the role going to the Actions menu, and clicking Delete, before saving the contact. The contact is created with the assigned role(s), when you click Create.
10. Optionally, add more roles to the user, as described in steps 6-8.
11. When all desired roles were added to the new user, click Create.

    The changes will be saved only if you click Create. The new user is now added to the list of users in the Users dashboard, and a confirmation message appears at the top right corner of the dashboard.

    Note:

    Overlapping of roles is not allowed. If a user is assigned a role for a specific instance, the user can not be assigned same role for the service and all instances of the service.