Managing Roles ACF Permissions

ACF permissions for New users to view Alerts and Logs

.
On the Authorised Functions tab page, go to Platform > Observe and Explore > Alerts > Access (This Option (Access) has been added to define access levels to view alerts for auditing the user action in AppViewX). Provide the access as follows:
  • All - Allows the user to view all alerts for the product line, including other users' actions. Recommended for admins or users needing full visibility
  • Group - Allows the user to view only alerts from their own user group. Used to restrict visibility to group-specific alerts only.
  • Self - Allows the user to view only their own activity alerts for maximum privacy

Roles ACF for Service Accounts

.
Users can manage client service accounts and can access AppViewX using a unique username and password maintained internally or by an external enterprise server. On the Authorised Functions tab page, go to Platform > Identity > Service Accounts. Provide the access as follows:
Role Description
View View existing service accounts in the inventory
Import Import service accounts details as csv.
Regenerate ClientId Regenerate Client Id for an existing service account.
Show Secret Show Client Secret for an existing service account.
Add/Modify Addition or modification of service accounts.
Regenerate Client secret Regenerate Client secret for an existing service account.
Delete Delete existing service account.
Enable / Disable Enable or disable existing service account.
To enforce ownership-based visibility for service accounts, thereby enhancing data isolation and security by restricting service account visibility to only relevant users. On the Authorised Functions tab page, go to Platform > Identity > Service Accounts > Access.
Role Description
All Accounts Allow users to manage all service accounts.
Self Accounts Allow user to manage self-created service accounts.

ACF permissions for existing users to view Alerts and Logs

.
On the Authorised Functions page, go to Platform > Observe and Explore > Alerts > Access (This Option (Access) has been added to define access levels to view alerts for auditing the user action in AppViewX). Provide the access as follows:
  • All - Allows the user to view all alerts for the product line, including other users' actions. Recommended for admins or users needing full visibility
  • Group - Allows the user to view only alerts from their own user group. Used to restrict visibility to group-specific alerts only.
  • Self - Allows the user to view only their own activity alerts for maximum privacy
For migrated user, default groups will be selected.

Configure the ACF permission for request retrigger

Grant selected users or user groups permission to retrigger failed workflow requests from a failed stage.

  • Ensure that you have administrator access to the ACF configuration.
  • Ensure that the target users or user groups already have access to the workflows for which retrigger actions must be allowed.

The request retrigger permission controls whether a user can retrigger a failed workflow request. Users can retrigger only failed requests and only for workflows they are already authorized to access.

This permission is available under the automation-related ACF settings for service requests.

  1. Open the ACF configuration page.
  2. Go to Platform > IDENTITY > Role.
  3. Select the required group.
    Note: To assign the permission to the required users or user groups.
  4. Go to Automation > Service Request > Action.
  5. Select the Retrigger permission.
  6. Save the ACF configuration.
  7. Open a failed workflow request for a workflow that the user can access.
  8. Use the retrigger action on the failed stage.

    If the user has the required permission and workflow access, the retrigger action is allowed.

Only users or user groups with the Retrigger permission can retrigger failed workflow requests, provided they also have access to the respective workflow.

Verify the permission by testing the retrigger action with both authorized and unauthorized users.

Note:

This permission controls access to request retrigger actions. It does not grant access to workflows by itself.