Portfolio Overview
One screen rolling up adoption, cost, and risk across every application in the estate, showing which decisions to make and how to add cost and ownership data.
Portfolio Overview is a single dashboard that rolls up adoption, cost, and risk data across every application Userlane tracks. It is built for portfolio owners, chief information officers (CIOs), and anyone making decisions across applications. It sits above the per-application HEART views as the executive view in Visibility.
A HEART scorecard shows how one application is performing. Portfolio Overview shows how the entire tracked estate is performing. It answers three questions: where the organization spends money on software nobody uses, where newly discovered applications create risk, and which applications need attention based on their HEART scores.

What the page shows
Portfolio Overview organizes data into three groups, each framed around a decision.
Cost and savings. Shows potential savings from unused licenses. For each application, Userlane compares the number of active users against the number of expected users and multiplies the difference by the estimated license cost per user. The total potential savings appears at the top, and the per-application breakdown is in the table below. This depends on uploaded cost data (see Adding cost and ownership data), because Userlane does not pull license costs automatically.
Risk and compliance. Highlights newly discovered applications that nobody has reviewed yet. App Discovery detects applications in use across the estate, and Portfolio Overview shows how many of those are new or flagged. This is the starting point for finding unauthorized tools or ungoverned AI services.
Value optimization. Groups applications by their HEART performance. Applications with strong scores are labeled as performing well, and those below a threshold are flagged as needing attention. You get a quick read on where to focus improvement effort without opening each application.
Where the data comes from
Three sources feed Portfolio Overview, and each updates on its own schedule.
HEART scores are calculated automatically. They follow the five-dimension model described in HEART and update as the underlying data changes.
Application data comes from App Discovery, which detects the applications in use through browser activity, or from applications added manually as tracked properties in the portal. Both types appear in the Portfolio Overview table.
Cost and ownership data is uploaded manually as a comma-separated values (CSV) file. There is no automatic integration with license management or procurement tools. Without an uploaded CSV file, the cost and savings group has nothing to calculate from, and potential savings are not shown.
Adding cost and ownership data
Cost data reaches Portfolio Overview through a CSV file upload. This is the only way to add license costs, expected user counts, application owners, and renewal dates.
Prepare the CSV file
The file must follow the template structure. Each row represents one application. The key fields are the application name, the expected number of users, the estimated annual license cost per user, the application owner, and the renewal date. The application name must match an application already tracked or discovered in Userlane.
Relevant articles
What Intelligence measuresHEART ScoreAdoptionApp DiscoverySet up the application URLFAQ
Last updated
Was this helpful?

