--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Regulatory alerts # Regulatory alerts {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Regulatory alerts Regulatory alerts in ServiceNow aggregate regulatory events and documents from multiple intelligence providers, offering continuous updates on regulatory changes. These alerts, resembling web feeds, are managed within the Regulatory Change Management application, which transforms and maps the alerts into structured records. Each alert record contains metadata to help stakeholders translate changes, plan actions, and ensure compliance with evolving regulations. Show full answer Show less ## Types of Regulatory Alerts and Associated Tasks * **Regulatory Event Alerts:** These alerts provide general updates on regulatory changes and news, created automatically from RSS feeds. They trigger *regulatory change tasks* to evaluate and update related GRC objects like policies and controls. * **Source Document Alerts:** These focus on specific changes to citations within authority documents, available when integrating with third-party providers such as Thomson Reuters via the Unified Compliance Framework (UCF). They generate *source document import tasks* to update or insert citations into the regulatory library. ## Alert Management and User Roles Alerts can be unassigned or assigned. Unassigned alerts can be updated, marked applicable or not applicable, deferred, or deleted by users with relevant roles. Marking alerts as applicable creates corresponding tasks automatically. Assigned alerts, which have a coordinator, progress through states like New, Deferred, Impact Assessment, In Progress, and Closed. User access is role-based: * **sngrcregchange.admin** and **sngrcregchange.manager** roles: Full access to all alerts. * **sngrcregchange.user** role: Can view and act only on alerts assigned to them. ## Alert Maintenance Alerts marked as not applicable require regular cleanup to maintain system performance. The application provides automated table cleaners scheduled by administrators (users with the **sngrcregchange.admin** role) to remove unnecessary alert records and processed registry files. ## Practical Actions and Enhancements * Users can assign alerts, initiate impact assessments, and mark alerts as applicable or not applicable to streamline compliance workflows. * The GRC: Predictive Intelligence application enables AI-driven citation recommendations on regulatory alerts, enhancing accuracy and efficiency by leveraging machine learning. Activating the Governance, Risk, and Compliance Predictive Intelligence plugin allows automated citation suggestions. * Both regulatory event alerts and source document alerts can be managed and assigned to appropriate users for timely action and compliance management. Regulatory alerts are an aggregation of different regulatory events and documents that are sourced from multiple regulatory intelligence providers. Similar to web feeds, a regulatory alert is a record of these regulatory changes. Such changes are frequently updated, and the alerts help you stay informed about the regulatory landscape. The Regulatory Change Management application transforms and maps the alerts. The application provides the information in regulatory alert tables. The Regulatory Change Management life cycle starts with the regulatory alert record. Each regulatory alert record contains metadata that helps stakeholders to translate the changes, create an action plan, and implement actions to comply with the regulatory changes. With the Regulatory Change Management application, you can use the regulatory alerts to inform the users about regulatory updates. ## Types of alerts and associated regulatory tasks {#regulatory-feeds__section_lds_dzm_hpb} Different types of alerts are displayed under the Regulatory Alerts module in the Regulatory Change Management application. You can use the following types of regulatory alerts: * Regulatory event alerts: Signify alerts, provide updates to news, and provide insights on regulatory changes. Alerts are by default regulatory event alerts. All RSS feeds result in a regulatory alert record. * Source document alerts: Signify changes to the citations. Citations are like various sections of an authority document. ServiceNow® GRC offers the Network Frontiers Unified Compliance Framework (UCF) integration. The integration creates authority documents after the import, and it creates corresponding citations under each authority document. When an existing citation is updated or a new citation is inserted, it signifies a change in the source document. Source document alerts are only available when integrating with a third-party regulatory intelligence provider; for example, Thomson Reuters. {#regulatory-feeds__ul_mds_dzm_hpb} The difference between a regulatory event alert and a source document alert is scope. Regulatory event alerts signify general alerts for general changes and for upcoming regulatory changes. In contrast, source document alerts signify changes that are specific to the citations. When an existing citation is updated or a new citation is inserted, it signifies a change in the source document. The different types of alerts each involve a separate set of regulatory tasks. These tasks are created whenever a user with the sn_grc_reg_change.user or sn_grc_reg_change.admin role takes an alert and then marks it as applicable. These tasks are the following: * Regulatory change task: This task is created for regulatory event alerts. The task is used to evaluate the changes and to update the GRC objects, such as policies, controls, and risk statements in the library. * Source document import task: This task is created for source document alerts. The task is used to update an existing citation or to insert a new citation that is received from the provider into the regulatory library. {#regulatory-feeds__ul_nds_dzm_hpb} ## Alerts and user roles {#regulatory-feeds__section_ibv_w3f_wmb} Alerts can have different states. The main property of an alert is whether it's assigned or unassigned. For assigned alerts, the Coordinator field has a value. An alert can be assigned either to a user with the sn_grc_reg_change.manager role or the sn_grc_reg_change.user or sn_grc_reg_change.admin role. In contrast, an unassigned alert isn't assigned to anyone. You can do various actions on unassigned alerts. These actions are the following: * Update * Applicable * Defer * Initiate Impact Assessment * Not Applicable * Cancel Regulatory Alert * Delete {#regulatory-feeds__ul_hd4_x2c_hpb} When an unassigned regulatory event alert is marked as applicable, a regulatory change task is created. When an unassigned source document alert is marked as applicable, a source document import task is created. When an unassigned alert is marked as not applicable with due comments, its state is updated as Closed in the regulatory alert form. Assigned alerts can have different states. These states are the following: * New * Deferred * Impact Assessment * In Progress * Closed {#regulatory-feeds__ul_dn3_51y_gpb} In terms of user roles, all alerts can be accessed by users with either the sn_grc_reg_change.admin role or the sn_grc_reg_change.manager role. Users with the sn_grc_reg_change.user role can view assigned alerts that are assigned to them, but they can't view unassigned alerts or alerts that are assigned to other people. ## Table cleaners for regulatory alerts {#regulatory-feeds__section_fx2_nck_bpb} The alert records that are marked as not applicable must be cleaned at regular intervals. The Regulatory Change Management application provides table cleaners for cleaning the alert records automatically. Users specify the time and frequency for the cleanup activity. Only users with the sn_grc_reg_change.admin role can perform cleanup activities. Similarly, registry file records that have been processed can be cleaned at specified time intervals. * **[Perform actions on regulatory alerts](https://www.servicenow.com/docs/x2rjVrAcuxXwdOSqycR4mQ)** Perform various actions on unassigned and other types of regulatory alerts. For example, you can assign an unassigned alert, initiate impact assessment on an alert, and mark an alert as applicable, among other actions. * **[Add an AI-recommended citation to a regulatory alert](https://www.servicenow.com/docs/8q1fu5fyVh9sdp87Hm8pXw)** Add an AI-recommended citation to a regulatory alert by using the GRC: Predictive Intelligence application. * **[Manage and assign regulatory event alerts](https://www.servicenow.com/docs/EMu3G45TEUJqUnaCl4re0w)** Assign regulatory event alerts that are received from the regulatory intelligence provider to an appropriate user. You can review other properties of the regulatory event alert. * **[Recommend citations on regulatory alerts](https://www.servicenow.com/docs/FfF6VvqEcBGvegQoBoakoA)** Train and use the machine learning solution by activating the Governance, Risk, and Compliance Predictive Intelligence plugin. The solution enables the system to automatically recommend correct citations on regulatory alerts to associate. * **[Manage and assign source document alerts](https://www.servicenow.com/docs/6YG092qs6r2Q_ahVzGqODg)** Assign source document alerts that are received from the regulatory intelligence provider to an appropriate user. You can review other properties of the source document alert.