SaaS License Management is the part of Software Asset Management that tracks cloud application subscriptions, shows who actually uses them and reclaims access that sits idle. Setup has three stages: request and install the plugin, connect each SaaS or SSO application through an integration profile, then review the reclamation rule the integration creates.
What SaaS License Management covers
SaaS applications are usually bought per user, and they come in two shapes. Hybrid SaaS pairs a local install with a cloud subscription, which suits organizations that need offline access or that have compliance rules requiring local installs. Adobe Cloud and Microsoft 365 are the two hybrid integrations supported. For the Microsoft side of licensing, see the Microsoft license rules guide. Direct SaaS runs entirely in the cloud and is reached through a browser or an app, with nothing installed on the device.
Three approaches bring a direct SaaS app under management. Choose one per application, based on how deep the integration must go, whether the vendor exposes an API, and whether single sign-on sits in front of the app.
| Approach | Best suited to | How unused access is removed |
|---|---|---|
| Direct Integration | Vendors with a built-in integration that need detailed usage and per-user assignments | Automated where the vendor offers a removal call; otherwise candidates are listed for manual removal |
| SaaS License Connections | Applications without a built-in integration that expose API endpoints, built with a low-code framework | Depends on the API and on removal logic built in Workflow Studio |
| SSO Integration | Applications reached through Okta or Microsoft Entra ID | Candidates come from login activity; whether removal is automated depends on the application’s integration and configuration |
Installing the plugin and preparing the instance
The Software Asset Management Professional plugin (com.snc.samp) must be active first. The SaaS capability ships as its own plugin, sn_sam_saas_int, which an admin requests from the ServiceNow Store. The request form asks for the instance name and a reason. Use Validate Instance to confirm the name before submitting. An approved request sends an email with install steps. For the wider rollout sequence, see the Software Asset Management Professional implementation roadmap.
After approval, open All > Admin Center > Application Manager and select Software Asset Management – SaaS License Management. Choose Install optional features, review the feature lists, and install now or schedule the install for later. Skipping optional features installs the base system features. The install adds the sam_integrator role, which inherits sam_user and can create and manage SaaS integration profiles. It also adds the tables that hold usage summaries, product definitions, SSO data and unrecognized identifiers. Demo data is included.
In the Zurich release, upgrading the SaaS plugin to version 16.0.6 or later requires the Software Asset Workspace app (sn_sam_workspace) at version 9.0.4. Confirm that version first.
Connecting a SaaS application through an integration profile
A SaaS integration profile pulls the vendor’s user list and flags people who have not used the application recently. Creating a profile also builds a software model and a reclamation rule. Ready-made integrations cover a wide range of products, including Asana, Box, Dropbox, Google Workspace, GitHub, Jira Software, Microsoft 365, Salesforce CRM, Slack and Zoom. For an application outside that list, create a custom integration profile.
Before reclaiming anything, review the reclamation rule, since its defaults may not match your policy. Then create a software entitlement so that purchased licenses and their cost are tracked against the usage data.
The SaaS playbook guides the same work in phases, with lanes of tasks that can be saved and resumed.
Custom integrations. SaaS License Connections uses Integration Hub with Flow Designer and Workflow Studio to call a provider’s API endpoints. You need an Integration Hub edition at Starter, Standard, Professional or Enterprise level. Build on a non-production instance, where installing Integration Hub plugins carries no charge, then move the work to production with an update set. Subscription-based models use the User Subscription license metric, and consumption-based models use SaaS Consumption. Check for an existing Integration Hub spoke first, because its data stream actions can be reused.
Reviewing reclamation rules before removing access
A reclamation rule sets the minimum period in which a subscription must show use. A user with no activity inside that period is added to the reclamation candidate list. For direct integrations, the qualifying activities differ by application, and one listed activity is enough to keep a user off the list. For SSO applications, the rule checks logins.
The last activity threshold defaults to 60 days for direct integrations and 30 days for SSO applications. Selecting Notify user emails the person that the account will be reclaimed unless they ask to keep it. If they do, the manager approves or rejects the removal. The days-before-reclamation field appears once Notify user is selected. Review the rule as a sam_admin, and check that users will not lose access to their files before an account is reclaimed.
The effect of automatic reclamation differs by application.
| Application | What happens after automatic reclamation |
|---|---|
| Box | The account is deleted, and files move to a folder in the admin account that authorized the integration |
| Google Workspace | Drive files move to an admin folder and email is deleted, so migrate mail first with the Google data migration service |
| Slack Enterprise | The user is deactivated and removed from channels; messages and files are kept |
| Zoom | Pro users move to Basic; Basic users lose their license and cloud recordings are deleted |
Some applications cannot be reclaimed automatically, including Adobe Cloud, Docusign at organization level, monday, SAP Ariba and SurveyMonkey. For those, change the license in the application’s own admin portal. Group-based access also needs care, so check a group’s membership before removing someone from it.
Reading the SaaS Overview dashboard
Open SaaS License > Overview and filter by software model or publisher. Office 365 and Adobe Cloud have their own view under SaaS License > Office 365 & Adobe Cloud. The dashboard also appears in the Software Asset Workspace, where the navigation path differs. For a broader look at subscription reporting, see the subscription management dashboard guide.
| Report | What it shows |
|---|---|
| Current Subscription Spend | Total cost of active subscription entitlements |
| Percentage of Unused Subscriptions | Stale rights divided by all assigned rights |
| SaaS Potential Savings | Cost that reclaiming unused subscriptions could save |
| Snapshot of Last Meaningful Activity | Users grouped by activity in the last 30, 30 to 60, 60 to 90 and 90 to 120 days |
The activity snapshot helps you judge where a reclamation threshold should sit. Two reports offer a Breakdown filter: All Subscriptions includes SSO, while Subscriptions Excluding SSO shows SaaS profiles alone.
Keeping subscription identifiers and exclusions accurate
A subscription identifier names a SaaS or SSO application and links it to a discovery map and software model. Provider changes to product name, edition, version, platform or language arrive through content updates twice a week. Models the platform generated update automatically. Customized models need a manual step: a dot on the model signals a discrepancy, and the suggestions dialog compares current and suggested values. Accept applies a suggestion, Reject keeps the existing identifier, and Update saves. The role needed is sam_integrator or admin.
An identifier with no software model is marked unrecognized. Under SaaS License > Unrecognized Subscription Identifiers, associate a model and select Update, and the related subscriptions take on that model. An admin can also choose whether an identifier is sent to the content team, if the organization has opted into the content service.
Exclusion rules keep low-value or high-volume subscriptions out of cost calculations. An identifier-based exclusion applies to one profile type. A user-based exclusion takes a user principal name and applies across all SaaS integration profiles. Both are created from the integration profile and need the sam_admin role. For the wider reconciliation picture, see the publisher license reconciliation guide.
To list subscriptions, go to All > SaaS License > All User Subscriptions. SSO rows have no subscription profile, and the assigned date stays empty when access comes through a group.
Finding browser-accessed SaaS apps with the detection report
The SaaS detection report lists applications people reach through a browser, paid or free, as collected by the Agent Client Collector for Visibility Content (ACC-VC). It needs the latest version of the SaaS License Management application and ACC-VC 1.9.0 or later. Open it from Software Asset Workspace > License usage > Reports.
Each row shows the product, publisher, whether ACC-VC monitors it, and a managed status. A product is managed when a software model exists for it. The row also gives its URLs, total users, last access time and total time accessed. The URL values are read-only in the report.
Frequently asked questions
Does SaaS License Management need the Software Asset Management Professional plugin first?
Yes. The Software Asset Management Professional plugin (com.snc.samp) must be active before the SaaS plugin is requested.
What is the difference between a direct integration and an SSO integration?
A direct integration reads usage for each user from the vendor and can remove access automatically where the vendor offers a removal call. An SSO integration reads sign-in activity from a provider such as Okta or Microsoft Entra ID, so it can flag stale users across many applications.
How long must a user be inactive before becoming a reclamation candidate?
The default threshold is 60 days for direct integrations and 30 days for SSO applications. You can change it on the reclamation rule.
What happens to a user’s files when the account is reclaimed?
It depends on the application. For Box, files move to a folder in the admin account that authorized the integration. For Google Workspace, Drive files move to an admin folder and email is deleted, so migrate mail first.
Can I keep certain subscriptions out of license cost calculations?
Yes. Identifier-based exclusions apply to one profile type, and user-based exclusions apply to named users across all SaaS integration profiles.
Can a user’s access granted through a group be reclaimed automatically?
It depends on the application. For Microsoft 365, reclaiming a subscription that comes through group membership also removes the user from the group, so review the group’s membership before removing anyone from it.