--- title: Assigning knowledge workflows to an OT knowledge base description: You can assign different Knowledge Management workflows to each Operational Technology \(OT\) knowledge base for the publishing and retiring processes. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/operational-technology/operational-technology-knowledge-management/assigning-knowledge-workflows-to-ot-knowledge-base.html release: australia product: Operational Technology Knowledge Management classification: operational-technology-knowledge-management topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Configure, Operational Technology Knowledge Management, Operational Technology] --- # Assigning knowledge workflows to an OT knowledge base You can assign different Knowledge Management workflows to each Operational Technology \(OT\) knowledge base for the publishing and retiring processes. ## Knowledge workflow overview You can use the default Knowledge Management workflows in the following table for Operational Technology Knowledge Management and apply them to OT knowledge bases. **Note:** For the workflows that require approval, you can configure which users can approve or reject by editing the `getApprovers()` function in the `KBWorkflow` script include.
| Workflow | Description |
|---|---|
| Knowledge - Approval Publish | Requests approval from a manager of the knowledge base. Articles in approval have a state of **In Review** before moving to a **Published** state after approval. If they're set to publish later, they’re moved to a **Scheduled** state. If the manager rejects the request, the workflow is canceled and the article remains in the **Draft** state. If the**ownership groups** option is enabled, email notifications with a link to the article are sent to the ownership group members for approval. If the **ownership groups** option isn't enabled, email notifications with a link to the article are sent to the knowledge base managers for approval. A notification is also sent to the authors or the revisers of the articles to inform them that their article has been approved or rejected. To turn on the approval email notifications, set the **glide.knowman.enable\_approval\_notification** property to `true`. **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. If any manager rejects the request, the workflow is canceled and the article remains in the **Published** state.If the **ownership groups** option is enabled, email notifications with a link to the article are sent to the ownership group members for approval. If the **ownership groups** option isn’t enabled, email notifications with a link to the article are sent to the 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 | Subflow that moves the knowledge article to the **Published** state. You can use this subflow when defining your own workflow. |
| Knowledge - Retire Knowledge | Subflow that moves the knowledge article to the **Retired** state. You can use this subflow when defining your own workflow. |