Dialog: Permissions
Function: The permissions of user groups are defined here, with which they can execute specific actions on specific objects in the project.
Call: command
Every change made in the dialog is applied immediately.
Actions
All possible actions on objects of the projects are listed in Actions. The actions are divided into four categories and mappings to all current objects of the project are listed below each action. For each "action->object" mapping, you can define the permission for each existing user group.
Action categories:
| Actions regarding the execution of commands |
| Actions regarding the configuration of user accounts, user groups, and their permissions |
| Actions regarding the creation of object types |
| Actions regarding the viewing, modification, removal, and child-object handling of objects of the project |
Actions in detail:
| Execute a menu command |
| Create a new object in the project |
| Add or remove a child object below an existing object |
| Modify an object in the editor or modification of user, group, and permission settings in the corresponding editor/dialog |
| Delete or remove an object |
| Open the view of an object in the editor |
![]() | Possible target of an action This can be specific objects of the project, or the user, group, and permission configuration. |
Permissions
All defined user groups (except the "Owner" group) are listed in Permissions with a toolbar for configuring the permissions of a group.
| The action, which is selected in the actions view, on the selected target(s) is granted for the selected group. |
| The action, which is selected in the Actions view, on the selected target(s) is denied for the selected group. |
![]() | The permission that executes the actions, which are selected in the Actions view, on the selected targets has not been defined explicitly. However, the actions are granted by default. For example, because the corresponding permission has been granted to the parent object. Example: The group has the permission for the "myplc" object. As a result, it also has the permission by default for the "myplc.pb_1" object. |
![]() | The action, which is expanded in the actions view, on the selected targets has not been denied explicitly. However, it is denied by default; for example, because it has been denied to the "parent object". |
No symbol | There are currently multiple actions selected in the Actions view for which the group does not have the same permission. |
Toolbar:
| The selected action on the selected target object is granted explicitly for the selected group. |
| The selected action on the selected target object is denied explicitly for the selected group. |
| The permission for the selected action on the selected target object is reset to the default value for the selected group. |
Export/Import | Opens a menu with the commands
|
Export all permissions | Exports all actions and their configured access permissions of the current project to a user-specific file of data type To do this, the Export Permissions dialog opens for you to specify a file name and to select a location in the file directory. The default file type is |
Export selected permissions | Exports all selected actions and their configured access permissions of the current project to a user-specific file of data type To do this, the Export Permissions dialog opens for you to specify a file name and to select a location in the file directory. The default file type is |
Import permissions | The contents of a If the permissions of the imported file differ from the permissions in the project, then the permissions in the project are overwritten. To do this, the Import Permissions opens for you to select the |
For more information, see: Using Permissions to Protect Objects