Role

Each role assigns a specific set of permissions relating to the modules that can be accessed and the tasks that can be performed in each AppViewX module. The roles can be assigned only to a user group. The user groups that are assigned with a role will automatically inherit all the associated permissions. User groups can be assigned with more than a role.

The Roles management of Inventory comprises some of the Out of the Box (OOB) roles available for ADC. The OOB roles can be cloned, enabled, and disabled. It can not be updated or deleted. Administrators can also create custom roles. Custom roles can be updated, deleted, enabled, and disabled. Users can either use OOB roles (if match their needs) or custom roles to map to user groups. The available roles are:

  • Application Manager ADC: The application manager will have complete/partial (complete access will not be given to Shared devices) insight on all the application-related devices. The application manager gets “write” access to all the objects of application objects.

  • Auditor ADC: Auditor access is predominantly for archived logs and the backed-up data along with the current reports and log data which would be used for all kinds of activity tracing.

  • DevOps ADC: The user can automate, execute workflows, perform plugin management and upgrade.

  • Executive Director ADC: Executive access is more towards business-level operational smoothness. The success rate of the changes and the monitoring data for the critical devices in report form ensure adequate details to have respective vendors communicate more data-oriented. This role would also help in understanding failure patterns.

  • Network Manager: Access to complete infrastructure as the responsibility of access provisioning to users and the limited device access provisioning is also handled by this user only. It would require almost admin level of access on the infrastructure, would only not include core system-level access.

  • Traffic Manager: The traffic manager can manipulate the state and status of any object/device to which he has been given access, there are possibilities that users may not have access to all the objects in the device as most devices are based on a shared network infrastructure basis.

In the Roles page, the following actions can be performed:

  • Create a Custom Role: Create a custom role. Note that to assign functions at a more granular level, click the expand icon beside a function checkbox and then select individual sub-options within that function. In the image below, for example, you can select ADC, which automatically assigns all six sub-options and the sub-sub-options within them, or you can expand the ADC function and select only the sub-options or sub-sub-options you want to assign.

  • Modify a Role: Modify a role in AppViewX.
    Note: The Out of the box role functions can not be edited. Only custom roles functions can be edited.
  • Delete a Role: To delete a role from AppViewX.
    Note: You can not delete a role that has active users in it. Also Out of the box (OOB) roles cannot be deleted. Only custom roles can be deleted.

  • Clone a role: The Clone a role option allows you to create an exact copy of an existing role with a different name. The user can modify the permissions and tasks that can be performed while cloning a role.

  • Enable a Role: Enable a role in AppViewX.

  • Disable a Role: Disable a role in AppViewX. Note that You cannot disable a role that has active users in it and The users associated with a disabled role through a user group will not be allowed to log in to AppViewX.

  • Role Mapping to User groups: To map a role to user groups.

For detailed instructions to perform above-mentioned actions, see Platform Userguide.