Granting Additional Database Roles to User Accounts

The Add User script grants the minimum database roles required for a user to access Oracle Clinical and, if you specify that RDC access is required, RDC.

• Oracle Clinical default database roles: CONNECT, RESOURCE, RXCLIN_READ, RXC_ANY, AND OCL_ACCESS

• RDC default database roles: RXC_RDC and RDC_ACCESS

Users require additional database roles to do meaningful work in either Oracle Clinical or RDC. If you want a user to have read-only access, grant them RXC_ANY only.

To grant one or more database roles to a user:

1. Log in to SQL*Plus as SYSTEM.

2. Grant a role to a user:

   grant database_role to user_name

   For example: grant rxc_site to BSMITH

For more information, see:

• Additional Database Roles for RDC Users
  
• Additional Database Roles for Oracle Clinical Users
  

Additional Database Roles for RDC Users

You must explicitly grant every RDC Onsite user at least one database role. You can use the predefined database roles listed in the following table, selecting the role that matches the user's job function, or define additional database roles if you need to further fine-tune security privileges; see Creating and Modifying Database Roles.

These database roles are mapped to user roles in the USER_GROUP_ROLES installation reference codelist. Those user roles are used to define security privileges and to customize various aspects of the user interface. See Configuring Discrepancy Management for more information.

Table 1-3 Default Database Roles Defined for RDC Users

Database Role	Typical User Profile
RXC_DMGR	Data manager
RXC_SUPER	Data manager
RXC_CRA	Clinical Research Associate (CRA)
RXC_SITE	Site user, study coordinator, or other person at the remote site responsible for entering patient data
RXC_INV	Investigator at the remote site who can approve CRFs

Additional Database Roles for Oracle Clinical Users

The database roles assigned to a user determine which tasks a user can perform by controlling which menu paths the user can see in the user interface—for example, Study Design, Data Entry, or Administration—and within those areas, finer distinctions such as whether the user can make changes or only view existing data. Oracle Clinical includes many predefined database roles for this purpose. You can also define your own database roles; see Oracle Clinical Menu-Based Security for more information.

The roles in the following table apply to the Oracle Clinical discrepancy management system as well as to RDC. Give one of the above roles to each user who has one of the corresponding job functions and who will be working with discrepancies in Oracle Clinical's Maintain Discrepancy Database window.