) for the user, and then click Edit. You can edit only users in the same login group as you.Note: This procedure does not apply for Oracle-hosted installations unless you are a superuser renaming a local user. You rename single sign-on users in the Oracle Health Sciences Identity and Access Management Services console.
Before you begin, if you work in a self-hosted environment with single sign-on, rename the user in Oracle Access Manager (OAM) or your single sign-on application. The user name in the single sign-on application must always match the user name in Empirica Signal.
When you change a user name:
The original user name cannot be used to log into the Empirica Signal application.
The new user name appears throughout the application, including historical activities in the User Activity Audit Trail.
It is possible to create another user with the same, original user name after a rename.
The application converts user names to lowercase automatically upon creation and, thus, does not allow duplicate user names that differ only in case. For example, if you create user jkelley, and then attempt to create user JKelley, an error occurs.
1. Click Settings.
The Settings page appears.
2. In the Manage Users section, click Edit Users.
The Users page appears.
3. Click the row menu () for the user, and then click Edit. You can edit only users in the same login group as you.
The Edit User page appears.
4. Click Rename User.
The Rename User page appears.
5. In the Username field, type the new user name for the user.
The name must be unique within the application, and can be up to 100 characters long. If you are implementing single sign-on, type the single sign-on user name.
6. Click Save.
The Edit User page appears with the new user name displayed at the top.
If the affected user is logged into the application, the user can continue working. However, the user must use the new user name for future logins.