Group management and change practice

[Diane22]

In our environment, I am responsible for Group Management in ITSM.  New groups are created by our platform core team, supported by a request item as this would be an auditable activity.  Operationally, we modify (add / remove members or retire) groups autonomously, supported by a request.

It was suggested that it may be a better fit with a standard change -vs- a request.

Wondering what most folks do out there?  I've never viewed a new group as a change, mostly because it would not need to be planned, scheduled, 'implemented, and tested, nor require approvals (other than from a Group Management resource).  This activity is more of a collaboration with the requester, ensuring that what they propose aligns with our Operational Service and Support model.   

Just looking for other opinions as to how others process these request types,

thank you,

d-

[Dr Atul G- LNG · Accepted solution]

Hi @Diane22 

Agreed, creating a new group is a request, not a change, because a group is foundational data, and its creation is a standard process with approvals and tasks in place. While standard changes typically don't require approval, group creation may require it, making it distinct from a change process.