Licence Clarity

[joecurry105]

Apologies in advance, I wasn't sure of where the best place to put this was. In theory it's more of an ask to ServiceNow, but someone in the community may be able to assist. 

As we're all painfully aware, ServiceNow's license model is beyond confusing. While I've managed to find some posts which try to help, they're still not totally clear. The best I've been able to find is Confused by ServiceNow licensing? - ServiceNow Community, but that still doesn't look at individual modules, just the potential models that may be used. 

What I would love to see is an update to the documentation. Every module should have a page where it explains the licences involved. I'm not expecting costs as I know they're done on a quote basis, but the licences are a technical specification, they should be clearly outlined in the documentation. 

The best example I've been able to find is on Hardware Asset Management licensing • Australia Asset Management • Docs | ServiceNow. This has a clear table with examples. 

I've spent the last hour just trying to find out if WSD uses a license model where all users pay, or one where only the fulfilment team pay.

We also use HRSSD and I need to know whether licenses are applied to users when they first login or when they're assigned a role which allows them to use the HRSD module. And when they leave, how does that licence get revoked? Can I just disable the account or do I have to fully delete it? 

I work in a large organisation (over 20k staff) so license management is very important. This massive gap in knowledge is a major hinderance and is likely to result us moving away from ServiceNow as a whole due to the massive costs that occur as a result of not being able to manage the licenses properly. 

[VJ_Srivastava]

Hello @joecurry105,

From an enterprise architecture and platform ownership perspective, your frustration is incredibly valid and represents one of the most common risks to ServiceNow scalability.

The reason you cannot find a simple, static documentation page outlining exact licensing triggers for WSD or HRSD is because ServiceNow's licensing architecture has fundamentally shifted, and it varies heavily based on the specific Master Services Agreement (MSA) your organization signed.

Historically, ServiceNow was licensed on a strict "Fulfiller" model (you paid for the IT agents fulfilling the work, while end-users were free). However, enterprise modules like Workplace Service Delivery (WSD) and HR Service Delivery (HRSD) represent a shift toward "Requester" or "Total Employee" licensing.

• Because the primary value of WSD and HRSD is enterprise-wide self-service, they are typically licensed based on your total employee headcount, regardless of whether every employee logs in on day one.

• The danger arises when custom architecture blends these modules. For example, if you accidentally assign a custom role to your entire employee base that the system interprets as a "Fulfiller" role, you can instantly consume thousands of unintended fulfiller licenses.

To protect your organization from a massive true-up bill, you must establish strict platform governance. Do not rely on generic documentation; require your architectural team to map every single custom role and group directly against the entitlements listed in your specific ServiceNow contract before deploying new modules to production.

 

[VJ_Srivastava · Accepted solution]

To answer your specific technical questions regarding user management and module access:

• Disabling vs. Deleting Users: You should never delete user accounts in ServiceNow. Deleting a user orphans all of their historical records (Incidents, HR Cases, Approvals), which breaks your audit trails and database referential integrity. To revoke a license, you simply set the user's profile to active = false. The Subscription Management engine automatically runs a scheduled job that unmaps inactive users from your license pools.

• How Licenses are Applied: Modern ServiceNow environments use the Subscription Management module. Licenses are not strictly applied just because a user logs in. They are applied based on User Sets (groups of users defined by conditions, like all active employees) or by the specific Roles assigned to them.

• HRSD and WSD Mechanisms: Technically speaking, both HRSD and WSD typically utilize a "Per Employee" licensing model rather than the traditional "Fulfiller" model used for ITSM. This means your Subscription Management module is likely counting the total number of active=true users who are eligible to submit an HR case or book a desk, not just the agents working the tickets.

I highly recommend navigating to Subscription Management > Subscriptions in your production instance. It will show you exactly how your specific instance is counting allocations (whether by Role, User Set, or Custom Metric) based on your current contract.

[Tanushree Maiti]

Hi @joecurry105 

For License related query , I will suggest you to reach out to your Servicenow Account Executive for  licensing details.