Automic Workload Automation

User authorizations will allow you to set object-related permissions. For instance, if I want the user TESTSAA to only able to run all JOBS with login object @LOGIN.SAA, but not edit them or modify them, I will need to set the permissions as below :

• JOBS : Name '*' for all names and 'X' for execution authorization.
• FOLD: here '*' with read (R) permission for all folders. I could as well restrict the folders that can be seen by this user, by setting their names, or using a wildcard (e.g. FOLD* would allow the user to read FOLDER1, FOLDER2, FOLDER.TEST, etc.)
• JOBI: by default jobs contain a job include (JOBI) object, like HEADER.UNIX and HEADER.WINDOWS. Without permissions on at least these objects it will not be possible to run jobs that use theseincludeobjects.
• LOGIN: usually a job will require a login object to be executed.
  

These can be adjusted either at the user or the user group level.

To complete this post, I'd like to share a question recently asked:

I want to assign one of my team member just access to create new users in Automic client joining the team.

This kind of user should have access to FOLD objects, because Users are saved in folders. It should also have rights on USER objects to edit, create and probably delete them also:

https://us.v-cdn.net/5019921/uploads/editor/bp/83qmpqfp7dyc.png" width="785">

WARNING - For AWA version 12 and the AWI:
Rights for this kind of users are slightly different. In addition of Authorizations, you should give access to the administration panel to the user: <Your User> > Automation Engine > Privileges > AWI Access Control > Access to Administration.

https://us.v-cdn.net/5019921/uploads/editor/xv/j6w3p44rb7iu.png" width="1098">

Finally, you should give read authorization to the variable UC_CUSTOM_ATTRIBUTES, that give access to Automation Engine tabs of users created.

https://us.v-cdn.net/5019921/uploads/editor/qg/ts6okcoa10if.png" width="1600">

The user is now configured.