 Welcome to the ControlM Automation API video about managing roles and authorizations using CLI and APIs. In this video, you will learn about our new ControlM version 19 API capabilities, which enables users to manage authorizations using the standard CLI or REST APIs. You will also learn how to create a new role and deploy it using the CLI. This video is intended mainly for ControlM administrators. However, other ControlM users or application owners who have security permissions can also perform these actions. In ControlM version 19, we are extending the API offering to include access to configuration management and operations, which are normally performed through the ControlM Configuration Manager, or CCM. In previous ControlM versions in the CCM, an administrator defined authorizations or roles, formerly known as groups, for users or LDAP groups, one at a time, which can be time-consuming. Using ControlM APIs, an administrator or ControlM user with the appropriate security permissions can run multiple and repeated operations using the standard CLI or REST APIs. This enables administrators or other designated users to provide faster service. They can quickly and easily define roles and assign them to users in LDAP groups and maintain existing roles. Note that the CLI installation is part of the ControlM version 19 installation. Before you can use the CLI, you need to set up a ControlM environment and direct the CLI to the ControlM environment that you are working in. See the ControlM Automation API help for more information. For this video, we will use the CLI to create a new role with authorizations by getting an existing role in a JSON file, modifying the JSON file and saving it as a new file, and last, deploying the new role to ControlM. Note that you can use REST APIs to perform these actions or operations. First, we'll get an existing role. In the CLI, we'll enter the command to get the existing role, and then enter the folder where we will save the file with its new name, Dev1Role. For this video, we'll save the new file to the temp directory, but most likely the file would be saved in your file system or version control system. Now we will open and edit the JSON file and save it as a new role. Before we edit the file, let's take a quick look at what's in the JSON file. Here's a filter of the jobs that this role has access to. Here are the allowed job actions that this role can perform. Here are different control and privileges. And here are the access levels to different control and resources such as folders, calendars, etc. Now we'll make the changes to the file. We'll change the name of the file and the description. And we'll also change the filter for the allowed jobs for this role. And now we'll save the modified JSON file. Note that you can assign other permissions and privileges as needed. For more information, see the ControlM Automation API Help. Next, we'll deploy the new role to ControlM. Returning to the CLI, we'll enter the following text. We can see that the role was added successfully to ControlM. And last, let's look at the new role we created in the CCM. We'll click Security and then Authorizations. In the Roles tab, we see the new role that we created. Using the CLI, you can create a script that allows you to deploy multiple roles. And you can automate the entire process by scheduling the script using the standard API CLI. Watch our next video that shows how to create a user and assign a role to the user and an LDAP group using the CLI. Thank you for watching this video.