Do you want to know more about the features and benefits of CORTEX’s Enterprise Governance capabilities? Watch our video with Stephen Connor and Eddie Watson, who explore how role-based access control and version control empower organisations to govern Automation effectively, achieve scalability, and enhance collaboration across different teams and departments.
You can also read the full transcript below.
I think you know, as Automation becomes more prevalent in an organisation, it’s going to be really important for the organisation to know, who’s defining that Automation, what version of the Automation is executing in production, who’s making changes to it, those sort of things. And so, with CORTEX, the role based access control, lets the organisation define exactly who has those types of rights, the HR team can make changes to Automation that is HR related. And for example, the finance team can only make changes to Automation that’s finance related and not vice versa. So with CORTEX role based access control, you can define that type of, of operational organisational governance.
So I think going further into that is that the role based access control allows you to compartmentalise Automations, that are relevant for various departments, people, and individuals. But if you imagine trying to control differences in code, you know that you can do a difference in code, the neat thing about the version control with Automation, is it graphically it does the same thing. And it highlights where that the graphical Automation has been changed, or things have been added, detracted or amended.
And what it’s also very, very powerful for is, if you, for example, have different parts of the business or different business units that you can amend the Automations. And you can actually deploy different versions of the Automation that are specific for those parts of the business. So it encourages this community development environment in a very controlled way where when you’re ready to deploy something out into Automation, there are checks and balances that allow that specific version of the Automation to be deployed out into the production environment, and to execute in a known way. And you’ve got management of that. I think that that enterprise readiness is a critically important aspect of the scalability and the power of a CORTEX deployment.
And so as part of that role based access control, you can also limit for example, your Cisco network engineers to be able to create and modify and maintain Automation that affects your Cisco network. And your Nokia engineers to be able to do the same for your Nokia network. But you certainly wouldn’t want to let your Nokia engineers modify your Cisco network or vice versa. And so your role based access control in CORTEX lets you govern and control who can make what changes to which part of your Automation.