Manage application access requests

Enabling the Workflow feature for an application allows end users to send requests for access to the application to designated users or roles for approval. Approvers can grant access to the application permanently or for a specified time window. Granting access to the application means the users receive the View, Run, and Automatically Deploy permissions.

Configure a request and approval workflow

As a member of the sysadmin role or a role with the Role Management administrative right, you can configure roles for all other users. Initially, only the members of the sysadmin role have the ability to enable a “request and approval” workflow and can configure the workflow for selected applications, specify the users or roles with authority to approve access requests, and identify the role or roles to which users will be assigned if their request is approved.

At a high level, the steps involved in configuring a workflow are these:

  • Create one or more roles that can enable a “request and approval” workflow.
  • Create one or more roles that can approve access requests for the applications that have a “request and approval” workflow.
  • Select an application and click Workflow to select the role into which requesters who are approved will be placed.
  • Select the user or role with authority to approve requests.

If the Requestor’s Manager is the only approver in the approver list and the user has no manager, the request will be approved. If this is not desirable, verify that your users have a manager (refer to Add CyberArk Cloud Directory Users for more information) or add other users or roles to the approver list.

Create roles for workflow administration

The first few steps in configuring the “request and approval” workflow are optional and involve creating one or more roles for users who are allowed to define a “request and approval” workflow for applications and the roles that can approve access requests. These steps are optional because you can choose to only allow members of the sysadmin role to be the users permitted to configure a workflow and members of the sysadmin role can assign approval authority to individual users without creating any approval roles. In most cases, however, creating roles for different sets of users provides greater flexibility and helps to reduce the number of requests left pending an approval.

If you don’t create any intermediary roles with the appropriate administrative rights to enable a workflow, only members of the sysadmin role will be able to configure any “request and approval” workflow you might want to implement.

In most cases, if you are configuring a request and approval workflow for applications, you should create at least one role for users who are allowed to add, modify, or remove applications and who have permission to change which roles are assigned to a specific applications. If you don’t create a role with the Application Management and Role Management rights, only members of the sysadmin role can configure the “request and approval” workflow for applications.

To configure roles that can enable a workflow

  1. Log in to the Admin Portal.
  2. Click Core Services > Roles.
  3. Click Add Role or select an existing role to display the role details.

    If you are creating a new role, you must provide at least a unique name for the role.

  4. Click Members, then click Add.
  5. Type a search string to search for and select users and groups for this role.
  6. Click Administrative Rights, then click Add.
  7. Select the appropriate rights, then click Add.

    For example, if you are creating a role with permission to enable a workflow for access to applications, select Application Management and Role Management. You can select any additional rights you want included in this role, but you must select at least one of the required administrative rights.

  8. Click Save to save the role.

Create roles for approvers

You can assign approval authority to individual users. However, in most cases, creating “approver” roles for different sets of users provides greater flexibility and helps to reduce the number of requests left pending an approval. If you don’t create any intermediary roles with the appropriate administrative rights to approve access requests, only members of the sysadmin role will be able to approve access requests. You can follow the same steps described in Create roles for workflow administration to create roles for approvers.

Keep in mind that if you are creating a role with permission to approve access requests for applications, you should include the Application Management and Role Management rights. You can select any additional rights you want included in this role.

Configure Workflow

As a member of the sysadmin role or a role with Application Management and Role Management administrative rights, you can configure a request and approval workflow for any application.

Request access to an application

Any user with an account in CyberArk Identity can request access to applications with workflow enabled. No special privileges are required to make requests.

View request details

You can view request status and history in the User Portal, or if you have appropriate administrative rights you can view requests in the Admin Portal. The Requests tab is only available if you made a request or you are a designated approver for a request.

  • User Portal

  • Admin Portal

Regardless of the entry point for viewing the Requests tab, the list of requests includes the following information:

  • Description provides a brief summary of the request indicating the type of access or application requested.
  • Status displays the current status of the request as Pending, Approved, Rejected, or Failed.

    You can review the request details to see the reason the request failed. For example, a request might fail if the email address for the approver or requester is invalid. A failed request might also indicate that the time allowed for taking the requested action has expired. For example, assume the request was for permission to use the root account to log on to a resource and the request was approved with a duration of 60 minutes. If the requester did not log on within 60 minutes of the request approval, the request status will display Failed.

  • Posted displays the date and time of the most recent activity for each request.

  • Approver displays the user or role designated for approving access requests if the approval is pending or the specific user who approved or rejected the request if the request has been resolved.

  • Requester displays the user who submitted the request.

  • Latest Log Entry displays the most recent information recorded for the request.

Respond to application access requests

There are no special privileges required to respond to requests. Anyone with access to CyberArk Identity can be designated as an approver.

If you are a designated approver for requests, you receive an email notification for requests. You can click the View Request link in the email to view the request details and the options to approve or reject the request.

  • Click Approve to approve the request and grant access to the application.

    If you click OK to continue with the approval, the request details are updated with the date and time the request was resolved and the approved status.

  • Click Reject to reject the request and type the reason you are rejecting the request.

    If you click OK to continue with the rejection, the request details are updated with the reason the request was rejected, the date and time the request was resolved, and the rejected status.

After you respond to the request, the Requests tab is also updated with the latest activity and email is sent to the requester as notification of your response to the request.