Named User License

A named user license ties the right to use software to a particular person. Each user who needs access must have their own license, whether they use the software every day or once a month. The license follows the person rather than a device, so a named user can usually access the software from a laptop, phone or browser. Most SaaS applications are sold this way, as do many enterprise software products.

Named user licensing is simple to understand and administer, and vendors favor it because it scales with the number of people using their products. For IT financial management, it means software costs rise and fall with headcount and access decisions. Managing named user licenses well, by assigning them carefully and reclaiming them promptly, has a direct effect on software spending.

Definition of Named User License

A named user license is a license model in which the right to use software is granted to an identified individual. The license is assigned to that person's account and cannot be used by others, even if the named user is not using the software at the time.

It is one of several software licensing models, alongside device-based, concurrent, processor-based and consumption-based licensing.

How Named User Licensing Works

The organization buys a number of named user licenses and assigns each one to a person, usually through an administration console or identity system. Only that person can sign in and use the software under the license.

Many vendors allow licenses to be reassigned when people leave or change roles, though some limit how often this can happen. Some products offer different named user types, such as full users and limited or read-only users, priced differently.

Sharing a named user account among several people, a practice sometimes used to save money, usually violates the license terms and can lead to findings in a software audit.

Named User vs Other Models

Device-based licenses are tied to a machine rather than a person, which suits shared workstations but not people who use several devices. Named user licenses suit people who work across laptops, tablets and phones.

Concurrent licenses limit how many people can use the software at the same time, allowing a pool of licenses to be shared. Named user licenses do not allow this sharing, so they can be more expensive for software used occasionally by many people.

Consumption-based models charge for actual use rather than access, which can cost less for light users and more for heavy ones.

Importance of Named User Licenses in IT Financial Management

Named user licensing is the dominant model for SaaS, so it governs a large and growing share of software spending.

Its costs depend directly on how many people have access. Every new employee, contractor or team that adopts a tool adds licenses, while licenses are removed only when someone takes action to reclaim them.

Small decisions about who receives a license, repeated across thousands of employees, add up to significant spending. A difference of a few hundred dollars per person becomes millions across a large workforce.

Costs Linked to Headcount

Because each user needs a license, named user costs grow with the workforce and with the number of people given access to each tool. This makes them suited to driver-based planning using headcount as the driver.

It also means that costs do not fall automatically when usage drops. A person who has stopped using the software still holds a license until someone removes it.

Organizations that do not reclaim licenses from inactive users and departed employees build up shelfware.

Choosing the Right License Types

Many products offer several named user tiers. Assigning premium licenses to people who need only basic features increases costs without adding value.

Matching license types to roles, for example giving read-only licenses to people who only view reports, can reduce costs significantly in products with large price differences between tiers.

Reviewing tier assignments before each renewal helps keep spending aligned with actual needs. People's roles change over time, and a license type that suited someone when they joined may no longer fit what they do.