Why Shared Groups Between ITSM and CSM Will Cause You Problems

[sgrison]

ServiceNow ITSM and CSM are designed to serve different audiences. ITSM serves your internal employees, CSM serves your external customers. On the surface, sharing a group across both seems harmless - one team handling two channels. In my experience, it's one of those decisions that creates subtle but serious problems down the line.

Here's where it breaks down. Groups in ServiceNow drive assignment, but they also influence record visibility and user lookups. When a group is shared across ITSM and CSM, any field that references the user table starts pulling from a combined pool. That means fields like Caller on an incident or Requested For on a request will include customer contacts - external users sitting in your CSM customer account structure - right alongside your internal employees.

That's a problem. An agent creating an incident shouldn't be picking from a list that includes external customers. Beyond the user experience issue, it introduces the risk of data ending up in the wrong place - an incident raised against a customer contact, or a request attributed to someone outside your organization entirely.

The cleaner approach is to keep your ITSM and CSM groups separate, even if the same people are members of both. Two distinct groups, maintained intentionally, gives you the control to scope user lookups, visibility rules, and reporting correctly for each domain.

In my experience, this is the kind of thing that gets flagged late - usually after someone notices odd names showing up in a Caller lookup or a report that doesn't make sense. Get ahead of it during your group design phase and you'll save yourself a difficult conversation later.