Role-based access overview
The system forms are added to a single deployable application. In deployable applications, access permissions are based on roles. Like groups, roles have permissions to access forms, fields, active links, and so on. Unlike groups, however, roles are defined for an application and are then associated with groups on the server where the application is deployed.
Roles make deployable applications easy to install on multiple servers. You can assign users to groups and then associate the groups with roles. This enables you to install an application on servers that have different groups without redefining the application's object permissions for each server.
The following table lists the roles used to access the deployable applications:
|Type of roles
|Manages alerts in the user alerts list.
|AR Definition Administrator
Allows read access to the AR System metadata forms. The AR Definition Administrator can also modify definitions through configurations.
Configures and manages the archive policies. The Archive Administrator performs the following tasks:
|Email Engine Administrator
|Configures the Incoming and Outgoing mailboxes to work with the mail server and manages email templates.
|Home Page Administrator
|Specifies the default home page for a server and configures the AR System Customizable Home Page.
|Configures and manages system, user, and application licenses.
|Configures and manages the system logs.
|Defines who has access to view a report. Views and manages the reports shared by all users.
Adds and deletes users in the AR System server , manages user permissions and preferences.
The AR System Administrator has all the rights defined for the above roles. To simplify, user access is usually described in terms of group permissions. For the deployable applications that use role permissions, the user access is ultimately determined by the groups that are mapped to the roles. For more information, see Creating and mapping roles.