---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Knowledge Flow

# Knowledge Flow {#ariaid-title1}

Release version: Brazil  
Updated September 10, 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 Knowledge Flow

Knowledge Flow in ServiceNow controls the publishing and retirement processes for knowledge articles through defined flows assigned to each Knowledge Base.
You can use default flows or create custom ones to manage different publishing and retirement scenarios, including approval requirements.
Show full answer Show less  

## Key Features

* **Flow Assignment:** Different flows can be assigned to each Knowledge Base to tailor publishing and retirement processes.
* **Approval Configuration:** Approval workflows can be customized by modifying the `getApprovers()` function in the `KBWorkflow` script include to specify who can approve or reject articles.
* **Email Notifications:** Notifications are sent to ownership groups or knowledge base managers for approval, and to authors or revisers upon approval or rejection. Approval notification emails can be enabled by setting the `glide.knowman.enableapprovalnotification` property to `true`. Only active users receive these notifications.
* **Parent-Child Article Relationship:** Articles and their translations have a parent-child relationship. Retiring a parent article does not automatically retire its translated child articles.

## Default Knowledge Flows

* **Knowledge - Approval Publish:** Requests manager approval before publishing. Articles move from Draft to In Review, then to Published or Scheduled for Publish upon approval. Rejection cancels the workflow and keeps the article in Draft.
* **Knowledge - Approval Retire:** Requests manager approval before retiring an article. Rejection cancels the workflow and retains the article in Published state.
* **Knowledge - Instant Publish:** Publishes draft articles immediately without approval or on a scheduled date.
* **Knowledge - Instant Retire:** Retires published articles immediately without approval.
* **Knowledge - Publish and Knowledge - Retire:** Actions that can be used to publish or retire knowledge articles manually.

## Key Outcomes

* Streamlined and customizable publishing and retirement processes aligned with organizational governance.
* Enhanced control over article lifecycle with approval workflows and notifications.
* Clear visibility and management of article states for administrators and knowledge managers.
* Ability for administrators and knowledge administrators to view and republish retired articles, ensuring content reuse and lifecycle management.  
The publishing and retirement processes for a knowledge article are controlled by flows defined for the Knowledge Base that the article belongs to.
You can assign different Flow processes to each Knowledge Base.

You can use one of the default flows, or create your own to define custom publishing and retirement processes for different types of knowledge.

For flows that require approval, you can configure which users can approve or reject by editing the getApprovers() function in the KBWorkflow script include.
{#r_KnowledgeFlow__table_eqc_lfl_1r__entry__2}

| Flow | Description |
|-|-|
| Knowledge - Approval Publish | Requests approval from a manager of the knowledge base. Articles in approval are In Review state before moving to Published state once approved or to Scheduled for publish if set to publish later. If the manager rejects the request, the workflow is canceled and the article remains in Draft state. If ownership groups is enabled, email notifications with a link to the article are sent to the ownership group members for approval. If ownership groups is not enabled, email notifications with a link to the article are sent to knowledge base managers for approval. A notification is also sent to authors or revisers of articles to inform them that their article has been approved or rejected. To turn on approval email notifications, set the glide.knowman.enable_approval_notification property to <kbd class="ph userinput">true</kbd>. Note: Only the active user receives the notifications. |
| Knowledge - Approval Retire | Requests approval from a manager of the knowledge base before moving the article to the retired state. The workflow is canceled and the article remains in the published state if any manager rejects the request. If ownership groups is enabled, email notifications with a link to the article are sent to the ownership group members for approval. If ownership groups is not enabled, email notifications with a link to the article are sent to knowledge base managers for approval. |
| Knowledge - Instant Publish | Immediately publishes a draft article without requiring an approval, or publishes on the scheduled publish date if set to publish later. |
| Knowledge - Instant Retire | Immediately retires a published article without requiring an approval. |
| Knowledge - Publish Knowledge | Action that can be used to publish the knowledge article. |
| Knowledge - Retire Knowledge | Action that can be used to retire the knowledge article. |
[Table 1. Default knowledge flow]

{#r_KnowledgeFlow__table_eqc_lfl_1r}  
Note:  
* Only administrators and knowledge administrators can view the retired knowledge articles. To reuse a retired article, administrators and knowledge administrators can republish the article. For more information, see [Republish a retired article](https://www.servicenow.com/docs/oWjxBwoR0rjcXNWxWaeDMg "Instantly republish a retired article.").
* An article and its translations have a parent-child relationship. Retiring a parent article does not automatically retire all its translated child articles.
{#r_KnowledgeFlow__ul_q3j_chc_mmb}