Within an AE system, various tasks are executed on a variety of systems. A well-functioning authorization system is therefore extremely important. AE provides efficient functions which facilitate the creation of your own authorization system.
Automic recommends planning your authorization structure thoroughly as this simplifies all the subsequent assignment of rights. Use naming conventions from the very beginning. You can name objects and folders by referring to the field of activityAn activity (or task) is an entity that can be planned, assigned to a user or a team and tracked with respect to their plan and state (started, cancelled, suspended, completed)., operating system or departmentDepartment name to which the Automation Engine user belongs., for example.
Identify the people that should have authorization to access your AE system. In the next step you can decide on who actually performs which activity. Only assign rights that are required. Based on your findings you can groupAn Automation Engine object type that integrates tasks so that they can be processed together. users in user groups, thereby reducing administrational work.
Agents are also part of the authorization system. Therefore, the first step following installation should be to assign adequate rights to them.
Rights do not only influence objects. Particular functions in the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] are also affected (e.g. the System OverviewThe UserInterface window that contains information about the Automation Engine system.). The applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. areas of AE Script also depend on them.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |