AX2573

Grant admin-level permissions

In Security, users can be designated as a system admin, by enabling the Administrator option on the General tab.

System admins have full rights to all features and all data for the system. Although you can configure security settings for admins, such as to define file access or table filters, these settings will be overridden as long as the Administrator check box is enabled for the user. The Effective Permissions section will reflect the user's full access.

Admin-only features

Admins have access to all features and files in the current Axiom Budget Planning and Performance Reporting system. While non-admin users can be granted access to many features and files, some features are only available to admins:

  • The ability to make another user a system admin.
  • The ability to lock non-admin users out of the system, and the ability to log into a locked system.
  • The ability to restore a deleted file.
  • The ability to modify system configuration settings using Save Type 4, or using the System Configuration page in the Axiom Web Client.
  • Access to Scheduler admin features in the Scheduler dialog (such as viewing all job history, managing system jobs and event handlers, managing Scheduler servers, and managing remote data connections).
  • Access to system folders in Axiom Explorer (therefore, any file management for system files that cannot be done using system utilities can only be done by admins).
  • Access to certain underlying file group folders such as the Plan Files folder, Plan File Attachments folder, and the Calc Method Libraries folder.
  • Access to the Developer > Tools menu on the Axiom Designer ribbon (though some of the features on this menu are available elsewhere without the admin restriction).
  • Access to the technical administration features in the Axiom Web Client, such as: Reset Services, Rebuild Table Views, System Logs, and Update License.
  • Ability to set the Execute By field in Scheduler jobs.

Security access for non-admins

If you want a user to access and edit security settings, but you do not want to make the user an admin, there are two options:

  • You can give the user the Administer Security permission. Users with this permission can add, edit, and delete users, roles, and subsystems, and can access security tools such as System Access and Logged in Users.

  • If you are using subsystems, you can assign a user as a subsystem admin. Users with this permission can edit the security settings for users that belong to the subsystem, and can also create and delete users within the subsystem. For more information, see About subsystems.

These users do not have access to the Administrator check box in Security. They cannot make themselves or any other user an admin.