--- 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 --- # Creating collaboration threads in exercises and crisis events # Creating collaborations in exercises and crisis events {#ariaid-title1} Release version: Australia Updated August 17, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Creating collaborations in exercises and crisis events Starting with BCM core release 12.x.x, ServiceNow enables crisis managers to create collaboration threads on crisis events to streamline coordination with recovery teams. These threads consolidate recovery teams, impacted assets, and email communications related to a specific crisis event, replacing disparate emails and spreadsheets with a centralized record of decisions, actions, and communications. Show full answer Show less ## Key Features * **Collaboration Threads:** Each thread is linked to exactly one crisis event and cannot be deleted independently; it is closed by setting its State field to "Closed". Threads appear in the Collaboration threads related list on the crisis event record and display key details such as Number, Name, Recovery teams, Impacted assets, Updated date, and State (Open or Closed). * **Action Items and Tracking:** Within a thread, the Action items tab tracks follow-up tasks with assigned ownership and status, facilitating clear task management during crisis coordination. * **Email Integration:** The Emails tab lists all emails sent from the thread, while the Email Attachments tab contains related files. These tabs are read-only and automatically update upon sending emails through the thread. * **Automated Notifications:** Creating or saving a collaboration thread triggers an automatic notification email to all recovery team members, linking them directly to the new thread. This system-generated email is distinct from any subsequent emails composed manually within the thread. * **Activity Feed Integration:** All field changes, emails, and attachments on collaboration threads are propagated to the parent crisis event's activity feed, ensuring real-time updates and a comprehensive audit trail for post-event review and compliance. * **Role-Based Access:** Users with the *snrecovery.eventmanager* or *snrecovery.eventuser* roles can create and update collaboration threads, including changing states and adding work notes. Users with the *snrecovery.eventviewer* role have read-only access to threads and work notes. ## Practical Application for ServiceNow Customers This functionality empowers crisis managers to efficiently coordinate response efforts by centralizing communication and task management in one place, enhancing visibility and accountability. Automated notifications and audit trails support timely responses and thorough post-event analysis. Customers can expect improved collaboration among recovery teams during exercises and real crisis events, reducing reliance on fragmented communication tools and improving compliance documentation. Starting with BCM core release 12.x.x, crisis managers can create collaboration threads on crisis events to coordinate responses with recovery teams and send email updates. ## Collaboration threads overview {#creating-collaboration-threads-in-crisis__section_collab_thread_overview} A collaboration thread groups the recovery teams, impacted assets, and email communication for a specific coordination effort on a crisis event. Each collaboration thread belongs to exactly one crisis event and is deleted if that crisis event is deleted. A collaboration thread cannot be deleted on its own; set its State field to close it instead. Collaborations details are displayed in the Collaboration threads related list on the crisis event record, as shown in the example. A collaboration thread includes the following details in columns: * Number * Name * Recovery teams * Impacted assets * Updated * State with a value of Open or Closed {#creating-collaboration-threads-in-crisis__ul_collab_thread_fields}For descriptions of these fields, see [Create Collaboration thread form](https://www.servicenow.com/docs/EGVKEsY2aA_rEmXMW5K26Q "Use the Create collaboration thread form in the BCM Configurable Workspace to enable team members to communicate and coordinate responses during an exercise or a crisis event."). Collaboration threads centralize crisis response coordination, replacing scattered emails and spreadsheets with a single record of decisions, actions, and communications. Automatic recovery-team notifications and activity-stream propagation keep responders informed in real time and preserve a complete audit trail for post-event analysis and compliance reporting. ## Action items, emails, attachments, and activity on a collaboration thread {#creating-collaboration-threads-in-crisis__section_collab_thread_activity} A collaboration thread record groups its related information under the Action items, Emails, and Email Attachments tabs, as shown in the example. Use the Action items tab to track follow-up tasks assigned during the coordination effort, with ownership and status for each item. On the Emails tab, the emails sent from a collaboration thread are listed. Files attached to it are listed in its Email Attachments tab. Both tabs are read-only: an email appears in the Emails tab only after it is sent from the thread, and you can't add or remove entries directly in either tab. Saving a collaboration thread sends an automatic notification email to the members of the recovery teams selected on the thread. The email notifies them that a new thread was opened and links back to it. This system-generated email is separate from any email you send afterward with Compose email, and it also appears in the Emails tab. Field changes, emails, and attachments on a collaboration thread are added to its parent crisis event's activity feed for review, as shown in the example. ## Roles associated with collaboration threads {#creating-collaboration-threads-in-crisis__section_collab_thread_roles} Users with the sn_recovery.event_manager or sn_recovery.event_user role can create and update collaboration threads, including their State and work notes. Users with the sn_recovery.event_viewer role can read collaboration threads, including their work notes. * **[Create a collaboration thread in a crisis event](https://www.servicenow.com/docs/XfH65tn3_Q~jURhGmcm8uw)** Create a collaboration thread on a crisis event and send an email to its recovery teams to coordinate a response.