Roles and permissions
By assigning roles, it is easy to install deployable applications on multiple servers. You can assign users to groups and then associate the groups with roles. This process 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 | Description |
---|---|
Administrator |
|
Application Business Analyst |
|
Alert Administrator | 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. |
Archive Administrator | 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. |
Licensing Administrator | Configures and manages the system, user, and application licenses. |
Logging Administrator | Configures and manages the system logs. |
Reporting Administrator | Defines who has access to view a report. Views and manages the reports shared by all users. |
User Administrator | Adds and deletes users in the AR System server, manages user permissions and preferences. |
The administrator has all the rights defined for the preceding 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.
To understand the goals for these roles and the capabilities provided by BMC Helix Innovation Suite to each role, see .