ServiceNow Named User vs Unrestricted User Licensing Explained

Why the Licensing Model Choice Matters More Than You Think

ServiceNow licences are not a commodity. The model you negotiate — named user or unrestricted user — determines how your entitlements are measured, how true-ups are calculated, and where your compliance risk sits. Organisations that accept the default model offered by ServiceNow's sales team frequently discover that the structure works against them at renewal or audit time.

Over 20% of enterprises have faced a formal ServiceNow licence audit in the last three years. The majority of those engagements were triggered by usage that had grown beyond contracted entitlements under a model the customer did not fully understand when they signed. Before committing to either licensing model, it is essential to understand precisely what each measures, how each is enforced, and what protections you can negotiate into the contract.

ServiceNow's Three Core User Types

Regardless of which licensing model you use, ServiceNow defines user access through three functional categories. Understanding these is a prerequisite for making sense of either licence structure.

Fulfillers

Fulfillers are the fully licensed users in the ServiceNow environment. They have complete access to create, edit, delete, and manage records within the applications they are licensed for. Typical fulfillers include IT service desk agents, ITSM administrators, developers, HR service delivery agents, and anyone who works directly within ServiceNow workflows as a practitioner. Fulfillers are the most expensive user category and the primary cost driver in any ServiceNow contract. At enterprise negotiated rates, fulfiller licences typically run between £55 and £90 per user per month depending on module, edition, and deal volume.

Requesters

Requesters — also referred to as end users or consumers — submit and track their own service requests or incidents. They access ServiceNow through self-service portals and knowledge bases but have no administrative or operational capabilities within the platform. Requesters do not, in most contract structures, require a paid licence. They are effectively free users who consume portal services without counting against your licence pool. This distinction is significant: an organisation with 10,000 employees may have only 500 fulfillers, with the remaining 9,500 interacting with ServiceNow only as requesters.

Business Stakeholders and Approvers

The intermediate category — variously called business stakeholders, approvers, or limited users — sits between fulfillers and requesters. These users can approve or reject requests, access detailed reports and dashboards, and perform limited management functions, but they cannot create or modify operational records. Business stakeholder licences are paid seats available in nearly all ServiceNow applications. They represent a more cost-effective option than full fulfiller licences for users who primarily need approval and visibility capabilities without operational access.

Named User Licensing: How It Works

Named user licensing — also described as role-based licensing — assigns licences to specific individuals based on the access rights and functional roles they require within ServiceNow. Under this model, you do not pay for every active user in the system. You pay specifically for users assigned to roles that trigger a licence obligation — typically fulfiller and business stakeholder roles.

What Named User Licensing Measures

In a named user model, the licence count is determined by the number of users who have been assigned specific roles within the ServiceNow platform. A user who has no assigned role — or who only has a requester role — does not count against the licence total. This means the licence count is directly tied to role assignments rather than total platform activity.

The compliance obligation under named user licensing is clear: if the number of users with fulfiller or business stakeholder roles exceeds the contracted quantity, you are in breach. Managing compliance means managing role assignments. Enterprises with robust governance frameworks find named user licensing straightforward to manage because role assignment is controlled through change management processes.

Advantages of Named User Licensing

The primary advantage of named user licensing is precision. You pay only for the access that has been formally granted and documented. If your fulfillers are a defined, stable group — as is typically the case in organisations with structured ITSM practices — named user licensing is the most cost-efficient model. For a 500-seat ITSM deployment in a 5,000-employee organisation, named user licensing means you pay for 500 fulfillers regardless of how many employees interact with the platform as requesters.

Named user licensing also gives you a clear, auditable record of licence consumption. Every licence has a named individual attached. Audit exposure is limited to the delta between contracted seats and assigned roles — a gap that is easy to monitor and manage with basic ServiceNow administration.

Risks of Named User Licensing

The compliance risk in named user licensing arises from uncontrolled role expansion. When additional roles are assigned to users without a corresponding licensing review — a common occurrence in large organisations where ServiceNow access is provisioned through IT service requests — the licensed seat count creeps beyond contracted quantities without anyone noticing until audit or renewal. Role proliferation is the single most common source of compliance exposure in named user environments.

Unrestricted User Licensing: How It Works

Unrestricted user licensing replaces the role-based model with a simpler count: any active user in the ServiceNow sys_user table counts against your licence pool, regardless of what roles they have been assigned or what access they actually use. You purchase a total active user count, and any active user in the system consumes one unit of that entitlement.

What Unrestricted User Licensing Measures

Under an unrestricted user model, licence consumption is determined entirely by the number of active users in the system — not by roles, not by module access, not by actual usage frequency. A user who was provisioned an account three years ago and has not logged in since remains an active user and counts against your entitlement if their account is still enabled. This model removes the granularity of role-based measurement in exchange for administrative simplicity.

The unrestricted user model is sometimes presented as a benefit by ServiceNow sales teams because it simplifies administration: no role mapping, no per-module licence tracking, no fulfiller-versus-requester segmentation. What is less prominently discussed is that this simplicity comes at a cost premium, and the true-up mechanics create very different compliance dynamics.

The True-Up Trap: Peak Usage, Not Average

This is the most important point about unrestricted user licensing: ServiceNow true-ups are based on peak usage, not average usage. The true-up is calculated against the highest active user count recorded at any point during the measurement period — not the average count across the year, not the count at renewal date.

The practical implication is significant. If your organisation onboards 200 temporary contractors for a major project in Q2, activating their ServiceNow accounts for six months before deactivating them, those 200 users contribute to your peak count for true-up purposes. Even though they are no longer active at the time of renewal, the peak-based measurement means you owe licences for them. Seasonal hiring, project-based provisioning, and migration activities all create peak spikes that drive true-up obligations under the unrestricted model.

Advantages of Unrestricted User Licensing

For organisations with genuinely broad access requirements — where the majority of employees require some form of ServiceNow access beyond basic requester capabilities — the unrestricted model can eliminate the administrative overhead of maintaining precise role inventories. It can also be advantageous in environments where ServiceNow is being used as a broad enterprise workflow platform rather than a targeted ITSM tool, and where the distinction between fulfillers and other users is genuinely blurred.

Unrestricted licences are sometimes offered at a lower per-seat list price than fulfiller licences, which can make the model appear cost-effective in initial modelling. However, because the seat count includes every active user — not just practitioner users — the total contracted quantity is inevitably higher, and the true-up exposure is broader.

Edition Boundaries and Their Impact on Both Models

The named user versus unrestricted user decision interacts critically with the ServiceNow edition boundary: the divide between Pro, Enterprise, and Enterprise Plus. This is the primary compliance risk that most enterprises fail to manage correctly.

Where the Edition Boundary Sits

ServiceNow's current edition structure runs from standard capabilities through Professional (Pro) to Enterprise and Enterprise Plus. The Pro-to-Enterprise boundary is particularly significant because Enterprise adds capabilities — including advanced AI features, deeper ITSM automation, and expanded CSM capabilities — that are not available in Pro.

The compliance risk arises when users are given access to features that belong to a higher edition than the organisation has contracted. In environments where ServiceNow has been deployed for several years, it is common to find that capabilities introduced in later releases have been enabled by administrators without a corresponding licence review. Users may be consuming Enterprise features on a Pro contract without anyone — including ServiceNow's account team — formally flagging the gap until an audit or renewal review.

How Edition Boundaries Interact with User Licensing

In a named user model, edition boundary compliance is managed at the role level: you must ensure that users assigned fulfillers roles are only accessing features within the contracted edition. In an unrestricted model, the edition boundary is enforced at the platform level — but the true-up exposure extends to every active user, not just those using elevated features. The combination of unrestricted user licensing and accidental Enterprise Plus feature usage creates the most severe compliance exposure profile.

Now Assist AI: A Licensing Layer on Top of Both Models

Now Assist — ServiceNow's generative AI capability suite — adds a further licensing dimension that affects both named user and unrestricted user structures. Now Assist is a premium add-on, not a standard inclusion in Pro or Enterprise base licences. Regardless of which user licensing model your organisation has adopted, Now Assist requires a separate procurement decision and carries its own cost implications.

Now Assist is available as Pro Plus or Enterprise Plus add-ons, layered on top of existing Pro or Enterprise subscriptions. ServiceNow's CFO publicly confirmed a greater than 30% price uplift for Pro Plus compared to base Pro pricing. Independent market data suggests Now Assist adds between £40 and £80 per fulfiller per month for a 500-seat deployment — equivalent to a 25–50% increase in the base platform cost. Organisations evaluating Now Assist must model this cost separately from their core user licensing, under both named user and unrestricted user scenarios.

Which Model Should Your Enterprise Choose?

The right licensing model depends on the structure of your ServiceNow deployment, your user base, and your governance maturity. Neither model is inherently superior — the optimal choice is determined by your specific circumstances.

Choose Named User Licensing If:

• Your fulfillers are a clearly defined, relatively stable group of practitioner users.
• Your organisation has robust access governance and role management processes.
• The majority of your employees interact with ServiceNow only as requesters through a self-service portal.
• You want the lowest possible cost per licensed user and are willing to manage role compliance carefully.
• You want precise, auditable licence consumption data that is easy to verify independently.

Choose Unrestricted User Licensing If:

• ServiceNow is deployed as a broad enterprise platform where many employees perform functional work within the system beyond basic request submission.
• The boundary between fulfillers and other user types is genuinely unclear or frequently shifting.
• Administrative simplicity is a higher priority than cost precision, and the organisation lacks the governance infrastructure to manage role inventories rigorously.
• Your user base is stable and seasonal fluctuations are minimal — limiting peak-based true-up exposure.

Negotiating Protections Regardless of Model

Whether you are on a named user or unrestricted user model, certain contractual protections should be negotiated at the outset. These protections can significantly reduce compliance risk and limit true-up exposure.

True-Up Cap

Negotiate a cap on the true-up obligation — for example, limiting true-up liability to a maximum of 10–15% above contracted quantities before an additional licence must be purchased. This creates a defined compliance buffer rather than leaving unlimited exposure from any overage.

True-Up Measurement Window

Under a peak-based model, negotiate how frequently the peak is measured. A quarterly measurement with a rolling average alternative is more favourable than a daily measurement against the highest single-day count. Even under an unrestricted model, the measurement mechanics are negotiable.

Audit Rights Limitation

ServiceNow's standard terms permit up to two audits per year. Negotiate this down to one, with advance notice requirements and the right to self-certify compliance before a formal audit is initiated. Organisations that have self-certified compliance through their own ITAM processes should receive credit for this work before a vendor-led audit commences.

Grace Periods for Role Removal

Under a named user model, negotiate a grace period — typically 60 to 90 days — to remediate any role count overage identified in a compliance review before a financial obligation is triggered. This gives your teams time to audit and clean role assignments rather than being immediately liable for any excess discovered.

Practical Steps to Assess Your Current Position

Before your next ServiceNow renewal, these steps will establish your baseline position and identify any exposure that needs to be addressed.

Step 1 — Read your contract: Identify whether you are under a named user or unrestricted user model. The licence schedule in your contract will specify the measurement basis. Many organisations do not know which model they are on.

Step 2 — Pull your current active user report: Run a report on active users in the sys_user table. Compare this to your contracted quantity. Under an unrestricted model, this is your current licence consumption figure.

Step 3 — Run a role inventory under a named user model: If you are on a named user model, run a report on all users with fulfiller and business stakeholder roles assigned. Compare this to your contracted seat count by module. Any overage is a compliance gap that needs to be resolved before renewal.

Step 4 — Identify your edition boundary: Confirm which edition of ServiceNow you have contracted (Standard, Pro, Enterprise, or Enterprise Plus). Cross-reference against the features your users are currently accessing. Any feature usage beyond your contracted edition is a compliance risk.

Step 5 — Engage independent advisory support: If you identify gaps, engage an independent ServiceNow adviser before contacting ServiceNow directly. The sequence in which you address compliance exposure — and the framing in which you approach ServiceNow — materially affects the financial outcome. An independent adviser who has managed similar situations can guide the remediation strategy.