Service mapping roles

AR2
Kilo Explorer

As per the whitepaper on Service Now its states on the below roles required for service mapping sm_admin, sm-user & sm_app_owner

Pls advise if it’s a best practise to assign admin roles to all the app SMEs or app teams to design their own model? OR

Is there any self help options available? 

Roles & responsibilies as per Snow

sm_admin - Sets up the Service Mapping application. Maps, fixes, and maintains application services. Also performs advanced configuration and customization of the product. Assign this role to application administrators.

sm_user - Views maps for operational application services to plan change or migration, as well as analyze the continuity and availability of services. Assign this role to application users.

sm_app_owner - Provides information necessary for successful mapping of an application service. Once a service is mapped, this user reviews the results and either approves it or suggests changes. Assign the sm_app_owner role to users who own application services and are familiar with the infrastructure and applications that make up the services.

 

 

 

 

 

2 REPLIES 2

Ashutosh Munot1
Kilo Patron
Kilo Patron

Hi,

If the need is to create a whole service map then sm_admin role is required. Also if the want to do something with patterns then its good. If they just want to normal relationship on service map then itil roles is also allowed with sm_user to create application service.

Thanks,
Ashutosh

For users to create "Maintenance Schedule" and it's associated "Schedule Entries", is there any other role that is comparatively less powerful than sm_admin role?