Set up a shared pipeline

A connected CRM

Access to integration settings and experiences

A partner experience to add it to

Open your CRM connection

Go to Settings, then Integrations and open your CRM connection. Attribution is the foundation of everything shared: it links each deal to the partner who sourced or works it, and until it is set there is nothing to show in a pipeline.

Define how deals relate to partners

Configure the attribution using the relationship your CRM already holds between a deal and a partner (for example a partner association or a property on the deal). This decides which partner each deal belongs to, so it appears for the right partner and no one else. Save it and let Introw sync; attributed deals then become available to expose in a pipeline view and on partner records.

Open the experience builder

Go to partner experiences and open the experience where the pipeline should appear. The view lives in the experience content, so partners reach it as part of their portal rather than as a separate report.

Insert a deals list and pick the pipeline

Add a CRM list of deals to the content, then set its core inputs:

• Object and pipeline - choose the deal object and which pipeline’s stages to show; this defines the columns of a board view and the stage set partners see.
• Stages - keep the stages partners should see and hide any that are internal-only, so the board reflects the partner-facing process.
• Layout - show the view as a board by stage or as a table. A board reads well when partners move deals through stages; a table suits a denser, read-heavy list. (A board needs more than one visible stage; otherwise it falls back to a table.)
• Saved views - save one or more named views with their own columns and filters when different cuts of the pipeline are useful.

Set the view's filters

Open the view’s filters. Even within a partner’s attributed deals, not everything belongs in the portal, and filters scope the list precisely. The view starts with a partner-attribution filter so each partner only ever sees their own deals; add further conditions (pipeline, stage, a property value) to narrow it. At least one filter is required, and the partner-attribution filter is what guarantees partners never see another partner’s deals.

Open the property configuration

Open the deals list configuration. Properties are set per embed (and the same configuration governs the record when a partner opens a single deal), so this is where you decide the partner-facing fields.

Configure the visible properties

Add the properties partners should see and shape how they appear. For each property you can:

• Add or remove - choose which fields are exposed; leave internal fields off entirely.
• Rename - relabel a field to partner-friendly wording without touching the CRM name.
• Reorder - drag to set the order partners read them in.
• Hide on card - keep a property in the detail view but off the summary card, to keep cards clean.
• Primary - mark the property shown as the card’s headline; it defaults to the account.
• Sort - set the property and direction the list sorts by (newest first by default).
• Notify on change - flag properties whose changes should drive update notifications to the people watching the deal.

Mark the editable properties

Decide related items

Choose what related records appear alongside the deal:

• Show related contacts - expose the contacts on the deal; optionally Include phone numbers, and on HubSpot Allow contact creation so partners can add contacts.
• Show line items - let partners view products and services on the deal. Viewing is available on any plan; Allow line item editing is HubSpot-only and requires the Product Hub add-on.
• Show quotes - HubSpot-only; lets partners view quotes on the deal. Allow quote creation and Allow quote publishing require the Product Hub add-on (and quote-write permission on the HubSpot connection), and you can gate who creates or processes quotes by segment.

Set per-embed notifications

On the Notifications tab, set which events notify people for this embed - for example a New object, Object updates (on the properties you flagged), a Sleeping object stuck too long, or a Deal closed won. These overrides are per embed, so this pipeline can notify differently from another. Save the configuration when done.