Skip to main content

Setting Up User Management in the Project

In CODESYS Safety Extension, a safety user configuration is integrated for a project with safety application. The project manager can use this safety user configuration for his project or create his own user management.

Tip

The project manager must already decide at the beginning of the creation of the new project in the New project dialog whether he would like to create an Empty project without user configuration or an Empty Safety project with safety user configuration (see Setting Up the Safety Application). If an Empty project is created (i.e., a project without safety user configuration), then the project manager must create a user management for the safety project himself (see User Management, Rights Assignment in CODESYS Help).

Tip

The permissions assignment for the user management is located in the Project menu (User Management and then Permissions).

Tip

Every user belongs automatically to the Everyone group.

Settings the safety user configuration

This user management already contains the following settings:

. User groups
  • Owner

  • Safety

  • Safety.ExtendedLevel

  • Everyone

. Users
  • Owner belongs to the Owner group

  • saf belongs to the Safety group

  • ext belongs to the Safety.ExtendedLevel and Safety groups.

The preset users do not have a password yet. The Owner group already includes the Owner users, but still without a password. The Owner user can assign corresponding users to the "Safety", "Safety.ExtendedLevel", and "Owner" user groups in the menu Project → Project settings → Users and groups, and issue passwords to the users.

The Owner user can define new user groups. A new user group initially has the permissions of the Everyone user group of the Safety User Configuration. Through the assignment of a new group to other, already existing user groups (e.g. Safety, Safety.ExtendedLevel), the new group receives the access rights of the group to which it is assigned.

Tip

The project manager must issue a suitable, safe password to the "Owner" user, in order to ensure the access protection of the project.

Procedure. Password definition
  1. Open the Project menu.

  2. Click Project Settings.

  3. In the Project Settings dialog, select the Users and Groups tab.

  4. On the Users tab, select the Owner entry.

  5. Click the Edit button.

  6. In the Edit User dialog, enter the old password, the new password, and the password confirmation.

  7. Click the OK button.

For more information about assigning passwords, see: User Management and Password Manager in the CODESYS Help

The permissions to commands, users and groups, object types and project objects are specified as follows in the user management, but can be changed at any time by members of the Owner group.

. Rights assignment of the Safety User Configuration
  • The Owner group has all permissions.

  • The Safety group does not have

    • Permission to create an Extended POU (Safety)

    • Permission to create an External POU (Safety)

    • Permission to Execute the Safety FBD: Insert Return command

    • Permission to Execute the Safety FBD: Insert Jump command

    • Permission to Execute user management Commands.

    • Permission to Edit the Users and groups.

  • The Safety.ExtendedLevel group does not have

    • Permission to Execute user management Commands.

    • Permission to Edit the Users and groups.

  • The Everyone group does not have

    • Permission to execute the Commands in the Safety category

    • The Rights to Generate the safety object types.

    • Permission to Execute user management Commands.

    • Permission to Edit the Users and groups.

Notes for the development of a safety application with the Safety User Configuration

The developer must be a member of the Safety.ExtendedLevel user group in order to insert an Extended POU (Safety).

After inserting a safety controller or the Safety Application object, the change rights for the Application (Safety) object are to be explicitly configured in the Properties dialog of the Safety Application object on the Access Control tab as follows:

For a detailed procedure, see: Further procedure for safety project with user management template.

  • + for Safety

  • + for Safety.ExtendedLevel

  • - for Everyone

After inserting an Extended POU (Safety), the developer must make appropriate settings on the Access Control tab in the Properties dialog of the Extended POU (Safety) to explicitly deny the Safety user group the right to Edit and Remove the Extended POU, if the Extended POU is to be edited and removed only by members of the Safety.ExtendedLevel user group.

Creation of a new project without a safety user configuration

If a new project is created as an Empty project, then the project manager must create a suitable user management for the safety application of the project. Refer to the CODESYS Help for the exact procedure and detailed information about the creation of this user management in the project.

In order to facilitate the selection of the safety-specific commands and object types for the developer, Safety is placed before the commands and object types that are relevant for the Safety developer in the permissions assignment.

Tip

If the developer does not have the permissions for a particular operation, he can login during the operation using a user name with more permissions. (Activation of the User Management → Logon user command in the Project menu)