> ## 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.
# Work deals from the Introw card
> What a partner rep does day to day from the Introw card in HubSpot: register a deal, link an existing one, edit it, and collaborate on the record.
Setup is a one-time job. This is what a partner rep does with the card afterwards, on the deals they already work. Everything here happens in the HubSpot record sidebar, and the portal views open in a modal inside HubSpot, so the rep never changes tabs or signs in again.
## What you'll achieve
A partner rep who registers deals, links them to the vendor's matching deal, keeps them updated, and collaborates with the vendor's team without opening a portal, a form, or an email.
## Before you start
The partner has connected HubSpot and added the **Introw Partner Connect** card to their deal view. See [Connect HubSpot](./connect-hubspot).
The card shows one tile per vendor portal that rep can reach. With none, they see a single "No partner portals" tile.
## What the card looks like on a deal
The card is a sidebar card on **deals and tickets**, and it renders one tile per vendor. Which tile state a rep sees depends only on how far that deal has progressed with that vendor.
| State | What the rep sees | What they do next |
| ------------------------------- | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| **Nothing shared yet** | The vendor, a short description of who they are, and **Collaborate** plus **View portal** | Register the deal, or start a conversation |
| **Registered, not yet linked** | A preview of the submission and the latest comment on it | Follow it up, or wait for the vendor to accept |
| **Linked to the vendor's deal** | The vendor-side deal properties the vendor exposes, formatted and live | **Edit deal**, **Add comment**, **View portal**, or unlink |
| **No vendor access** | One small tile: "No partner portals, contact your partnership manager" | Ask their partner manager for portal access |
| **Connection lapsed** | A **Reconnect** prompt | Re-authorize HubSpot from the portal |
## Register a deal from HubSpot
The most common daily action. The rep has an opportunity in their own CRM and wants it registered with the vendor.
On the vendor's tile, **Collaborate** opens the vendor's portal in a modal inside HubSpot, already signed in, on the right record.
The rep completes the vendor's registration form. It is the vendor's real form, so whatever fields, required values, and dropdowns the vendor configured apply here exactly as they do in the portal.
Once submitted, the tile switches to the submission state and shows the submission plus its latest comment, so the rep tracks the outcome from the same record. On the vendor's side the registration runs through their normal conflict checks, approval gates, and automations. Nothing about registering from HubSpot bypasses those.
## Link a deal the vendor already has
When the vendor already has the deal, whether the partner registered it earlier or the vendor created it, linking joins the two records into one shared opportunity instead of creating a duplicate.
From the card, or from **Link existing deals** in the partner's portal, the rep picks the vendor deal that represents the same opportunity. See [Enable Partner Connect and link a deal](./enable-partner-connect-and-link-a-deal) for the full flow and the To do / Done tabs.
The two records become one shared deal. From then on the card reads the vendor's side of it live, so the rep sees the vendor's current stage and next steps on their own record without asking.
## Keep a linked deal moving
Once linked, the tile becomes the rep's working surface for that vendor.
Worth setting expectations on: the card is a **live read** of the vendor's deal plus partner-initiated writes back to it. The rep always sees the vendor's current state, and their edits and comments land on the vendor's record immediately. It is not a background field-by-field mirror of the partner's own pipeline into the vendor's CRM, so tell reps to use **Edit deal** and **Add comment** when they want the vendor to know something, rather than assuming a silent sync carried it.
* **Read the vendor's side.** The properties on the tile are the vendor's deal fields, exactly the ones that vendor chose to expose, with live values. No status email required.
* **Edit deal** appears when the vendor has marked any of those properties editable, letting the rep update the vendor's record from their own CRM.
* **Add comment** opens the shared conversation on that record, so the vendor's team is answering in the same thread the deal lives in.
* **View portal** opens the whole portal in the modal, still inside HubSpot and still signed in, for everything beyond the deal: enablement, training, commissions, and the shared timeline and deal coaching for this opportunity.
* **Unlink** (the icon in the tile header) disconnects the two records if the match was wrong. Nothing is deleted, and they can be re-linked. See [Unlink a deal](./unlink-a-deal).
## Working with more than one vendor
A rep who co-sells with several vendors gets one tile per vendor on the same deal, each with its own state. They register with one vendor and not another, and each vendor only ever sees their own tile's activity. Nothing is shared across vendors.
## Verify it worked
Open a HubSpot deal as a rep with vendor access: the card lists the vendor, and after registering, the tile shows the submission. After linking, it shows the vendor's live deal properties. If the tile stays on "No partner portals", that rep has no access to a vendor portal yet, which is a vendor-side permission, not a setup problem.
## Related
The one-time setup that puts the card on the record.
The partner-facing overview to forward.
Sequence this across a large partner base.
The coaching a rep gets in the portal view.