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.

The following table lists the roles that users need to be assigned with, in Oracle Life Sciences IAMS, to access different applications. For details on assigning the roles, see Assign roles in Oracle Health IAMS.

Note:

For every Oracle Life Sciences SSO account, password expires every three months. Users receive a password reset reminder when approaching expiriation date.
Product Roles in Oracle Life Sciences IAMS Additional information

Oracle Clinical One Platform
  • clinicalone-CNE: this role is required for all users.
  • clinicalone-CNE_AssignGlobalRoles: this role is required for product administrators only.

    Note: Product administrators are responsible for creating studies and global users in Oracle Clinical One Platform. Users who have this role can give access to studies for themselves and other users.

 Once Oracle Life Sciences SSO accounts are created in Oracle Life Sciences IAMS with the required roles approved, administrators must set up users' accounts in Oracle Clinical One Platform. This is required to access either as a global user or as a study user:

Oracle Clinical One Digital Gateway
  • inthub-CNE: this role provides access Oracle Clinical One Digital Gateway.
  • clinicalone-CNE: this role provides access to Oracle Clinical One Platform, which is also required for Oracle Clinical One Digital Gateway users.

Oracle Clinical One Digital Gateway is a separate system from Oracle Clinical One Platform.

Users with these roles can start working right away.

Oracle Life Sciences IAMSOAuth Admin Console

  • system-admin: this role is required for any Customer Delegated Administrator (CDA) in order to work in the Oracle Life Sciences IAMS OAuth Admin Console.

The Oracle Life Sciences IAMS OAuth Admin Console is an application used to generate client IDs and secrets, as well as provision API developers with the right permissions for them to make API calls.

Users with this role can start working right away. See the Get started as a system administrator section in the REST API guide for the Clinical One Platform.

Related Topics

Parent topic: Create user accounts