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

# Collaborate on a shared deal

> Open a CRM record for partner collaboration, set the right collaborators, and keep the deal conversation on the record with comments and files.

{/* Co-selling on a record only works once the partner can see it, the right people are in the
  loop, and the conversation lives on the deal instead of scattered across inboxes. This guide
  covers the whole job: share the record for collaboration, put exactly the right partner
  contacts on it, then work it together with comments and files. Reach for it when a single
  opportunity needs hands-on co-selling rather than just pipeline visibility. */}

## What you'll achieve

A specific CRM record is opened as a shared workspace: the partner sees it from the portal, only the partner contacts you choose can act on it, and the back-and-forth (comments, files, next steps) lives on the record itself - so context never gets lost and both sides work the same opportunity instead of trading email updates.

## Before you start

<Steps>
  <Step title="The record is attributed to the partner">
    Only records attributed to a partner can be shared with them, so confirm the deal, contact, or company is attributed first. See [Set up a shared pipeline](./set-up-a-shared-pipeline).
  </Step>

  <Step title="The partner has portal access">
    The partner contacts you add need access to the experience so they can open the shared record.
  </Step>
</Steps>

## Steps

<Steps>
  <Step title="Find the record">
    Go to [Deals overview](https://app.introw.io/overview/DEAL), or open the partner's record, and locate the deal, contact, or company you want to co-sell. Starting from the overview lets you work any attributed record; starting from the partner shows just theirs.
  </Step>

  <Step title="Share it for collaboration">
    Use **Share** to open the record for partner collaboration. This turns the CRM record into a shared workspace and takes you to its collaboration view, where the conversation, files, and tasks live. Sharing is what makes the record visible to the partner in the portal - without it, the partner cannot see or act on it.
  </Step>

  <Step title="Set the collaborators">
    Open **Collaborators** and put exactly the right partner contacts on the record. Collaborators are the people in the loop, so this is your access control for the deal:

    * **Add** the partner contacts who are working the opportunity, so they can see and act on it.
    * **Remove** anyone who should not have access; removal ends their access to the record immediately.

    Keeping the list tight means the deal is visible to the people co-selling it and no one else at the partner.
  </Step>

  <Step title="Discuss it in context">
    On the collaboration view, use the **Activity** feed to comment on the deal. Everyone in the loop sees the thread and can reply, so decisions and next steps stay attached to the opportunity as it moves. Share relevant attachments in **Files** so the materials live with the deal too.
  </Step>
</Steps>

## Verify it worked

The record opens in its collaboration view, the partner contacts you added see it from the portal, and a comment you post in the **Activity** feed appears for both sides. Anyone you removed can no longer open the record.

## Related

<CardGroup cols={2}>
  <Card title="Run tasks on a shared deal" icon="list-check" href="/features/co-selling/tasks/guides/run-tasks-on-a-shared-deal">
    Add next steps with owners and due dates on the shared record.
  </Card>

  <Card title="Set up a shared pipeline" icon="diagram-project" href="./set-up-a-shared-pipeline">
    Attribute deals and control the fields partners see and edit.
  </Card>

  <Card title="Collaborate from your CRM" icon="plug" href="/features/integrations/crm">
    Work the same shared record from inside HubSpot or Salesforce.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full configuration options.
  </Card>
</CardGroup>
