Adding and editing users in an Oracle-hosted environment

Note: This procedure does not apply for self-hosted installations. For more information, see Adding and editing users in a self-hosted environment.

For Oracle-hosted installations, you create users in the Oracle Health Sciences Identity and Access Management Services console. However, you manage the user's access rights on the Empirica Signal Users page.

1. To add a user:

A. Log in to the IAMS console.

B. Create the user.

For more information, see the IAMS Delegated Administrator Quick Reference Guide on the My Oracle Support website.

C. Assign the Signal role to the user.

After a few minutes, the user is created in Empirica Signal, and an entry appears in the userprovisioning.log file on the application server.

The user is provisioned with the default user profile specified as a site option.

D. Optionally, change the roles and permissions assigned to the user.

E. If you plan to use the Topics feature of Empirica Signal, optionally do the following for newly created users:

i. Add the user to one or more work teams.

ii. Assign work team permissions to the user.

2. To edit a user's access rights:

A. Log in to the Empirica Signal application.

B. In the Manage Users section, click Edit Users.

The Users page appears.

C. Locate the user to edit in the table.

D. Click the row menu () for the user, and then click Edit.

Note: You can edit only users in your login group.

The Edit User page appears.

E. Fill in the fields.

F. Click Save.

Your changes are saved.

Field descriptions

Field	Description
Authentication (read only)	Indicates that the user is authenticated with single sign-on.
Username (read only)	Unique name of the user account (up to 100 characters). You can reuse deleted user names. Does not apply if LDAP authentication is used. For more information, see About user names.
First Name (read only)	First name of the user (up to 64 characters).
Last Name (read only)	Last name of the user (up to 64 characters).
Email (read only)	Email address of the user. This address (or addresses, separated by a comma) is used: As the default email address if the user chooses to be notified of data mining run completion notification. When a message is generated by a topic email notification rule. When you use the Send Message to All Users link on the Settings page. It is recommended that all users have an associated email address.
User Profile	The user profile, or set of attributes (login group and quota), user roles, permissions, and default user preferences that can be applied to users. By default, new users are provisioned with the user user profile. The user user profile does not include any permissions or roles.
Quota	Maximum amount of server space in megabytes (M) that the user is permitted to use for creating runs. If this limit is exceeded, the user cannot submit new runs (or re-runs). To indicate an unlimited amount of storage space, leave this field blank. If you enter 0, the user cannot create any runs even if the user has appropriate permissions.
Login Group	Name of the login group to which the user belongs. Appears only if you are a superuser. By default, new users belong to the Users login group
Password (Local authentication only)	Password for the user account (up to 64 characters). The password does not need to be unique. Note that users can also modify their own passwords. Follow any recommendations by your organization related to creating secure (hard-to-guess) passwords. You must create passwords according to the password restrictions set by your site administrator. Does not apply if LDAP authentication is used.
Confirm Password (Local authentication only)	Re-enter the password for the user account to confirm it. Does not apply if LDAP authentication is used.
Superuser	If selected, the user can perform any activities. This check box is available only if you are logged in as a superuser. If you are not a superuser, the label Superuser appears (without a check box) for any previously created superuser.
Password never expires	If selected, the user's password never expires. Note: If a user's password has expired, a message at the top of the Edit User page tells you this when you edit the user. Does not apply if LDAP or SSO authentication is used.
User must change password at next login	If selected, the user is required to change the password when next logging in. This option is cleared automatically once the user has changed the password. Does not apply if LDAP or SSO authentication is used.
Account locked	If selected, the user cannot log in until you clear the check box. This check box is selected automatically for a user who tries to log in with an incorrect password more than the number of times allowed by the site option, Number of Attempts Allowed.
Account disabled	If selected, the user account is disabled and the user cannot log in. Note: When a user's password has expired, the user's account becomes disabled. To allow the user to log in again, you must both assign a new password to the user and re-enable the user's account.