> ## Documentation Index > Fetch the complete documentation index at: https://docs.introw.io/llms.txt > Use this file to discover all available pages before exploring further. # Synced Sections > Build a content block once and reuse it across every portal experience - edit in one place, update everywhere. > Synced Sections are reusable content blocks you maintain once and reuse across every portal experience, so a single edit updates content everywhere it appears. ## What it does A synced section is a content block, built from rich text, documents, CRM views, forms, and other elements, that you save once and drop into any portal experience. When the same content needs to appear in multiple portals, such as a standard welcome, program terms, or an enablement block, you maintain it in one place instead of copying it everywhere. Edit the synced section and the change flows to every experience that uses it. This keeps your portal content consistent and removes the drift that creeps in when teams paste copies around. Partner marketing manages shared content centrally and trusts that every partner sees the same, current version. ## The problem it solves Copy-pasted portal content goes stale the moment it is duplicated: * **The same content lives in many portals** → Maintain it once as a synced section. * **Updates have to be repeated everywhere** → Edit the section once and it updates every use. * **Copies drift out of sync** → A synced section keeps every instance identical. * **A one-off needs to differ** → Detach a single instance when you need a local edit. ## From problem to solution Synced Sections give your portal a content layer that stays consistent. Build a block once, reuse it broadly, and edit in one place. When a single portal needs something different, detach just that instance. Shared content stays current without manual upkeep. ```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}} flowchart LR build["Build a block once"] --> reuse["Reuse across experiences"] reuse --> edit["Edit in one place"] edit --> detach["Detach a one-off when needed"] ``` ## Use cases Drop one section into many experiences. Change a synced section and every use updates. Ensure every partner sees the same current content. Detach an instance for a local edit when needed. ## Impact * **Low total cost of ownership** - Partner marketing manages shared content with no engineering. * **Time to value** - New portals reuse proven content instead of rebuilding it. ## Who it's for Maintains shared portal content in one place. Keeps portals consistent across partner types. ## Works with {/* CONNECTS:START - generated content goes here */} Reuse one section across experiences. Compose sections from library content. ## Going deeper Setup, configuration, and all how-to guides. Integration surface and code.