--- 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 --- # Managing issues from Business Continuity Workspace # Managing issues from Business Continuity Workspace {#ariaid-title1} Release version: Australia Updated August 17, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Managing issues from Business Continuity Workspace This feature in ServiceNow's Business Continuity Workspace allows you to associate and manage issues directly linked to business continuity plans, recovery events, and exercises. It helps track problems identified during continuity planning and crisis events through to resolution, enhancing organizational resilience and minimizing operational disruption. Show full answer Show less ## Key Features * **Issue Association:** Create or add existing Governance, Risk, and Compliance (GRC) issues from the Issues related list on plan, event, or exercise records to track and manage them within business continuity processes. * **Classification and Source Tracking:** Issues created from plans are classified under Business Continuity Management, with the originating plan recorded as the primary source and other linked plans/events as secondary sources. * **Role-Based Access Control:** Access to create, view, or modify issues depends on roles such as plan contributor, manager, and viewer, integrated with GRC: Profiles roles to ensure appropriate permissions. * **Issue Visibility:** From an issue record, view all linked plans, events, and exercises under Impacted Items tabs or related lists, depending on installed applications, to track all associated continuity activities. * **Vertical Page Layout:** BCM Administrators can enable a vertical layout for better organization and visibility of related records, improving navigation and data access within the workspace. * **Dependencies:** Requires installation of GRC: Profiles, GRC: Issue Management, and GRC: Advanced Core applications for full issue management integration with BCM. ## Practical Benefits By integrating issue management into business continuity planning and crisis management, organizations can: * Track and prioritize issues efficiently throughout their lifecycle to reduce resolution time. * Leverage AI-powered insights to identify root causes and strengthen resilience planning. * Maintain critical operations and reduce downtime by proactively addressing issues identified during planning, events, and exercises. ## Usage Considerations * Issues can only be added or created when plans, events, or exercises are in editable states (not archived). * Removing an issue from a related list only removes the association and does not delete the issue record itself. * Access to issues aligns with plan and event permissions, ensuring secure and role-appropriate management. ## Next Steps To implement and use issue management in Business Continuity Workspace effectively, ensure prerequisite GRC applications are installed and configured. Use the Issues related list on plan or event records to create or associate issues, monitor their status, and maintain clear traceability between issues and continuity activities. Associate issues with business continuity plans to track problems identified during continuity planning. Create or add an existing issue from the Issues related list on a plan record. ## Business continuity with issue management {#managing-issues-in-bcm__section_h45_yhr_3kc} Prerequisites : The GRC: Profiles application must be installed as a prerequisite for issue management. For more information, see [Issues module integration dependencies with BCM](https://www.servicenow.com/docs/T18Co3g01swDC1Aa6YAuJg "The following GRC applications are required for Issues integration with BCM."). Benefits : The GRC: Issue Management integration enables organizations to track, prioritize, and resolve issues throughout their life cycle, reducing resolution time and minimizing business impact. AI-powered insights accelerate root cause identification, strengthen resilience planning, and support data-driven decisions to prevent future disruptions. This maintains critical operations and reduces downtime. Usage : Associate issues with business continuity plans and events to track problems identified during planning, exercises, and crisis events. Use the Issues related list in plan and event records to create an issue or add an existing GRC issue and track it through resolution. ## Dependencies {#managing-issues-in-bcm__dependencies} Certain GRC applications are required for issue integration with BCM: * GRC: Profiles, which provides issues and remediation * GRC: Issue Management * GRC: Advanced Core, which provides issue triage {#managing-issues-in-bcm__ul_hzm_x4v_3kc}The Issues related list appears when BCM and these GRC applications are installed. For more information, see [Issues module integration dependencies with BCM](https://www.servicenow.com/docs/T18Co3g01swDC1Aa6YAuJg "The following GRC applications are required for Issues integration with BCM."). ## Classification and source {#managing-issues-in-bcm__classification_source} When you create an issue from a plan, the issue is given the Business continuity management classification. The issue source and issue source reference are set to the plan that you created it from, the primary source of the issue. When you add an existing issue to another plan, that plan is recorded as a secondary source of the issue. ## Relationship between an issue and a plan {#managing-issues-in-bcm__relationship_behavior} The relationship between an issue and a plan is stored in a many-to-many table sn_bcp_m2m_plan_issue (Plan related issues) that brings the issue fields into the related list. Removing an issue from the related list removes the association. It does not delete the issue record. ## Access {#managing-issues-in-bcm__access} Adding or creating an issue requires write access to the plan, the same as for recovery tasks and loss scenarios. The list of issues that you can add shows the active issues that you have access to. You can't add or create an issue when the plan, recovery event, or exercise is in a state that doesn't allow edits, such as Archived. Issue access by role is described in the following table and the following illustrations. {#managing-issues-in-bcm__table_issue_access_roles__entry__2} | Role | Access to issues | |-|-| | sn_bcp.plan_contributor | Read, write, and create | | sn_bcp.plan_manager | Read, write, and create | | sn_bcp.plan_viewer | Read only | | sn_recovery.event_manager, sn_recovery.event_user | Read, write, and create | | sn_bcm.program_manager | Read, write, and create | [Table 1. Issue access by role] {#managing-issues-in-bcm__table_issue_access_roles} Note: When GRC: Profiles is installed, all roles in this table contain the sn_grc.compliance_assurance_user role, except sn_bcp.plan_viewer, which contains the sn_grc.compliance_assurance_reader role. The role records show the contained roles for each role. The sn_grc.compliance_assurance_user role or sn_grc.compliance_assurance_reader role appear only when GRC: Profiles is installed. ## Issues on crisis events and exercises {#managing-issues-in-bcm__issues_on_events} Recovery events and exercises support the same issue association as continuity plans. From an event or exercise record, use the Issues related list to create an issue or add an existing issue. The issue is given the same classification and source reference behavior as an issue created from a plan. ## Viewing plans and events from the issue record {#managing-issues-in-bcm__viewing_from_issue_record} The issue record shows every plan, recovery event, or exercise linked to it as a related item. Where these appear depends on which applications are installed. When the Issue Management app is installed, plans, crisis events, and exercises each appear as a separate tab under Impacted items, with Add and Remove actions. The Plans, Crisis events, and Exercises tabs are independent --- linking a record to one tab does not affect the others. When only GRC: Profiles is installed, the plan, event, and exercise related lists appear directly on the classic issue form, also with Add and Remove only. The first plan or event that an issue is created from is set to its primary source. Every other plan or event you link afterward is recorded as a secondary source. Removing a plan or event from the issue record's related list removes only the association. The plan, event, and issue records aren't affected. ## Vertical page layout {#managing-issues-in-bcm__section_tjz_s1k_2kc} BCM Administrators can group and arrange related lists in a vertical layout. It enables you to access connected data without scrolling through a traditional horizontal page layout. The Record page vertical template (sn-rec-pg-vertical) and GRC: Issue Management applications are the core components for the enhanced layout. The Impacted Items section now groups related items for improved visibility and easier identification of affected items. The "Record page vertical template" application is installed with GRC Base Workspace (app-grc-base-workspace). It manages related lists and UI pages on a record page within groups. Its template uses preset values that enable the page to work without complex configuration. It also controls how related information is organized and displayed when you view records in Business Continuity Workspace as shown in the example. **Related concepts** * [Issue modules in Business Continuity Workspace](https://www.servicenow.com/docs/Lon8pY9x9bGcZTNJ3iyoww "Browse and create issues from dedicated modules in the List view of the Business Continuity Workspace without opening a plan, crisis event, or exercise.") **Related tasks** * [Add or create an issue from a plan](https://www.servicenow.com/docs/O79oDZA83JLqHnNnMU3ASA "Add an existing issue or create an issue from a business continuity plan to track problems identified during continuity planning.") * [Add or create an issue from an exercise](https://www.servicenow.com/docs/UDqNeKjC3RshtN2Nof_9Ag "Add an existing issue or create a new issue to track problems identified during an exercise.") **Related reference** * [Issues module integration dependencies with BCM](https://www.servicenow.com/docs/T18Co3g01swDC1Aa6YAuJg "The following GRC applications are required for Issues integration with BCM.")