{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":18100,"path":"governance-risk-compliance/recovery-team-collaboration.md","title":"Global recovery teams and collaboration threads","bundle":null,"doc_type":null,"release":"australia","body":"\n# Global recovery teams and collaboration threads\n\nRecovery teams and collaboration help organizations coordinate business continuity responses using reusable teams and integrated communication.\n\n## Recovery team management\n\nRecovery teams are supported at global level and they are available across all BCM applications. BCM users can create and store recovery teams to address defined problems and fulfill organizational requirements. Key features include an active flag for recovery teams, support for global recovery teams, ability to reference saved recovery teams within plans, and enhanced recovery team hierarchy management.\n\n## Recovery teams module in Business Continuity Workspace\n\nBCM administrators can create and manage recovery teams from the Recovery teams module in Business Continuity Workspace.\n\n\\[Omitted image \"recovery-teams-module.png\"\\] Alt text: Recovery teams module.\n\n## Benefits of using recovery teams\n\nRecovery teams and collaboration provide the following benefits:\n\n|Benefit|Details|\n|-------|-------|\n|Centralized tracking|Eliminates scattered Excel spreadsheets and fragmented communication. All event-related collaborations, decisions, and actions are captured in a single platform.|\n|Reusability|Recovery teams are created once and can be associated with multiple recovery plans and events, reducing administrative overhead and ensuring consistent team definitions across the organization.|\n|Hierarchical organization|Parent-child team relationships enable modeling of complex organizational structures \\(site-level, country-level, global teams\\) with automatic cycle prevention.|\n|Audit trail|Built-in activity streams and historical records capture all decisions, actions, and communications for compliance requirements and post-event analysis.|\n|Real-time coordination|Integrated collaboration threads, email capabilities, and action tracking keep all team members aligned during crisis events without context switching to external tools.|\n|Automatic recipient resolution|Email notifications automatically resolve team membership including nested groups, eliminating manual recipient management during urgent situations.|\n\n## Capabilities and use cases\n\nThe BCM recovery team and collaboration functionality provides key capabilities for coordinating business continuity responses.\n\n|Capability|Description|Use case|\n|----------|-----------|--------|\n|Team management|Create reusable recovery teams with hierarchical structures, configurable membership, location association, and lifecycle management|Site Evacuation Team reports to Regional Safety Team, which reports to Global Recovery Coordination Team|\n|Collaboration threads|Capture discussions, decisions, coordination, action items, and email communications with timeline and attachments|Fire incident: Evacuation Team documents decisions, Safety Team reports status, Facilities Team assigns restoration tasks|\n|Crisis event coordination|Automatically notify recovery team leads with context about impacted assets and recovery objectives|Crisis declared: team members receive notifications enabling immediate action without manual coordination|\n|Escalation and routing|Tag events with crisis levels and automatically resolve team recipients including nested group members|High crisis level signals executive teams; system resolves all recipients eliminating manual email management|\n|Multi-team coordination|Parent-child team hierarchies enable coordination between specialized teams with organizational oversight|Data Recovery team reports to Infrastructure Recovery team; Site Evacuation to Regional Safety to Global Recovery|\n|Exercise and planning|Participate in exercises and tabletop discussions with automatic capture of decisions and actions|Recovery teams join exercises; all decisions captured for improvement tracking without manual spreadsheet updates|\n|Plan development|Select pre-configured teams from global repository ensuring consistent definitions across all plans|Administrators reuse teams across plans; updates to team definitions benefit all referencing plans and events|\n|Post-event analysis|Complete collaboration thread serves as authoritative record capturing all activity, decisions, and actions|Resolved events provide comprehensive audit trail for post-event reviews, compliance, and improvement planning|\n\n## Components used in recovery teams\n\nThe global recovery team consists of the following components:\n\n|Component|Description|\n|---------|-----------|\n|Tables|\n|sn\\_bcm\\_recovery\\_team|Core table storing recovery team records with fields for name, description, location, and active status|\n|sn\\_bcm\\_m2m\\_recovery\\_team\\_user|Junction table linking users to recovery teams with automatic department mapping for picker filters|\n|sn\\_bcm\\_m2m\\_recovery\\_team\\_group|Junction table linking groups to recovery teams, supporting recursive group membership resolution|\n|sn\\_bcm\\_m2m\\_recovery\\_team\\_recovery\\_team|Self-join hierarchy table supporting parent-child team relationships with automatic cyclic-relationship prevention|\n|sn\\_bcp\\_m2m\\_plan\\_recovery\\_team|Junction table linking recovery teams to recovery plans|\n|Access control|\n|core\\_viewer|Read and report-view access to recovery team records|\n|core\\_manager|Create, write, delete, and management permissions for recovery teams. These roles extend to all related records including collaboration threads and email communications.|\n|Rules|\n|Business rules|Validate parent-child relationships and prevent invalid team hierarchies. The system prevents cyclic relationships and self-loops automatically, maintaining data integrity during team configuration.|\n\n## Key capabilities\n\nRecovery teams and collaboration provide the following key capabilities:\n\n-   Team management and planning\n    -   Create reusable teams with hierarchical structures and configurable membership\n    -   Reference teams across multiple recovery plans with automatic filtering of active teams\n-   Collaboration and communication\n    -   Coordinate through integrated threads with automated email notifications and recipient resolution\n    -   Track activity streams, delivery status, attachments, and role-based work notes\n-   Event escalation and tracking\n    -   Tag events with crisis levels to indicate severity and control access\n    -   Maintain persistent escalation values across all event views\n-   Documentation and reporting\n    -   Export complete recovery timeline to Word and PDF with collaboration threads and event details\n    -   Automatically propagate email history and activity updates to parent crisis event feed\n\n**Related topics**  \n\n\n[Create and manage a recovery team](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/create-recovery-team.md)\n\n[List view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/list-view-uib-ws.md)\n\n[Recovery teams, loss scenarios, and recovery tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/recovery-teams.md)\n\n[Creating collaborations in exercises and crisis events](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/creating-collaboration-threads-in-crisis.md)\n\n[Create a collaboration thread in a crisis event](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/compose-email-collaboration-thread-crisis.md)\n\n[Create Collaboration thread form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/create-collaboration-thread-crisis-event-form.md)\n\n"}}