Control SaaS Spend via recycling under-utilized apps
For most any application in your portfolio, there are likely employees with licenses who don't actually need or use them. The challenge of managing and tracking the 'right' number of licenses for each application in your portfolio can be a daunting, if not impossible task. The result? Purchasing additional licenses with each new employee and (hopefully) re-allocating the licenses made available through ebb-and-flow of employee attrition.
Why use Productiv for rightsizing licenses
Org chart and contract data provide context to the user activity insights (engagement or logins) in Productiv to understand: who is using which application licenses to do what.
With the combination of org chart, contract and activity data Productiv can provide 'right-sized' recommendations for reclaiming unused licenses (deprovision) or even 'down-grading' licenses to a more appropriate tier of capabilities.
How to use Productiv for rightsizing licenses
- Identify an application of interest
- Search for application by name (Search box)
- Sort or filter the App list by low Active vs. Provisioned licenses
- NOTE: Rule-out core, or 'birthright,' applications that all employees should always have
- Review the Recommendations
- NOTE: By default the 'rightsized' recommendations will be displayed
- Interpret the license tier recommendations by user type:
- Ignored users =
- users or accounts on the exemption list
- users with licenses provisioned in last 60 days
- Inactive users = users not active (logged in) in past 60 days
- Used less features = users partially utilizing the license provisioned
-
- Efficient users = users fully utilizing the license provisioned
-
- Ignored users =
3. Take action with automated workflows
-
- Create provisioning workflow to automatically downgrade or deprovision licenses:
-
- Downgrade = reclaim higher-tier license and replace with lower-tier license
- Deprovision = reclaim license
-
- Create provisioning workflow to automatically downgrade or deprovision licenses:
Comments
0 comments
Article is closed for comments.