Understanding the app summary view

• Contract data
• Engagement or Provisioning data
• SSO data (Single Sign-on)
• Social login data
• MDM data (Mobile device management)
• Network data (CASB)

Contract data

• User licenses: Total number of user licenses across all active contracts.
  • Note that this does not include non-user line items, like implementation consulting or consumables.
• Total contract value: Sum of contracts spend for the full term of all active contracts as of the selected date.
• Upcoming end date: Next upcoming contract end date from the selected time period.

• Gain visibility: Understand the current state of your contractual obligations at a glance.
• Ensure completeness: A blank card indicates missing contract information. Ensure you upload contract data to identify optimization opportunities, track renewals, and make informed decisions.

Engagement or Provisioning connector

• Engagement connectors can pull usage and provisioning data
• Provisioning connectors can only pull provisioning data.
  
  

• Provisioned: Total number of users who have been granted a license to use this application as of the selected date.
• Engaged: Users who have performed at least one engaged user action within the select timeframe (default: Last 30 days).
  • Engaged user actions are specific, trackable user actions within an application, such as creating a Jira issue or attending a Zoom meeting.
  • To view the list of tracked actions for an application, click the “View Engaged user action” button displayed in the tooltip.
• Not Engaged: Users who have not performed any "engaged" user actions within the select timeframe (default: Last 30 days).
  • To view the list of actions for an application, click the “View Engaged user action” button displayed in the tooltip.

• Identify inactive users: Analyze the "Not Engaged Users" metric to identify users who haven't interacted with the application recently.  For underutilized licenses, explore options like downgrading or removing them to reduce costs.
• Enhance data insights: If the app is not currently connected to an available engagement source, the card will prompt you. By connecting your application, you can gain deeper insights into user behavior and optimize usage.

• When viewing a suite of apps (like Office 365), the engagement number includes every person that has engaged with one of the child apps.
• When viewing an app with multiple connected instances, the data shown includes every account that is provisioned on or has engaged with any of the instances.

SSO data

• Has access via SSO: Users with access to the application tile in the connected SSO provider.
  • Note: Having access via the SSO provider does not necessarily mean they have been granted a license.
• Logged in via SSO: Users who have logged in to this app via SSO in the last 30 days.
  • Note:  Log-in activity is not always a reliable measure of app usage. The frequency of log-ins can vary significantly between apps, with some requiring daily log-ins while others may only need a log-in every few weeks.

• Enforce SSO login: If there is no activity, the app may not be integrated with your SSO. Ensure all users access the application through SSO to enhance security and control.
  • If you know that the app is behind SSO but it’s not appearing in Productiv as expected, you can find the SSO data and match it to the right application by following instructions on this page.

Google Social Login

• First authentication via Google Social: Users who have authenticated through Google Social for the first time in the last 30 days. (Google Social only tracks a user’s first authentication with a particular application.)

• Identify security risks: Users who authenticate via Google Social may pose a security risk as they are not using your SSO platform. This serves as a discovery measure to identify users and take necessary action.
• Identify Shadow IT: Discover apps that your users are signing into that may not be approved or managed by IT.

MDM data (Mobile Device Management)

• App installed: Users who have the application installed on their managed laptop or mobile device as of the selected date.

• Identifying interest: For new applications not currently in your portfolio, this metric can be used as a discovery tool to identify potential user interest and demand.
• Enforce security policies: Implement measures to discourage the use of unauthorized applications.

Network data (CASB)

• Unique endpoints: Unique endpoints represents users accessing the application’s website. When user information is unavailable, different devices or IP addresses may be counted separately as unique endpoints.

• Identifying interest: For new applications not currently in your portfolio, this metric can be used as a discovery tool to identify potential user interest and demand.
• Enforce security policies: Implement measures to discourage the use of unauthorized applications.

• This metric provides a general sense of interest in the application, but it doesn't directly measure active usage. It's important to note that this metric may include individuals who are simply browsing the website and have not necessarily engaged with the app itself.