More control over how security works within intelligentcontract has now been released. The change relates to how security groups are inherited when creating new records. For example, if a particular security group has been assigned to a contract, what security groups are automatically applied to an alert when its added to that contract.
The options now available are:
(Not-Linked) Security Group changes applied ONLY to future Sub Tab records. Sub Tab security is editable - if selected, any changes to a records Security Group value will only apply for future Sub Tab records created, all existing Sub Tab records will keep their previous Security Group values - the Sub Tab record Security Group field can be edited
(Linked) Security Group changes applied to All sub-tab records. Sub Tab security non-editable - If selected, any changes to a records Security Group value will ripple down to all existing and future Sub Tab records - the Sub Tab record Security Group field cannot be edited.
(Semi-Linked) Security Group changes applied to ALL sub tab records. Except where sub tab Security has been manually changed. Sub tab security is editable -If selected, any changes to a records Security Group value will ripple down to all existing and future Sub Tab records , except if a Sub Tab records Security Group has already been updated - in this case the existing value will remain. The Sub Tab record Security Group field is editable.
This article describes how security groups work in detail: Security Groups
Paul John Darlow
More control over how security works within intelligentcontract has now been released. The change relates to how security groups are inherited when creating new records. For example, if a particular security group has been assigned to a contract, what security groups are automatically applied to an alert when its added to that contract.
The options now available are:
This article describes how security groups work in detail: Security Groups