--- title: Reference section for Incident Management description: Reference sections provide additional information about components installed with Incident Management. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/incident-management/reference-section-for-incident-management.html release: australia product: Incident Management classification: incident-management topic_type: reference last_updated: "2025-01-30" reading_time_minutes: 1 breadcrumb: [Incident Management, IT Service Management] --- # Reference section for Incident Management Reference sections provide additional information about components installed with Incident Management. For information about incident routing and feedback, see the [Exploring Incident Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/incident-management-process.md). To track the KB articles that were used to resolve incidents, use the Knowledge related list on the Incident form. For more information, see [Create a knowledge article from an incident using an article template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/create-a-knowledge-article.md). - **[Domain separation and Incident Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/domain-separation-incident-management.md)** Domain separation is supported in Incident Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data. - **[Incident Management data model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/incident-mangmt-data-model.md)** Learn about the Incident Management application by viewing the data model diagram. This diagram shows the relationships between the tables within the application and provides an overall picture of how the Incident Management application operates. - **[Incident Management plugins](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/incident-mgmt-plugins.md)** Many of the Incident Management plugins are activated in the base system. Others, you can activate when you are ready to use them. Some plugins include demo data. - **[Features of enhanced security model adoption for incident tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/comp-instal-itsm-enhanced-sec-features.md)** Help prevent unauthorized access to incident-related tables using Deny-Unless ACLs. A Deny-Unless authentication ACL restricts access for a non-authenticated user. - **[Incident Management integrations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/inci-mgmt-integrations.md)** Users of an incident management solution need to have access to a multitude of features so that they can address specific challenges directly. Incident Management integrations aims to fully integrate and automate your incident response system. **Parent Topic:**[Incident Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/incident-management/c_IncidentManagement.md)