Shared Pipelines gives both sides one view of the deals you are working together - and turns each of those deals into a shared workspace. Partners see their attributed pipeline, your team sees the same, and everyone collaborates on the actual CRM record.
What it does
Shared Pipelines brings the pipeline and the record together. Partners see the deals attributed to them in a pipeline view inside the portal, while your team sees the same opportunities org-wide or per partner inside Introw. Because the records are drawn from your CRM through attribution, the two views never diverge: a stage change in the CRM shows up for everyone who should see it. Each deal in that pipeline is also a collaboration surface. Any attributed CRM object - a deal, contact, company, ticket, or custom object - opens with a shared activity feed for comments, a files area, tasks, and the properties you expose. Reps work it from inside HubSpot or Salesforce, partners from the portal or an embed, so neither side leaves the tool they live in. You stay in control of scope. Attribution decides which deals belong to which partner, filters narrow the pipeline view, collaborators decide which partner contacts are in the loop on a record, and field-level settings decide which properties partners can see and which they can edit - all without handing out a CRM seat.The problem it solves
Partners working blind to pipeline, and reps blind to the partner, is one of the biggest drags on channel revenue:- Partners cannot see their own deals → A pipeline view in the portal shows partners the opportunities attributed to them.
- Vendor and partner views drift apart → Both sides read from the same CRM-attributed records, so there is no reconciling two pipelines.
- Updates get lost in email threads → A shared activity feed keeps the conversation on the record, where it belongs.
- You cannot control what partners see or change → Attribution, filters, collaborators, and visible/editable properties scope the view precisely, with no CRM seat for partners.
From problem to solution
Shared Pipelines makes the CRM’s pipeline a shared, scoped surface, and each record a shared workspace. Attribution and filters decide what shows, collaborators and field-level visibility decide who sees and edits what, and both sides read and act on the same records. Partners get visibility and a way to contribute; your team keeps a per-partner view and full control; the CRM stays the single source of truth.Use cases
Show partners their deals
Give partners a pipeline view of the opportunities attributed to them.
Co-sell on a deal
Comment and share files with a partner directly on the deal record.
Scope the view
Filter pipeline and choose which properties partners can see and edit.
Work from your CRM
Reps read pipeline and collaborate from inside HubSpot or Salesforce.
Impact
- CRM-native - Pipeline and collaboration are drawn from CRM-attributed records, so vendor and partner views stay in sync.
- Work where you already are - Reps work from the CRM and partners from the portal, each in the tool they already use.
- Trust & accuracy - Attribution, filters, and field-level visibility keep the shared view scoped and correct.
Who it’s for
Partner Manager (CAM / PAM)
Reads partner pipeline and keeps shared deals moving.
Sales Rep / AE
Collaborates with partners on shared accounts without leaving the CRM.
Partner - Sales & Marketing
Sees their attributed deals, prioritizes follow-up, and works the record.
RevOps
Configures attribution and the field-level scope partners get.
Works with
CRM
Collaborate from inside the CRM record.
Deal Coaching
AI coaches partners on pipeline deals.
Tasks
Add tasks to any shared deal.
Shared Pipeline
Registered reseller deals work on this shared pipeline.
Headless
Going deeper
How to
Setup, configuration, and all how-to guides.
API reference
Integration surface and code.