--- title: Page title test description: A visual overview of the HubSpot Knowledge setup for sharing product updates across MCB teams and customers. --- [Skip to main content](https://activecampaignday.com/page-title-testefqwefgqewg4qg3bvqrvq#main-content) MCB HubSpot Team Knowledge sharing setup for HubSpot product updates HubSpot Product Updates to Knowledge # A shared knowledge engine for MCB teams and customers. The first draft centers on exciting HubSpot product updates. An employee saves the update once, then HubSpot workflows and agents prepare the right drafts for internal teams and external customer communication. Source 1 record Outputs 3 drafts Control 2 reviews 01 **Product update** 02 **Knowledge record** 03 **Agent drafts** 04 **Human approval** End-to-end flow ## From update discovery to approved communication. The system keeps automation fast while preserving employee review before anything is published or sent. 01 ### Find the update An MCB employee reviews HubSpot product updates and picks an update worth sharing. 02 ### Create Knowledge record The employee adds the product update to the custom object Knowledge in HubSpot. 03 ### Choose the routes The record captures which hubs, teams, and content channels should receive attention. 04 ### Agents draft content Workflows and agents prepare blog, LinkedIn, and Slack drafts from the submitted update. 05 ### Review blog task A HubSpot task sends the employee to review, adjust, and publish the draft blog post. 06 ### Approve Slack message The employee reviews the internal Slack draft and approves sending to selected channels. HubSpot custom object ## The Knowledge record becomes the single source for the setup. The employee makes the editorial decisions at record creation: which product update it is, who it matters to, and which channels should receive a draft. Mandatory input 1 ### Name of the product update Mandatory input 2 ### Product update description copied from HubSpot Mandatory input 3 ### Hubs where the update is available Mandatory input 4 ### Create LinkedIn post in draft Mandatory input 5 ### Create blog post Mandatory input 6 ### Create internal Slack message Mandatory input 7 ### MCB teams that may be interested Agent output ## Drafts are created automatically, approvals stay human. The workflow can create only the requested assets. Every draft remains reviewable before customers or internal teams see it. ### Blog post Draft for customer-facing knowledge sharing. ### LinkedIn post Draft for external reach and update awareness. ### Slack message Draft for selected internal MCB channels. Blog review task ### Assigned to the employee in HubSpot The employee reviews the draft blog post, makes changes if needed, and then publishes the article. Slack approval ### Reviewed before channel delivery The internal message can be rewritten, then approved for the specific Slack channels tied to interested MCB teams. Audience route ### Internal HubSpot team Audience route ### Sales and account teams Audience route ### Customer-facing consultants Audience route ### MCB customers interested in HubSpot Sharing model ## One update can travel internally, externally, or both. MCB keeps the product update in HubSpot as reusable knowledge, then routes the resulting content to the teams and customers most likely to benefit from it.