> ## 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.
# Every section you can add to a portal
> The complete catalogue of portal sections: what each group in the section picker holds, what it shows partners, and which ones depend on your CRM or plan.
> For anyone facing an empty experience and wondering what can go in it.
The experience builder is an open canvas, which is its strength and the reason a first build takes longer than any other setup step.
You cannot design a portal around blocks you do not know exist, and the picker groups them by where they come from rather than by what they are for.
This is the full list, with what each one shows a partner and when to reach for it.
## What you'll achieve
A working mental model of the section picker: sixteen groups, what each holds, which ones are populated automatically from partner data, and which ones only appear for your CRM or your plan. Enough to design a tab on purpose instead of by exploration.
## Before you start
Go to [Experience builder](https://app.introw.io/templates) and open one.
Sections are added inside a stage (a tab), so pick the tab you are building first.
See [Build and publish a portal experience](./build-and-publish-a-portal-experience).
Three things change what you see: which CRM you connected, which modules are on your plan, and whether you have saved any synced sections yet.
Each is called out below.
## The catalogue
### Where the picker starts
The picker opens on **Overview**, which is not a section type.
It shows a handful of suggested blocks for the fastest possible start, then the full group grid underneath.
With a CRM connected, the suggestions are your deal pipeline, your contact list, **Tasks & Journeys**, **Announcements**, **Asset hub** and **Forms**.
Without one, they are **Tasks & Journeys**, **Announcements**, **Asset hub**, **Forms**, **Introduction** and **Product overview**, so a portal is still buildable before the CRM is wired.
Search from here reaches every block in every group, which is faster than hunting through the grid once you know a name.
### Smart sections
Curated blocks that populate themselves from that partner's own data. These are what make one experience read as if it were built for each partner.
| Section | What the partner sees |
| ---------------------- | ----------------------------------------------------------------------------- |
| **Tasks & Journeys** | Their open tasks and their position in any journey they are on |
| **Goals** | Their targets and live progress against them |
| **Announcements** | Your published announcements, newest first |
| **Tiers** | Their current tier and the ladder above it |
| **Asset hub** | A browsable, searchable library of the content they are entitled to |
| **Commission** | Their commission lines and payouts |
| **Courses** | The courses they are enrolled in, with progress |
| **Certificates** | The credentials they have earned |
| **Partner Profile** | A chosen set of fields from their partner record, optionally editable by them |
| **Power BI Dashboard** | A Power BI report scoped to their data |
Reach for these first.
A portal built from smart sections stays current with no editing, because the content is the partner's data rather than copy you maintain.
### Rich sections
Layout and copy blocks. These are what you write, rather than what Introw fills in.
| Section | Use it for |
| ------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Introduction** | A named person with a photo, which is what makes a portal feel staffed rather than generated |
| **Hero Section** | The top of a tab: a headline, a line of context and a call to action |
| **Team** | The people behind the partnership, with photos |
| **Product overview** | What you sell, for a partner who has to explain it to a customer |
| **Banner** | A single strip of emphasis, for a deadline or a change |
| **Collapsible content** | An accordion. Each item holds any block, an embedded form included, so it is the right home for an FAQ |
| **Columns** | Two to five columns per row with draggable widths. Any block goes in a column |
| **Text** | Headings, lists, tables, dividers and images |
| **Call to action button** | Sends a partner to a tab, a form or an asset |
### CRM
Live views of your CRM, scoped to that partner. Every one of these carries your own object labels, so a portal reads in your team's vocabulary rather than ours.
| Section | Availability |
| ------------------ | ---------------- |
| Deal pipeline | Every CRM |
| Contact list | Every CRM |
| Company list | Every CRM |
| Ticket pipeline | Not on Pipedrive |
| Lead list | Not on Pipedrive |
| Custom object list | Not on Pipedrive |
| Order pipeline | HubSpot only |
Sharing CRM data with partners is scoped rather than open: you choose the records and the fields.
See [Set up a shared pipeline](/features/co-selling/shared-pipelines/guides/set-up-a-shared-pipeline) and [Show and rename CRM fields](/features/integrations/crm/guides/show-and-rename-crm-fields).
### Forms
Your own forms, in two shapes:
* **A form**, embedded so a partner submits without leaving the page. This is where deal registration, referrals, applications and requests belong.
* **Form submissions**, a list of that partner's own submissions with a **Status** column. This is the block that stops partners emailing to ask where their registration got to.
See [Ways to submit a form](/features/forms/sharing-submitting/guides/ways-to-submit-a-form).
### Content and embeds
Five groups that all put existing material on the page.
| Group | What it holds |
| ------------------- | ---------------------------------------------------------------------------------- |
| **Asset library** | Your folders and assets, placed directly in the tab |
| **Synced sections** | Sections you saved for reuse. Maintain once, and every experience using it updates |
| **Documents** | Google Slides, Google Sheets and Google Docs |
| **Videos** | Loom, Vimeo, YouTube and Vidyard |
| **Embed anything** | Any other URL |
**Meeting** is the same idea for booking links: HubSpot meeting links, Calendly and Cal.com, so a partner books time without an email round trip.
Synced sections are the answer to the same legal notice or program rules living in nine experiences.
See [Reuse content with synced sections](/features/content/synced-sections/guides/reuse-content-with-synced-sections).
### Reporting
**Dashboard embed** puts a whole dashboard in the portal, **Report embed** puts a single chart in, and **Power BI** surfaces a Power BI report.
These three are not on the group grid, so search for them by name.
See [Embed a dashboard in the portal](/features/reporting/dashboards/guides/embed-a-dashboard-in-the-portal) and [Show a partner dashboard in the portal](/features/reporting/partner-analytics/guides/show-a-partner-dashboard-in-the-portal).
### Groups that depend on your plan
**Marketing Funds** and **Affiliate Campaigns** only appear when those modules are on your plan.
Marketing Funds shows a partner their fund balance and their requests; Affiliate Campaigns shows their tracked links with clicks and conversions.
If either group is missing from the grid, that is why.
Check what your plan includes at [introw.io/pricing](https://introw.io/pricing).
## Two things that are not sections
**Dynamic variables** are not blocks. Type `{` anywhere you write and insert a value that resolves per partner, so one paragraph greets every partner by name and names their own manager. Anything you would have built a section for just to personalise it is usually a variable instead.
**Quizzes and video lessons** belong to courses, not portals. They appear in the course builder rather than here. See [Build a course manually](/features/courses/authoring/guides/build-a-course-manually).
## Verify it worked
Preview the tab as a real partner and check two things: every smart section resolved to their data rather than sitting empty, and nothing on the page is a block you would have to remember to update by hand.
An empty smart section usually means the underlying thing does not exist yet for that partner, not that the section is broken.
See [Draft, published and preview](./draft-publish-and-preview).
## Related
Put these sections into a working portal.
Decide which tab each section belongs on.
The most personal of the smart sections, in detail.
Full configuration options.