Security Group

You can package and deploy a Security Group definition and its associated artifacts from one environment or repository to another environment or repository using the package feature in AVEVA Work Tasks.

You can package the security group from the following three levels:

• Repository level

• List level

• List item level

Repository Level

In repository level, you can only overwrite the standard security group. You cannot create or delete the standard security group.

List Level

At list level, you cannot create or delete security groups. You can only overwrite the security groups at list level.

List Item Level

At List Item Level, you can select and package individual security group. When installing or updating the package in the target environment, the package checks whether the security group customization is enabled at the list item level.

Notes:

• You cannot create or delete a security group at List Level or List Item level. Thus, the Resource Mapping is identified option is not available in both the List Level and List Item Level Security Group Configuration Settings.

• You cannot package a standard Security Right as an associated artifact.

• Web part page will not be packaged with the security group as an associated artifact. It will just provide a reference to the web part page in the target environment. After the security group is installed, if the web part page is present in the target environment then the security group is linked to it.

• A list item from a dynamic list, such as Employee list can be edited or viewed using different forms or form versions based on the security rights given to the logged in user.

• For an existing Security Group, you can get a backup of the artifact that is available in the target environment.