What this article covers
- The differences between Requester, Fulfiller and Business Stakeholder
- How to think about use rights for users who only view or only approve
- Why user types and product scope should be checked separately
- Conditions to check for app development and AI
When you consider introducing ServiceNow, “how many people will use it” is important information. But that alone does not decide the licenses you need, because the people who submit requests, the people who handle them and the people who check on their department’s status need different use rights.
If you sort out who will perform which operations in which products before asking for a quote, you can consider how you will use ServiceNow after implementation and what it will cost in concrete terms.
The differences between Fulfiller, Requester and Business Stakeholder
ServiceNow has several user types. The typical types that appear in use rights documents for products such as ITSM are Requester, Fulfiller and Business Stakeholder.
A Requester is a user who submits and checks their own requests and searches knowledge articles.
A Fulfiller is a user who performs operations beyond the scope allowed for a Requester or a Business Stakeholder. For example, a service desk member who handles inquiries from other users and updates the records is a Fulfiller. The term does not refer only to administrators and developers.
A Business Stakeholder is a user who approves and views records and reports within the contracted scope of the product. The information they can actually view also depends on access settings.
Make “view only” and “approve only” specific too
Even “checking the status” requires different use rights depending on whether you look at your own inquiries, at the cases of your whole department, or at individual records from a report. You cannot conclude that no license is needed just because a person does not update anything.
Nor can you decide by job title alone, such as a manager being a Business Stakeholder and a staff member being a Fulfiller. If a person corrects content or handles the work in addition to approving, those operations must be included in the check. List the permissions and the number of people needed, including people who use the system only occasionally.
Check user types and product scope separately
Having Fulfiller use rights does not mean you can use every ServiceNow product. If you use CSM in addition to ITSM, or roll out your own apps with App Engine, check the use rights for each.
Besides models that count users according to their permissions, contracts include options such as Unrestricted User, which covers all active users. The models available differ by product and contract terms, so it is important to share not only the total number of employees but also the users’ roles and your rollout plans.
Note that even if a role has been assigned and a user can perform an operation, you still need to check separately whether the required use rights are under contract. If ServiceNow is already in place, it is also necessary to compare the contracted quantities with how roles are assigned.
Plan ahead for additional app development and AI
When developing your own apps, also check the conditions for App Engine and custom tables. Even if your contract has room for more tables, they cannot always be used for any business purpose. What needs checking depends on whether you are extending an existing product or building a new business app.
When using generative AI or AI Agents, check not only the target features but also the units of usage such as “Assists,” the amount included in the contract, and the terms when you exceed it. In addition to who will use it, what processing will run and how often are the inputs for estimating cost.
The packages have also been updated. As of November 2026, the official US ITSM page presents Foundation, Advanced and Prime. When reviewing an existing contract, check your current order forms and use rights documents, and then compare the options ahead.
Thinking about current use and the next rollout together
You do not need to decide every requirement from the start. You can begin by sharing the target work, the operations and number of people for each type of user, and the features you want to add.
SYSLABO can help with everything from ServiceNow license sales to implementation, development and operational improvement. We listen to your business and future plans, and work with you to decide the use rights you need and how to implement them.
Note: This article is based on public materials as of November 2026. For actual use rights and pricing, check the applicable order forms and contract terms.
