Editing an Existing User

You can edit the first name and last name of an existing user. Also, you can add or remove policies from the user.

To edit an existing user:

1. In the Users dashboard, click on the name of the user, or click the three dots (…) menu from the Actions column.
2. Select View Details.

   The Update User popup is displayed.

3. From the User Details, edit the First Name and/or the Last Name.
   Note
   
   You cannot edit the Primary Email.
4. Click Next.
5. From the Update User screen, go to the Assign Policy section to add or remove policies from the user.
   Note
   
   Overlapping of policies is not allowed. If a user is assigned a policy for a specific instance, the user can not be assigned same policy for the service and all instances of the service.
6. From Assign Policies, expand the Policy Name dropdown, and select a policy.
   Note
   
   When the Windows Administrator for Non-Production Environments policy is selected and added to a contact, and if the Windows Login For Cloud policy is not added at the same time, then Pulse will automatically add the policy Windows Login For Cloud after the contact is created.

   Policy Name	Definition	Additional Information
   Linux Access for Prod and Non-Prod Middle Tier (custanalyst)	Assign this policy in order to allow for the user to request login access to any of the non-production and production middle tier hosts. This policy 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 policy 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 policy is required to be added prior to adding any Windows Administrator privileges.	This is for the login account. If only this policy is assigned to the user, they will not be able to login into any Windows Servers.
   Windows Administrator for Non-Production Environments	Assign this policy 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 policy 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 policy 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/policy 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 policy 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/policy 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 policy 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 policy 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 policy 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 policy 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 policy 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 policy 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

7. Expand the Service , then Instance dropdown, and then select a value.
8. Click Add .
   Note
   
   The policy will be added to Current Assigned policies, but is not yet saved for the contact. You can remove the policy going to the Actions menu, and clicking Delete, before saving the contact. The contact is created with the assigned policy(ies), when you click Create.
9. Optionally, add more policies to the user, as described in steps 6-8.
10. When all desired policies were added to the new user, click Save.

    The changes will be saved only if you click Save. 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 policies is not allowed. If a user is assigned a policy for a specific instance, the user can not be assigned same policy for the service and all instances of the service.