---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Reference

# Reference section for Incident Management {#ariaid-title1}

Release version: Australia  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Reference sections provide additional information about components installed with Incident Management.
For information about incident routing and feedback, see the [Exploring Incident Management](https://servicenow-prod.fluidtopics.net/gOGriNfy1XkJZHpMD4d6fw "ServiceNow Incident Management supports the incident management process with the ability to identify and log incidents, classify and prioritize incidents, assign incidents to appropriate users or groups, escalate, resolve, and report incidents.").

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://servicenow-prod.fluidtopics.net/WPGAhCXLDF9cabY3WxrXHA "Provide a resolution for an issue by creating a knowledge article from an incident with fields defined in an article template.").
* **[Domain separation and Incident Management](https://servicenow-prod.fluidtopics.net/XJp0iWTZ3lgGOfb939S_EQ)**   
  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://servicenow-prod.fluidtopics.net/Zs1mOSVHKC76KrMnCTT38w)**   
  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://servicenow-prod.fluidtopics.net/BlugV4qKpdpHptFE~NF74Q)**   
  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://servicenow-prod.fluidtopics.net/CconLApP7NUcWzVlEIbz5Q)**   
  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://servicenow-prod.fluidtopics.net/y1rBWXS9odY~gUjyZ0jrww)**   
  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.