Every section you can add to a portal

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

​

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. 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.

​

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. Sharing CRM data with partners is scoped rather than open: you choose the records and the fields. See Set up a shared pipeline and 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.

​

Content and embeds

Five groups that all put existing material on the page. 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.

​

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 and 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.

​

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.

​

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.

​

Related