All modules overview
Quick answer
ServiceNow is a single cloud platform that hosts dozens of products (commonly called modules or applications). They all share one data model, one workflow engine and one UI, which is why a change ticket, an HR case and a security incident can all reference the same CMDB record.
Key takeaways
- The four big workflow pillars
- One platform, shared services
- How to use this section
- Try it Yourself
ServiceNow is a single cloud platform that hosts dozens of products (commonly called modules or applications). They all share one data model, one workflow engine and one UI, which is why a change ticket, an HR case and a security incident can all reference the same CMDB record. This page maps the whole catalogue so you can see how the pieces relate before you dive into any one of them.
The four big workflow pillars
ServiceNow groups its products into workflow families. Everything below runs on the same Now Platform / App Engine foundation.
One platform, shared services
The reason to learn the modules together is that they lean on the same platform services: the CMDB for configuration data, Flow Designer for automation, the Service Catalog and Service Portal for request experiences, and Now Assist for generative AI across every workflow.
How to use this section
- Start with ITSM, it is the most widely deployed and teaches the core task model everything else reuses.
- Then follow the family most relevant to your role (IT, customer, employee, or planning).
- Each module page links down to its deep-dive lessons and the developer topics that power it.
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What do all ServiceNow modules share?
- A. One platform, data model and workflow engine
- B. Separate databases per product
- C. Nothing, they are unrelated apps
Show answer
A. One platform, data model and workflow engine
Every module runs on the same Now Platform instance and data model.
Which module is the best starting point for the core task model?
- A. ITSM
- B. Telecommunications SM
- C. Legal Service Delivery
Show answer
A. ITSM
ITSM teaches the incident/problem/change task model reused across the platform.
Cross-module workflows (incident spawning a change) are...
- A. Native to the shared instance
- B. Always external integrations
- C. Not possible
Show answer
A. Native to the shared instance
Because modules share one instance, these flows are native, not integrations.