> ## 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.
# Shared Pipeline
> Give resellers one CRM-drawn view of the deals they own and let them work each one on the live record - see the fields you expose, edit the ones you allow, manage line items, and build quotes, all without a CRM seat.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> A reseller who owns the sale needs more than a read-only deal - they need to run it. Shared pipeline gives resellers a CRM-drawn view of every deal they own and turns each one into a workspace where they update the fields you allow, manage line items, and build quotes, while you keep full control and your team keeps its CRM seats.
## What it does
Shared pipeline is the reseller-applied version of [co-selling's shared pipelines](/features/co-selling/shared-pipelines): the same CRM-drawn pipeline and record collaboration, scoped to the deals a reseller owns. After a reseller registers a deal and it lands attributed in your CRM, it appears in their pipeline view in the portal. Your team sees the same opportunities org-wide or per partner inside Introw, and because the records are CRM-drawn the two views never diverge.
Each deal in that pipeline is a workspace, not just a row. You decide which properties the reseller can **see** and which they can **edit**, and your changes write back to the CRM under your rules. For deals, the embed adds commercial controls: resellers can manage line items and, where supported, create and publish quotes, so a reseller can run the full commercial side of their own opportunity. None of it requires a CRM seat for the partner.
You stay in control of scope. Attribution decides which deals belong to the reseller, visible properties decide what they see, editable properties decide what they can change, and line item and quote settings decide how far their commercial control extends. Anything you do not explicitly open stays read-only.
## The problem it solves
Resellers stall when they can see a deal but cannot work it:
* **Partners cannot see the deals they own** → A pipeline view in the portal shows resellers every deal attributed to them.
* **Partners email the vendor for every field change** → Resellers edit the fields you mark editable directly on the CRM record.
* **Giving partners CRM seats is costly and risky** → The pipeline, edits, line items, and quotes all work through the portal and embeds, with no CRM seat.
* **You cannot let partners touch everything** → Visible and editable properties scope the record field by field; everything else stays read-only.
* **Quoting goes back and forth over email** → Resellers manage line items and build quotes on the deal itself.
## From problem to solution
Put registered deals on a shared pipeline, expose the fields a reseller owns as visible and editable, and optionally enable line items and quotes. The reseller runs their deal on your CRM record - viewing pipeline, updating fields, assembling line items, and quoting their customer - while your team stops being a data-entry relay and the data stays clean because every change writes back to the CRM under your rules.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
registered["Registered deal"] --> pipeline["Shared pipeline"]
pipeline --> work["Reseller edits and quotes"]
work --> writeback["Writes back to CRM"]
```
## Use cases
Give resellers a pipeline view of every deal attributed to them.
Allow edits on the fields the reseller owns; keep the rest read-only.
Let resellers run the commercial detail on their deal.
Everything works from the portal or an embed.
## Impact
* **CRM-native** - Pipeline, edits, line items, and quotes are all drawn from and written to the CRM record, no seat required.
* **Low total cost of ownership** - You choose, field by field, what resellers see and change.
* **Trust & accuracy** - Attribution and visible/editable scope keep the shared view correct and the partner's deal protected.
## Who it's for
Decides what resellers see and edit on shared deals and keeps their pipeline moving.
Sees their deals and works each one directly on the CRM record.
Configures attribution and the field-level scope resellers get.
## Works with
{/* CONNECTS:START - generated content goes here */}
Registered deals land on the shared pipeline.
Resellers build quotes on their shared deals.
The cross-motion shared pipeline this builds on.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.