2.1 What is a View?

The View incorporates both a visualization, such as a scatterplot or bar chart, and a table of supporting data to help you analyze the following types of identity governance activities:

  • Provisioning of access rights, such as requests to add a role.

  • Process activity based on workflows from Identity Manager that are associated with the specified request activities.

    For example, employee Emma Belafonte logs in to Identity Manager where she requests access to the SAP application.

  • Activities associated with the assignment or removal of an access right that occur outside of an Identity Manager workflow process.

    For example, someone assigned Emma the access right within the SAP application or in Active Directory.

  • Activities related to access reviews that occur in Identity Governance.

Each View can provide a unique set of data, depending on its configuration. You not only specify the type of activities you want to see but also specify the time frame when the activities occurred. To include View content in presentations or reports, you can export the data as a PDF or a CSV file. However, the exported file will not include the visualization.

The example for using a View explores how a resource or application owner might resolve problems with the process for granting access to the resource or application.

2.1.1 Example for Using a View

Avanti Rana, who owns the SalesForce application, has received complaints from sales managers that requests for access take weeks to fulfill and require multiple calls for action. She knows that the workflow for granting access to SalesForce roles requires a quorum of three out of four approvers. The approval list includes the employee’s manager, Yuen Lin-wei in Risk Management, Arden Herman in Sales Management, and Avanti as the resource owner. Her company has been using this process for about 12 months. Normally, Avanti prefers to wait for two of the others to approve the request before she responds, thus giving more control to the managers who know which users should have access to SalesForce.

To identify the root of the problem, Avanti creates a View that contains all requests for SalesForce that occurred in the last six months. In the scatterplot, she observes several data points that represent incomplete requests with no activity in the last week or more. As she selects each of the incomplete data points, she realizes that these requests are awaiting approval by either Arden or Yuen. Next, Avanti looks at the data points for requests that already have been approved. In the details for these activities, she sees that Yuen and Arden took as long as two weeks to respond to the requests. She wonders whether one or both of them changed positions in the company or left the company. To verify their current status, she selects Arden’s name in the Summary details so she can see Arden’s User Profile. Then she does the same for Yuen. Neither has changed their job status; thus, at least one of them should be reviewing and approving the access requests in a more timely manner.

She exports the data to a CSV file so she can share these results with her management and the two approvers. She also creates a screen shot of the scatterplot to show the number of pending requests that await a response from Yuen or Arden. With this data in hand, she can formulate a plan for addressing the complaints about the approval process.