Glossary
A buyer side definition with the commercial implications that matter at renewal.
Glossary
The ServiceNow requester definition describes a user who raises requests, reads knowledge and tracks their own tickets, but does not work or fulfil them. A requester consumes the platform rather than operating it, which is why requester access is typically bundled or very low cost while the licensed fulfiller carries the real price.
The line between requester and fulfiller is where a large share of ServiceNow cost is decided. A requester can submit, view and comment. The moment a user picks up work, resolves a ticket, edits a record as an agent or acts inside a fulfiller workflow, the vendor expects a paid fulfiller licence. Account teams read this boundary generously in their favour, so the buyer side job is to count who genuinely only requests and keep them out of the fulfiller line. Based on benchmark observations, fulfiller licences carry the cost while requester volume is effectively free, so misclassifying even a few hundred light users as fulfillers is a material and avoidable overpayment.
Two cautions apply. Approvers are a frequent grey area: an approver who only approves usually does not need a fulfiller licence, but vendors sometimes argue otherwise, so confirm it in writing. And under the 2026 Foundation, Advanced and Prime model the requester boundary still governs the headcount you license, which is why our work on ServiceNow fulfiller vs requester economics treats it as the first number to fix in any renewal. Our ServiceNow licensing advisory reconciles entitlement against real usage so the classification holds, and the ServiceNow requester licence and named user entries cover the adjacent definitions.
In practice the requester count is rarely the problem. The cost sits in the users sitting one step the wrong side of the line, the part time approvers and occasional updaters a vendor would prefer to license as fulfillers. Pin the definition down in the agreement, count the genuine fulfillers from your own activity data, and the requester population becomes the inexpensive volume it should be rather than a quiet source of overpayment at every renewal.
A requester is a user who raises and tracks their own requests and reads knowledge but does not fulfil work. Requester access is normally bundled or very low cost, in contrast to the paid fulfiller licence carried by users who action tickets.
Generally no. Pure requesters consume the platform rather than operating it, so they sit outside the fulfiller count. The cost risk is misclassifying light users as fulfillers, which inflates the licensed headcount unnecessarily.
A fulfiller works tickets, resolves requests and acts inside fulfiller workflows, and must be licensed. A requester only submits and views. The boundary between the two decides a large share of total ServiceNow cost.