---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Routing policy details

# Routing policy details {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Routing policies are essential for automated certificate management in TLS certificates as they define specific criteria, such as CA and environment, enabling efficient handling of different scenarios during the certificate
lifecycle.  
There are three different scenarios for how routing policies work for automated certificate management for TLS certificates.

* Scenario 1: A single routing policy matches and manual approval is required. The approver can verify the task details and approve the certificate request. Once approved, this triggers the automated flow.
* Scenario 2: No routing policy matches OR there are multiple routing policies that match. The approver can verify the task details and select Choose Routing Policy \& Approve. The approver needs to manually select the routing policy. The updated routing policy then displays. The approver selects the routing policy which then triggers the automated flow.
* Scenario 3: A single routing policy matches, manual approval is not required, and Approval Required flag is inactive. This triggers the automatic flow.
{#how-routing-policy-works__ul_e3b_djf_4qb}  
Hinweis:  
If the approver has rejected the certificate request task, the task is marked as Failed. A single approval is enough for triggering the automated flow progress.