Ways to administer users

How you administer users depends on your installation type and authentication method:

• Oracle-hosted installations with single sign-on—Create users in a cloud identity service console, such as Oracle Identity Cloud Service (IDCS) or Oracle Health Sciences Identity and Access Management Service (IAMS). New users are provisioned with the default user profile specified as the Default User Profile site option. The users login group, roles and permissions can be further modified on the Oracle Empirica Signal Users page.

  For more information, see the appropriate documentation for your cloud identity management service, either Managing Oracle Empirica Signal Cloud Users with Oracle Health IAMS or Managing Oracle Empirica Signal Cloud Users with Oracle IDCS.

• Self-hosted installations with single sign-on—Create users in Oracle Access Manager or another single sign-on application, and provision users in the Oracle Empirica Signal Users page.
• Self-hosted installations with LDAP—Import user data from an LDAP directory, and provision users in the Oracle Empirica Signal Users page. For more information, see Configure Oracle Empirica Signal for use with LDAP.
• Self-hosted installations without external authentication—Create and provision users in the Empirica Signal Users page.

You provide each user with a user name and password for the Oracle Empirica Signal application.

Note:

For Oracle-hosted installations, you provide Oracle Empirica Signal credentials only for superusers. Superusers log into the application directly.

In addition, you provision users with:

• Permissions—Rights to perform specific tasks in Oracle Empirica Signal. For example, you can enable a user to create data mining runs, and prevent the user from creating report definitions. For a list of permissions, see User permissions.
• User roles—Sets of permissions associated with a user's role. For example, you might create a user role that includes the permissions to create data mining runs and view data mining run results. You can assign one or more user roles to a user. Oracle Empirica Signal includes pre-defined user roles, and you can create custom user roles.
• Login group—Group to which a user belongs. When a user publishes an object (for example, a query or report), the object can be used by other users in the same login group. Each login group can have a customized Home page, with links to customer-specific information.

  Note:

  Users with the Administer Users permission can use both published and unpublished objects created by users in their login group.
• Work teams—Subsets of users in a login group. A user can be in multiple work teams for the same login group. Work teams are used only in the context of the topics feature and are intended to structure the level of access that different users have to topics.
• User profiles—Sets of attributes (login group and quota), user roles, permissions, and default user preferences that can be applied to users as a convenience in setting up users. If you do not use a user profile, you must set the attributes, user roles, and permissions for users individually, and individual users must set their own preferences.