foreign [Music] it's Justin thank you for watching and welcome to my house that's Justin's house I've got a new Utah future for you and it has to do again with change management that's right change requests let's do a little refresher here with change request in service now we have this concept of change models okay so I've got it up here on the screen so you can see when I go to create a new change I can select from emergency or normal change using the different models or I have some pre-approved something that sometimes you might call them standard changes but pre-approved models that I can now go ahead and submit and make onto their fields lockdown for some of the fields but Model Management is where we facilitate that now sometimes there's a use case where you might want to restrict what particular models are available to certain types of users and servicenow has that taken care of for us now what I'm all of what I'm going to show you isn't new but I want to be sure to cover the entire feature appropriately there so notice that I navigated to to change Administration and then change models so there it is there's a path that I went to changed Administration change models or you can just type in change model and it'll bring you straight to this one that I selected here change models and you don't have to navigate the menu once you're here you can see the list of available change models I've got change registration Cloud infrastructure emergency normal standard and unauthorized changes no one submits an unauthorized change it's just a way for us to classify something as an authorized change and have a different workflow for it when we detect a change so don't get hung up there but let's open up let's do our use case it's going to be emergency change we may not want certain teams certain users certain people using the emergency Change Model because they haven't been trained on the process or it's just not appropriate for them to use it but giving them their scope and their responsibilities so what we've had in change manage before is this little button called Advanced security and when you select that's button it activates two or three new tabs on the Forum you can see them there available for not available for and can write the new one in Utah that's new and you haven't seen before is not available for so we had available for in Tokyo we had Ken Wright in Tokyo I'm not sure when they came along but I wouldn't check my Tokyo instance just to make sure the not available for is the important one and in a sense what you would do is you'd come in here it's like not available for and you would think that you'd click the edit button or new and go ahead and create a user criteria for that but no don't do that what you want to do first after you check that advanced security button is you need to save the form save the change model because that's an unchanged field on the change model so let's go ahead and do the right thing here let's click save and that'll save it and now I can go ahead and edit what's in that list for not available for so we'll go ahead and edit there and it's going to show me all these different groups that I can add users roles or whatever someone's defined using different user criteria so let's just say anybody with ITIL not admin we are going to make that not available for them right so that ITIL non-admin if we take a look at that role we see what the user criteria is or that group and it is they have the role I2 so basically we just stopped everybody who's using itsm from using the emergency change request probably not a practical example but hopefully gets the message across and let's round this out with well how do I develop those different groups and those different uh criteria for my users well search your member search your menu for user criteria and notice in the change management menu under Administration I have another option for user criteria so that's where you can come in and go ahead and create different groups of users that as may be necessary maybe it's a certain group or several groups maybe it's people with a certain role like we just did with ITIL whatever it is you can come in and Define that and you'll probably notice on the other screen we can even flip into an advanced mode and do some scripting in order to find what we want it's probably easier for most of us to do a user a group a role a company a location a department which you can see there in the middle of the screen and we can even specify whether that's going to be any one of these apply or you have to match all the things that we've put in these boxes in order for that user criteria to work but that's it that's the new feature in servicenow Utah the ability to specify when a change management change management model is not available for somebody as opposed to available for somebody I hope you find this video helpful if you did please like Please Subscribe or share it with somebody who you think might be interested in controlling access to their changed models in service now and until next time don't forget to always be learning [Music] foreign [Music]