[00:00] When sending voice notifications, you typically want your users to validate their identity by typing in a PIN. This way you can verify that the intended user is listening to the message and not just whoever picked up the phone. Fortunately, this is very easy to set up, it just takes two parts. The first part, if you head over to the Configure Section of your gateway, under Security and Users and Roles, I'm going to make a change to one of my users in my default User Sources here, so I click the Manage Users button on the right and we'll give George here a PIN. This will be the number he'll have to type in. We'll head over to the right and click the Edit link. I'll scroll down the list of all of George's properties here and if you have the voice notification module installed, you'll see a security PIN property. We'll give George here a PIN to use. Note that you'll need to give a PIN to each user that the system will attempt to call. Once you're finished, click Save Changes. Step 2, we have to enforce the use of PINs on our pipeline, so we want to head over to our designer for this next part here, I'm going to bring my designer real fast, and in the Project Browser here, you can see I'm under Global, under notification pipelines and I'm looking at a pipeline. I have a notification block down already, I'm going to specify that it needs to use a voice notification profile and when you do, there will be this "Require PIN" property. So if it's at the "False", the system won't ask for a PIN but of course, I'm going to click over here where it says "False", select "True" and then we can save our project. Now, when this notification block here tries to call users on this roster, the system won't ask each user for their PIN which George now has.