> ## 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. # Experiences > Build the partner portal no-code from stages, sections, and blocks: one experience, published to every linked partner portal. > Experiences are the no-code builder behind your partner portal: design once from stages and sections, then publish the same polished experience to every partner. ## What it does An experience is a portal layout you build from stages (the tabs partners navigate) and sections (the content blocks inside them). You assemble it visually, dropping in rich text, documents, CRM views, forms, and more, without writing code or filing an engineering ticket. Assign an experience to your partners and each gets their own partner portal based on it, so you design the portal once and deliver it consistently to everyone. When you improve an experience, you publish the change out to the partner portals linked to it, and you can preview exactly what partners will see before you do. Reusable synced sections let you maintain shared content in one place and drop it into many experiences. The result is a partner portal your team owns and evolves on its own. ## The problem it solves A partner portal that needs engineering to change is a portal that never changes: * **Building a portal needs engineering** → A no-code builder lets partner marketing assemble the portal from stages and sections themselves. * **Every partner needs the same experience** → Design one experience and publish it to every linked partner portal. * **Updating the portal is slow and risky** → Edit the experience, preview it, and publish the change to all rooms at once. * **The same content lives in many places** → Synced sections keep shared content in one place and reuse it everywhere. ## From problem to solution Experiences put the portal in your team's hands. You build stages and sections visually, preview the result, and publish to every linked partner portal from one place. The portal becomes something partner marketing ships and iterates on, not a project that waits on engineering. ```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}} flowchart LR build["Build stages and sections"] --> preview["Preview"] preview --> publish["Publish to partner portals"] ``` ## Use cases Assemble stages and sections visually, no engineering required. Assign an experience so every partner gets the same portal. Improve an experience and push the change to all linked rooms. Maintain synced sections once and drop them into many experiences. ## Impact * **Low total cost of ownership** - Partner marketing builds and changes the portal with no-code. * **Time to value** - A full portal experience comes together in an afternoon, not a project. ## Who it's for Designs and ships the portal experience partners use. Keeps experiences assigned and consistent across partners. ## Works with {/* CONNECTS:START - generated content goes here */} Gate tabs and sections to segments. Add library assets to a stage. Embed forms in a stage. ## Going deeper Setup, configuration, and all how-to guides. Integration surface and code.