Privacy Functional DomainFunctional Domain for Privacy The Functional domain field is added in the Settings tab to segregate a particular data and classify it as Privacy related data. All the privacy related compliance library should be tagged with Privacy. The Functional domain field is available in all compliance library related forms such as Entity, Control, Control Objective, Policy, Authority document, Citation, Issue, Indicator, Indicator template, Acknowledgement campaign, Policy exception. As a system admin, you can define this configuration by navigating to GRC Administration > Functional domains > Domain inheritance. User must manually add the tag, functional domain, in the base forms such as Policy, Authority document, Entity type, Entity class, Entity, Plan, Engagement for auto-tagging the child records. When a parent table is tagged with a particular functional domain, and if the user removes the tag from one of its child records, then the removed tag is not added during auto-association. Similarly, if the user manually adds a tag, then the added tag is not removed during auto-association. The GRC functional domain user action [sn_grc_functional_domain_user_action] table captures and stores all manual actions of the user in the Functional domain field of the record that belong to a particular table in the respective functional domain. The below objects are pre-confgured for setting the functional domain as privacy. One can customize the automatic tagging of related objects when assigning a functional domain like Privacy to an object. In the below use case, when Policy is tagged with Privacy, all the issues. policy exceptions, policy acknowledgements, control objectives and child policies will be auto-tagged with Privacy. Adding new configurations Privacy Admin/Privacy manager can add in new configurations for the functional domain auto-tagging other than the predefined configurations. Navigate to module Functional Domains > Domain inheritance.After the parent record is created, you must associate the child relationships required for this configuration. Open the record in the related list where there is an option to create new relationship or add existing (Edit) ones. Ensure the 'table' field in domain inheritance record and 'table' field in the relationship registry record are the same.Ensure the fields Reference column and M2m source column are populated based on the relationship type. If not added run the fix script 'Populate new fields in relationship rec'.Fix script populates only the column names when it gets one field with the queried reference type. In case of multiple fields with same reference type then we need to manually add the appropriate field name. Frequently asked questions When does the control or risk will be tagged as privacy? When a control objective/risk statement is associated to a processing activity, controls/risks are associated to processing activity. When these are associated, the control/risk are tagged with Privacy. When does the entity will be tagged as privacy? When a processing activity is created for an entity, it will be auto-tagged as Privacy. The auto-tagging is not reflecting when an object is tagged with Privacy? The auto-tagging is taken care by a schedule job 'GRCObjectsFunctionalDomainChanges' which runs daily. This will be reflected once the job runs.