3 Create user accounts in Oracle Life Sciences Identity and Access Management Service (IAMS)

• Oracle Life Sciences SSO accounts
  You can create Oracle Life Sciences SSO accounts for product administrators, Oracle Clinical One Platform study users, and Oracle Clinical One Digital Gateway users in Oracle Life Sciences Identity and Access Management Service (IAMS). But, you must use Oracle Clinical One Platform to add a user to a study in Oracle Clinical One Platform and add an Oracle Clinical One Digital Gateway global user.
• Create an Oracle Life Sciences single sign-on
  As the delegated administrator, you can use Oracle Life Sciences Identity and Access Management Service (IAMS) to create Oracle Life Sciences single sign-on (SSO) account for each Oracle Clinical One Platform or Oracle Clinical One Digital Gateway user.
• User roles in Oracle Life Sciences IAMS for all applications
  Roles provide permissions for users to work in studies in Oracle Life Sciences products. Different roles provide access to different products and different sets of permissions.
• Create product administrator accounts
  To create a product administrator for Oracle Clinical One Platform, a delegated administrator must create an Oracle Life Sciences single sign-on (SSO) in Oracle Life Sciences IAMS, assign roles, and then add the user as a global user in Oracle Clinical One Platform. The product administrator is typically the first user account you create.
• Provide user access to Oracle Clinical One Digital Gateway
  To provide a user access to Oracle Clinical One Digital Gateway, a Customer Delegated IAMS Administrator (CDA) must create an Oracle Life Sciences single sign-on (SSO) user account and assign the appropriate product roles in Oracle Life Sciences Identity and Access Management Service (IAMS). Then, add the user account as a global user and assign the appropriate global roles in Oracle Clinical One Platform.
• Access requests
  If you use the approval process to grant users access to applications, it generates access requests. The user with the Approver role must approve or reject these requests. If approved, the user can access the application. If your organization does not use the approval process, assigned roles take effect immediately.