About ServiceNow Licensing Guide

[SAMfluencer786]

After analysing every ServiceNow licensing reference page and knowledge article available, I've pulled everything together into one place  attached as a reference workbook at the end of this post.

The Three Models Know Which One You're In:

ServiceNow organises all its products into three subscription categories. Most people only know one of them.

1. Account-Level Products

These are licensed at the account level. No user counting. No discovery queries. You buy the entitlement and it's active.

The products here include Assists (the currency behind Now Assist), Creators, and Cloud Storage.

Simple in concept  but watch the Assists model closely as Now Assist adoption scales across your organisation. Consumption can spike faster than contracts anticipate, and unlike user-based models there's no natural ceiling built into headcount.

2. Role-Based Products

This is where most ITSM, CSM, GRC, and SPM/APM spend lives. The platform counts users by querying role assignment tables against the roles mapped to your entitled applications.

There are three distinct role tiers and they are not interchangeable:

Fulfiller (FF) : Your core service desk agents, case managers, and workflow owners. Anyone actively working and resolving records. The platform counts active users who have logged in within the past 365 days, are not flagged as Web Service Access Only, and hold a Fulfiller role mapped to an entitled application. Products in this tier include ITSM, CSM/TSM, FSM, App Engine, and GRC.

Fulfiller + Requester:  Used by collaborative products like SPM/APM (formerly ITBM) and Legal Service Delivery, where both role types are chargeable. The measurement logic is the same as above but extends to both role assignments.

Business Stakeholder (BSH) : This one catches people off guard because it is measured across two separate tables one for role assignment and one for approval activity. A user qualifies as a BSH if they hold an Approver role but hold no Fulfiller role. The moment a BSH user gains a Fulfiller-mapped role, they move out of BSH measurement entirely.

Unrestricted User:  No role restriction at all  every active user on the instance is counted. Products like HRSD, Employee Center Pro, and several others use this model. The practical implication is that tenant-wide active user governance stops being a hygiene task and becomes a direct cost control.

3. Definition / Capacity-Based Products

This is the ITAM practitioner's territory - and where things get genuinely complex.

Rather than counting users, ServiceNow measures discovered units — servers, devices, managed software, nodes, AI systems, robots, portal visits, work orders, and more depending on the product. Each product has one or more Definition IDs, and the count is pulled from the platform's usage analytics engine.

How to verify your count in-instance:

1. Navigate to the usageanalytics_count table
2. Add the DefinitionID field via the column chooser
3. Sort by Most Recent Date descending
4. Filter for the relevant Definition ID
5. If a definition appears inactive, check usageanalytics_count_cfg and then ua_stats_defn

The billable number is the peak count in the most recent accrual period - not an average. A single-day spike from a large discovery run can set your billable count for that period.

Products covered under this model span a wide range of business units  Asset Management (SAM Pro, HAM Pro, EAM), IT Operations Management (multiple ITOM SKUs with separate Definition IDs per SKU), Risk (IRM, BCM, Privacy), Security (Vulnerability Response, Security Posture Control), Workflow Data Fabric (Integration Hub pool, RPA robots, Data Fabric credits), Workplace Service Delivery, Customer Service Management portal visits, Field Service work orders, HR profiles, and more.

Some products span multiple Definition IDs  ITOM in particular has more than twenty active definitions covering different SKU combinations. Knowing which Definition IDs your contract actually covers is non-negotiable before any renewal conversation.

After going through every reference page, I pulled it all into one structured workbook covering all three subscription categories, every product, every Definition ID with its description and measurement schedule, the OOB measurement logic for all role types, and the current documentation links.

It's attached below. Use it as a pre-renewal checklist, a workshop reference, or a starting point for your own governance documentation.

Important Disclaimer: The content in this article and the attached workbook represents my personal findings gathered from publicly available ServiceNow documentation, knowledge articles, and community resources. It is shared in the spirit of peer knowledge exchange and is not an official ServiceNow publication. Licensing terms, measurement logic, and entitlement details can vary by contract, release version, and product configuration. For any official confirmation, please always validate through your ServiceNow Support channel or engage directly with your ServiceNow Account Executive.

Regards,

Abby