Accept or edit the login groups associated with the Enterprise ID

When your organization requested Oracle to enable multi-enterprise support for your Oracle Empirica Signal Cloud environment, your organization supplied a list of login groups to create and the users who belong to each login group.

Your organization also supplied the mapping between the login groups and the enterprise IDs associated with the multi-enterprise enabled environment.

However, Oracle discourages changing a user’s login group once the user has logged in and potentially created objects.

• If changed, the created objects may yield unexpected results because the objects may contain data that is no longer associated with the enterprise ID of the new login group.
• If an enterprise ID is no longer available, then the Argus Mart Enterprise field will display Unknown.

If you must change the login group assignments, you must be a superuser.

Note:

Each enterprise ID can be associated with only one login group.

1. In the left navigation pane, click the Settings icon ().
2. In the Manage Users section, click Edit Login Groups.
3. Click Edit for a login group you wish to associate with a different enterprise ID.
   The Login Group Settings page appears.
4. If multi-enterprise support is enabled, an Argus Mart Enterprise field appears. Only a superuser can set or change this field. This is a read-only field for non-superusers.
   1. If the field is blank, it means an enterprise ID has not been associated with the login group. You can select an enterprise ID from the drop-down list.
   2. If the login group has already been saved with an enterprise ID, the field is read-only even for superusers. However, a Change link allows superusers to select a different enterprise ID.
5. To change the enterprise ID, click the Change link.
6. Read the warning message and click OK to continue the change.
7. Select a different enterprise ID from the Argus Mart Enterprise drop-down list, and then click Save.

   Note:

   If you modified settings for an existing login group, then users currently logged in who are associated with the login group are not affected by the changes during their current session. The changes take effect the next time they log in.