Superusers can perform any activities in the Oracle Empirica Signal application, with the following exception:

Superusers must also have the Administer User permission to arrange the columns of a table and define that layout as the default for a login group.

Superusers can act on objects (for example, data mining runs) created by users in any login group. In contrast, users with the Administer Users permission who are not superusers can act only on objects created by users in their login groups.

Only a superuser can:

• Publish an object to multiple login groups.
• Create, edit, or delete user roles.
• Create or delete login groups.
• Restart the listener process.
• Set any site options.
• View the server status.
• View free space.
• Create a report definition using XML.
• Create or edit built-in report definitions.
• Permanently delete a topic workflow configuration.
• Create a run definition file.
• Create a report definition file.
• Change default runs for users.
• View data source tables for runs.
• Delete any runs.
• Manage run storage.
• View the batch report queue.
• Delete a data configuration that has runs, case series, saved lists, report definitions, or report outputs associated with it.
• Add saved lists in bulk mode.
• Assign, edit, or publish in multi-enterprise support (MES).

Superuser accounts in Oracle Empirica are intended for global system management and user administration activities, and should not typically be used for routine business tasks. If the same individual in your organization performs both types of activities, you might want to consider assigning that user separate accounts so that user signs in as a superuser only when needed.

When customers use superuser accounts exclusively for system and user management, Oracle does not require separate Oracle Empirica application licensing for these accounts.

However, if a superuser is assigned other roles and privileges, licensing for Oracle Empirica Signal and Oracle Empirica Topics usage is required.