The fulfiller and requester split describes what a user does on records. A fulfiller assigns, updates, resolves or closes work items. A requester raises requests, follows their own items or confirms an approval. The exact names and terms come from your subscription, so check your own agreement. Deciding which type each user needs is mostly a role-mapping exercise, and it is worth doing carefully because the number of users holding fulfiller access is the figure to check against your own terms.
Start from what each role does, not what it is called
Job titles are a poor guide. A team lead may approve changes one week and close incidents the next, and a title such as coordinator can mean anything from a read-only reporting role to a full dispatch function. Begin with the roles configured in your instance, then describe each one in three parts: the applications it opens, the actions it takes on records, and whether it ever changes a record that belongs to someone else.
Read the permissions a role actually grants instead of relying on its description. Descriptions are written once and then drift, while the permissions are what the platform enforces. Where a role grants more than its description says, record the gap.
Mapping each role to a fulfiller or requester license
Work through four steps in order. First, group roles by the kind of access they give: work fulfilment, administration, or request and approval only. Second, check each group against recent use and ask whether the user updated or closed a work item in the review window. Third, where one person holds several roles, check against your agreement which license type the combined access falls under. Fourth, write the decision and its reason beside the user, so the next reviewer does not have to rebuild the logic from scratch.
The table below uses four invented roles to show the pattern. Your instance will have its own role names, and your agreement defines the license types, so treat the outcomes as a method rather than a ruling.
| Fictional role | What it does day to day | Likely license type |
|---|---|---|
| Dispatch coordinator | Assigns and reassigns work items and updates their status | Fulfiller |
| Site manager | Raises requests for their site and confirms spend approvals | Requester, if approval-only under your terms |
| Regional reviewer | Reads dashboards each month and edits no records | Requester or reporting access, depending on your terms |
| Field technician | Closes work orders every day from a mobile device | Fulfiller |
What a requester can reach in the Self-Service app by default
The Self-Service application gives end users a front end to their IT support organization. By default it provides common actions such as a homepage, the Service Catalog, knowledge articles, incident work and surveys. Use that default set as the reference point when you check what each requester actually does in your instance, because it is the baseline a configuration starts from.
Treat the default set as a starting point and check it against what your instance shows each user. A requester who reaches an approval or a record edit through a custom form is doing more than the defaults cover, and that difference matters when you decide which license type the user needs.
Approvers who hold more access than their work needs
Approvers are a group where extra access tends to build up. An approver who only confirms requests is not doing fulfilment work, but people pick up a second role over time, such as one that lets them edit the underlying record. That extra role lets the same person act on records in ways the business would not count as fulfilment. Remove the extra role and keep the approval step, then confirm that approvals still complete before the change reaches production.
Users who both approve and fulfil need more care. Someone who approves a purchase on Monday and closes the related task on Tuesday will usually need fulfiller access for the second action. Splitting that person into two accounts can look like a fix, but check how your agreement treats separate or shared accounts before you do it.
Finding over-assigned users without trusting a single ratio
A common shortcut is to set a target for the fulfiller count as a share of total users and aim to hit it. A single ratio tells you very little. A service desk with many fulfillers may be entirely correct, and a low count can hide people who hold fulfilment roles they never use. Compare assigned roles against activity across a window long enough to include a month end and at least one periodic task, such as a quarterly review. The cost factors that sit alongside license type are covered in the cost factors that shape a ServiceNow licensing plan, and they should inform how you set that window.
Treat activity as evidence, not proof. Someone on leave, or a manager covering a queue for a week, will look inactive for reasons that have nothing to do with their license. Users with no fulfilment activity across the window are candidates for review, not automatic removals. Where usage data has to come from more than one system, ways to connect license usage data to your review set out the common approaches.
Using the fulfiller workspace to see real assignment load
The Simplified ITSM landing page shows the signed-in fulfiller three counts: items assigned to them, items breaching or about to breach, and unassigned items. Each count covers incidents, requests and catalog tasks, so one view shows the queue a person holds across those three record types. Treat it as a snapshot taken when you look, not a verdict on its own.
The view depends on roles. The Simplified ITSM view appears for users who hold the Service Desk Agent role. To reach advanced flows such as Major Incident Management, the user must not hold that role alongside itil or admin roles. Check the role set before and after any downgrade, since the landing page a user sees can change with it.
Contractors, leavers and the risk of downgrading
Contractors can be given fulfiller access for a project and keep it after the project ends. Where your onboarding process allows it, set an end date on contractor access when it is granted. Check that the leaver process removes both the account and its roles, because a process that handles one but not the other leaves a gap that only an audit tends to find.
Downgrades carry their own risk. Removing a fulfiller role removes the record actions that role allowed, so an assignment or approval that depends on them can stall. Test each affected workflow in a non-production copy first, then move changes in small groups so that any breakage traces back to one batch. Keep a record of what each user held before the change so you can restore it quickly if a workflow stops.
Questions teams ask about fulfiller and requester licenses
Which users need a fulfiller license and which only approve or request?
The usual test is whether a user changes work items beyond their own requests, by assigning, updating, resolving or closing them. A user who only raises requests, follows their own items or confirms an approval normally falls under the lighter type. Confirm the boundary in your own agreement, because the wording of user types and any approval exceptions varies.
How do approvers and contractors affect the cost of the subscription?
How fulfiller access is counted depends on your own terms, so check them. If your terms count each user who holds fulfiller access, an approver or contractor given a fulfilment role adds to that figure even if they touch the platform only a few times a month.
Is there a sensible balance between fulfillers and requesters?
There is no universal ratio that makes a configuration right. A balance that suits a large service desk would be wrong for a team of specialists who each close their own work. Use the ratio only as a prompt to look harder, and judge each group against its activity. If much of a group acts on records in a typical week, its fulfiller count is probably justified. For the wider program, the ServiceNow software license optimization guides place this review alongside the other steps.
Will downgrading a user disrupt their workflows?
It can. The risk sits in the work a user picks up automatically, such as assignments, approvals and scheduled actions, rather than in what the user does by hand. Test those flows before downgrading, and keep a record of the previous roles so you can put them back if a flow stops.