Glossary
A buyer side definition with the commercial implications that matter at renewal.
Glossary
The ServiceNow named user definition describes a licence assigned to one identified individual rather than shared across a pool or measured by concurrent logins. A named user licence is counted per person on the platform, so the size of the named population, not peak usage, is what sets the bill at renewal.
Because a named user licence is tied to a specific person, the commercial exposure is the count of named individuals carried on the agreement, whether or not each one logs in. This is where dormant accounts quietly compound. A named user who left the business, changed roles or never adopted the platform still sits in the count until someone removes them, and the vendor has no incentive to prompt that clean up before renewal. Based on benchmark observations, dormant named fulfillers in the range of 10 to 20 percent of the licensed base are common in estates that have grown across several terms.
The buyer side discipline is to reconcile the named population against real activity before the quote anchors the renewal, then license to the cleaned number with a defined resize right for genuine growth. The named user count interacts with the fulfiller boundary, so it is read alongside the ServiceNow fulfiller vs requester split and our ServiceNow licensing advisory reconciliation. The related ServiceNow named user licence page covers the mechanics in depth, and the requester entry covers the users who sit outside the named fulfiller count entirely.
One further point matters at renewal. Because the count is per person, a named user agreement rewards regular housekeeping in a way a concurrent model does not. An estate that removes leavers and role changers each quarter walks into the negotiation licensing only the people who actually use the platform, while an estate that never cleans the list pays for years of accumulated drift. The vendor will not prompt that clean up, so the buyer has to run it as a standing practice rather than a renewal scramble.
Treat the cleaned named population as the baseline the whole renewal is sized against, and the saving compounds across the term.
A named user is a licence assigned to one identified individual rather than shared or measured by concurrent use. The platform counts named users per person, so the named population determines cost.
Because they are counted per person, including individuals who no longer use the platform. Dormant named accounts stay in the billable count until removed, so an uncleaned base inflates the renewal.
Reconcile the named population against real activity, remove dormant accounts before the renewal quote anchors, then license to the cleaned number with a defined resize right for genuine growth.