--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Tag categorization # Tag Categorization in Tag Governance {#ariaid-title1} Release version: Australia Updated March 12, 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 Tag Categorization in Tag Governance Tag Categorization in Tag Governance automatically groups similar tag keys into predefined categories, simplifying the management of configuration items (CIs) and cloud resources. This feature promotes consistent tagging practices by categorizing tags daily and mapping unrecognized tag keys to appropriate categories, improving tag accuracy and governance. Show full answer Show less ## Key Features * **Predefined and Custom Categories:** Comes with preconfigured tag categories which you can modify or extend by creating new categories or adding tag keys to fit your organization's needs. * **Automated Recategorization:** A scheduled daily job categorizes new tags and updates mappings when category changes occur. Changes are tracked via the `snitomtag.recategorizationrequired` property and applied within 24 hours, with the option for immediate recategorization. * **Compliance Monitoring:** The Tag category policy identifies CIs missing category mappings and marks them as non-compliant, enabling proactive remediation. * **Domain Separation Support:** Supports domain-specific tag management. In domain-separated instances, categories are managed within each leaf domain; in non-domain-separated instances, categories reside in the global domain. ## Requirements and Considerations Full functionality requires Service Mapping Plus version 1.16.3 or later, as Tag Categorization relies on the `svctagcategories` and `svctagnames` tables from Service Mapping. Without this, access to key tables and features like recategorization and tag definition modifications may be limited. ## Practical Benefits for ServiceNow Customers * Ensures consistent and clear tagging of CIs and cloud resources, enhancing asset visibility and governance. * Automates tag grouping and compliance checks, reducing manual effort and errors. * Supports organizational structure through domain separation, enabling tailored tag governance across business units. * Allows flexibility to customize tag categories, helping align tag management with your specific operational requirements. By automatically grouping similar tag keys into predefined categories, Tag Categorization streamlines the management of configuration items (CIs) and cloud resources while promoting clear and consistent tagging practices. ## Tag categorization requirements {#tag-categorization-tag-governance__section_nfn_lrp_tfc} Note: The Tag Categorization feature in Tag Governance leverages the CI tag category \[svc_tag_categories\] and the CI tag key \[svc_tag_names\] tables in Service Mapping. Full access to these tables requires installation of the version 1.16.3 or later of Service Mapping Plus. Without it, access to these tables might be limited, affecting your ability to recategorize tags, modify tag definitions, or fully use the feature. For more information, see [Install Service Mapping Plus](https://www.servicenow.com/docs/oSi~VdXdAwSs0c1Qu8XIiw "You can install the Service Mapping Plus application (sn_sm_scoped_app) if you have the admin role. The application installs related ServiceNow Store applications and plugins if they are not already installed."). ## Tag Categorization overview {#tag-categorization-tag-governance__section_hyc_yrp_tfc} Tag Categorization helps streamline and improve the accuracy of tag management by providing preconfigured categories to help you group tags for your CIs. A daily scheduled job categorizes newly added tags and maps any unrecognized tag keys to the appropriate category. For more information about the predefined tag categories, see [Components installed with Tag Governance](https://www.servicenow.com/docs/8KrKfxD_IxExkkv81clOng "Several key components are installed with, or linked to, the Tag Governance plugin to help standardize and manage your organization's tags."). You can modify the tag category definitions, create your own categories, or add additional tag keys as needed. For more information, see [Modify tag category information for Tag Categorization](https://www.servicenow.com/docs/ERpKGnem59rxMThyKpK8Aw "Modify tag category definitions to support Tag Categorization and ensure that tag categories align with your requirements for data management and classification."). The Tag category policy confirms that all categories are properly mapped and up-to-date. It retrieves records and checks for category mappings to identify any missing categories. CIs that are missing a category are marked as non-compliant, which helps you address and remediate any tag category issues. The system uses the sn_itom_tag.recategorization_required property to determine whether recategorization is needed. By default, this property is set to false. When a change to a category occurs, a business rule sets the property to true, indicating that recategorization is needed. A daily scheduled job then checks this property and if it is set to true, begins the recategorization process. This process automatically updates the tag mappings within 24 hours of the change, but you can also initiate recategorization to apply the changes immediately. All changes and updates are stored in the CI tag category table. ## Tag Categorization and domain separation {#tag-categorization-tag-governance__section_xc1_yjq_tfc} Tag Categorization supports domain-specific management. If an instance isn't domain-separated, the categories are added to the global domain. For domain-separated instances, the categories are added to each leaf domain. When you access or manage tags, the system gets domain information from the CI and adds tag mappings to the matching category in the appropriate domain. For general information about domain separation with Tag Governance, see [Domain separation and Tag Governance](https://www.servicenow.com/docs/ebLgQl~nXCGRdHiZRsxC1g "Domain separation is supported in Tag Governance. 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.").