---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Assign a source document alert to a coordinator

# Assign a source document alert to a coordinator {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Log in to the GRC: Regulatory Change Management application, review the
source document alert, and assign it to a coordinator. The coordinator then assesses the
applicability of the alert and completes the associated regulatory tasks.

## Antes de Iniciar

Roles required: sn_grc_reg_change.manager, sn_grc_reg_change.user

## Por Que e Quando Desempenhar Esta Tarefa

As a manager, you can view and assign the source document alerts to users with the
sn_grc_reg_change.user role. The user can then perform actions on the source
document alerts.

## Procedimento

1. Log in with the sn_grc_reg_change.manager user role.
2. Navigate to AllRegulatory Change ManagementCompliance Workspace.  
   The Regulatory Change Management application in the Compliance Workspace is displayed.
3. Navigate to ListsAssigned Regulatory Alerts view.
4. Select a source document type alert in the list.
5. In the Details tab, fill in the form.  
   {#manage-source-document-alerts-using-ws__table_rkr_v1y_fnb__entry__2}

   | Fields | Description |
   |-|-|
   | Title | Title of the source document type of alert as received from the provider. This field is automatically set to display the title. |
   | Citation | Citation number for the source document that is received from the provider. This field is automatically set to display the citation. |
   | Provider URL | URL of the alert provider. This field is automatically set to display the provider URL. |
   | Regulatory body URL | URL of the regulatory body that is associated with the alert. This field is automatically set to display the regulatory body URL. |
   | Provider | Name of the alert provider. This field is automatically set to display the name of the provider. |
   | Type | Type of the regulatory alert. For example, source document alert. This field is automatically set to display the type of the alert. |
   | Coordinator | User that the alert is assigned to. |
   | Dates ||
   | Source publication date | Date when an alert is published by the regulatory body. Auto-populated field. This field is automatically set to display the source publication date. |
   | Comments date | Date until when the comments can be provided for the alert. Auto-populated field. This field is automatically set to display the comments date. |
   | Effective date | Date when the alert is going to be applicable. This field is automatically set to display the effective date. |
   | Compliance date | Date by which the alert is going to be compliant. This field is automatically set to display the compliance date. |
   | Expiration date | Expiry date for the alert. This field is automatically set to display the expiration date. |
   | Activity Journal ||
   | Additional comments | Additional comments related to the alert. |
   | Compose ||
   | Additional comments | Additional comments related to the alert that are added in the Compose section. |
   | Log of the activities | Log of the activities related to the alert. Displays the system generated changes and additional comments. |
   | Highlighted details ||
   | Taxonomy | Taxonomy details associated with the alert. This field is automatically set to display the taxonomy details of the alert. |
   [Tabela 1. Details tab in the Source Document alert form]

   {#manage-source-document-alerts-using-ws__table_rkr_v1y_fnb}
6. In the Coordinator field, assign it to a user with the sn_grc_reg_change.user user role.
7. Log in with the sn_grc_reg_change.manager role, open the selected source document alert, and mark the alert using one of the following options.

   | Field | Description |
   | Applicable | Marks the alert as applicable. |
   | Not applicable | Marks the alert as not applicable. Select one of the following reasons and select Submit: * No action required on the alert * Duplicate alert * Other {#manage-source-document-alerts-using-ws__ul_ay1_l4n_brb}As a result of this action, the stepper component in the alert page displays the stage as Completed. |
   | Cancel regulatory alert | Cancel the regulatory alert. |
   | Defer | Defer the alert to a later date. |
   |-|-|

   {#manage-source-document-alerts-using-ws__choicetable_utb_d4n_brb}
{#manage-source-document-alerts-using-ws__steps_qqh_2vs_cqb}

## Resultado

After marking the source document alert as Applicable, a new source document import task is created under the Import document tasks related list.