Skip to main content
Paperwork is where partner onboarding stalls. The terms sit on a web page, the NDA and the partner agreement sit in DocuSign, the signed copies end up in somebody’s inbox, and the partner is chased by email for all three. This guide puts that whole sequence inside the partner’s own portal: a click-through acceptance during intake that lands in your CRM, a signing step for the heavier agreements where the partner already works, and every signed document back in their portal afterwards.

What you’ll achieve

A partner who accepts your terms while applying, with the acceptance written to their record in your CRM. The agreements that need a real signature reach them as a step in their onboarding rather than an email thread. The signed documents live in their portal, visible to them and to nobody else. And what an unsigned partner can do is gated automatically, instead of being tracked by hand.

Who does what

There is no DocuSign app to install. Introw does not generate envelopes, and your e-signature tool does not notify Introw when one is signed. Everything below works the same with DocuSign, PandaDoc, Adobe Acrobat Sign, or any tool that gives you a signing URL.

Before you start

1

Connect your CRM

Acceptance and signature milestones are written to CRM properties, and segments read them live. See Connect HubSpot.
2

Have your terms page and your signing links

The public URL of your terms and conditions, and from your e-signature tool either a reusable signing link for a document every partner signs, or a per-partner envelope link.
3

Decide what each agreement unlocks

Write down which agreement gates which part of the program, for example that deal registration opens only after the partner agreement is signed. That decision drives the segments later in this guide.

Steps

Accept your terms at intake

1

Open your intake form

Go to Forms and open the form partners apply through. A partner application form already carries a terms and conditions checkbox, so there is nothing to add. On any other form, add a Checkbox field from the Add to form menu. See Set up a partner application form.
2

Point the label at your terms

In the field label, replace the placeholder URL with the link to your own terms and conditions, so an applicant can read them before agreeing. Keep the label to one sentence: this step should cost the partner one click.
3

Record the acceptance in your CRM

A ticked box is only useful if it leaves a record. In the field’s settings, map it to a CRM object and property, then open the form’s Automation tab and set how the submission writes:
  • A boolean property - who accepted. Map the checkbox to it on the partner’s company record, so the fact sits on the account and not only on a form submission.
  • A date or date-time property - when they accepted. Set it from the automation as the compliance record of the moment.
  • Write behavior - Fill if empty is the default and never overwrites what a rep set. Choose Overwrite when you want a later re-acceptance, after a terms update, to replace the earlier date.
Attribution to the partner is automatic, using the method you defined on Object Linking, so there is nothing to wire per form. See Map form fields to your CRM.
For many referral and affiliate programs, this checkbox is the entire agreement. Ask for a countersigned pack only from partners who have shown they will transact. Four documents in front of a partner who has not done anything yet is where onboarding dies.

Put the signing step inside the portal

1

Generate the signing link

In your e-signature tool, produce the link that opens the document. It comes in two shapes, and they are placed differently in Introw:
  • One document, every partner - a reusable signing link, such as a DocuSign PowerForm. The signer identifies themselves on the signing page.
  • One document, one partner - an envelope prepared for a named signer, with a link that belongs to that partner alone.
2

Place the reusable link on the experience

In the experience builder, open the onboarding stage and add an Embed anything section with the signing URL, so the document renders inside the portal. Some signing pages refuse to be displayed inside another page; when that happens use a Call to action button section instead, which opens the signing page in a new tab and keeps the portal as the single starting point. See Embed external content.
3

Place a per-partner link on the partner

Open the partner, go to their Assets tab, and add the envelope link with Web page URL, set to Partner Specific. Surface it through a Partner Specific Asset Hub section so each partner sees only their own documents. The same hub will later hold the signed copy, which means one place in the portal covers the agreement before and after it is signed. See Share an asset with one partner only.
4

Make it a step in their journey

A link nobody is asked to click gets ignored. On the onboarding journey, add a task for the agreement and use Add action to close it automatically:
  • Opens a link - the task completes when the partner opens the signing link. Use it for the light documents, where reaching the page is enough of a signal to stop chasing.
  • Uploads a file - the task completes when the partner returns the executed copy, which then sits on their record. Use it when you need proof rather than intent.
Set the journey to sequential when the NDA has to be signed before anything else opens, give each task a due-date offset, and let partner notifications do the chasing. See Journeys.
Introw is not told by your e-signature tool when a document is signed, so Opens a link records that the partner reached the signing page, not that they finished. When “signed” has to be a fact, get it from one of two places: the partner uploads the executed copy on the task, or your e-signature tool’s own CRM integration writes a property on the partner’s CRM record, such as DocuSign writing back to Salesforce, which Introw then reads like any other CRM field. Use the second one whenever the signature gates something.

Gate what a signature unlocks

1

Build the segment

Create a dynamic segment filtered on the property that carries the acceptance or the signature. Dynamic segments re-evaluate as CRM data changes, so a partner joins the moment the property flips. See Segments.
2

Restrict the stage to it

In the experience, restrict the stage, tab, or section that the agreement unlocks to that segment: deal registration, pricing, marketing funds. An unsigned partner never sees it, and nobody grants access by hand. See Build a progressive onboarding path.
3

Automate the ends

Enroll every new partner in the agreements journey with a workflow when they are created, and trigger the next step on Journey completed, so the tier, the certificate, or the welcome email follow the signature without anyone watching for it. See Workflows.

Give the signed documents back

1

Upload the executed copy

On the partner’s Assets tab, add the countersigned PDF as a Partner Specific asset and name it for the partner, for example “Reseller agreement 2026” rather than a file name from your drive.
2

Place it in their hub

Point the asset at the Partner Specific Asset Hub section, ideally on a Contracts or Legal stage, so a partner who needs their paperwork a year later finds it themselves instead of emailing their partner manager.
Where your team keeps the legal record does not change. If your e-signature tool files the executed copy into your CRM, it stays there for your team, and the copy in the portal is the partner’s own.

Verify it worked

Submit a test application with the box ticked, then open the partner’s record in your CRM: the acceptance property is set and the date property carries the moment. Open the portal as that partner: the agreement step is on their journey and the link opens the right document. Complete the step, and check that the task closes, the segment picks the partner up, and the gated tab appears for them. Finally, upload a signed copy as a partner-specific asset and open the portal as a different partner on the same experience: the hub is there, their own documents are in it, and the first partner’s file is nowhere.

Build a progressive onboarding path

Unlock the rest of the portal as partners qualify.

Share an asset with one partner only

The mechanics behind partner-owned documents.

Set up a partner application form

The intake form the terms checkbox lives on.

Implementation reference

Full onboarding configuration options.