*Gap samples / Gap 1 - Getting started (admins)*

# Set up your partner program: the admin quickstart

You finish this page with one pilot partner approved, invited, and through their first referral, with the referral sitting in your CRM. Each step links to the detailed article that already exists. This page supplies the order, because most setup mistakes in EULER come from doing the right steps in the wrong sequence.

**Gap:** 1 of 13 · **Reader:** New EULER admin · **Result:** One partner live, end to end

## Why this page needs to exist

The help center has a partner "Start Here" page and detailed admin articles, but no admin path. A new admin who approves a partner before the CRM is connected, or publishes a form before testing its CRM mapping, creates records that have to be fixed by hand. Forms 2.0 says Forms will not work at all until a CRM is connected, and that warning sits halfway down a long article.

## What exists today, and is linked rather than repeated

- [Forms 2.0](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0), [Create an Agreement Template](https://support.eulerapp.com/en/c/core-euler-features/agreements/create-an-agreement-template), [Flows](https://support.eulerapp.com/en/c/core-euler-features/flows/flows), [Potential Duplicate](https://support.eulerapp.com/en/c/integrations/potential-duplicate), [Configuring PAM](https://support.eulerapp.com/en/c/ai-agents/customer-guide-configuring-and-monitoring-pam-for-partners).

---

*Sample documentation starts here*

## Before you start

- You are an admin on your EULER workspace. **[VALIDATE ROLE NAME]**
- You can sign in to your CRM (Salesforce, HubSpot or Pipedrive) as a user whose permissions EULER should inherit. EULER acts with the permissions of whoever authorizes the connection.
- You have one real pilot partner. A real partner finds setup problems a test account does not.
- Your partner agreement exists as a document.

## What can go wrong

- A form question mapped to a CRM field that does not exist makes the form's CRM sync fail. Forms 2.0 has a Test button for exactly this.
- In Salesforce, a Lead that already has the applicant's email makes partner creation fail with a duplicate error. See [Salesforce setup checks](05-salesforce.md).
- Choosing **Mark as Approved** on a potential duplicate changes the status only. It creates nothing in EULER or your CRM.

## Steps

1. **Connect your CRM first**

   Go to **Integrations**, find your CRM and click **Integrate**, then authorize it ([Salesforce](https://support.eulerapp.com/en/c/integrations/salesforce/salesforce), [HubSpot](https://support.eulerapp.com/en/c/integrations/hubspot/integrating-hubspot)). You **shall** do this before building any form: Forms require an active CRM integration, because answers are written straight to the CRM. You **should** authorize with an integration user rather than a person, so the connection does not break when that person leaves.

   **Check:** the CRM shows as connected on the Integrations page, under the user you intended.
2. **Build and test the partner registration form**

   Go to **Settings > Forms**, click **+ New Form**, and choose the **Partner Registration** type. It starts with First Name, Last Name, Email and Company. Give every question an **API Value** that exactly matches a field on the CRM object. Then click **Test**: it submits sample answers to your CRM with your mappings.

   **Check:** the test record appears in your CRM with every answer in the field you mapped. If you edit a mapped question afterwards, test again.
3. **Create the agreement template and decide whether it locks the portal**

   Create the template (see [Create an Agreement Template](https://support.eulerapp.com/en/c/core-euler-features/agreements/create-an-agreement-template)). The template **shall** have your company signature on file: a template without one cannot be sent. Decide now whether partners can use the portal before signing. EULER can lock the portal until the agreement is signed.

   **Check:** the template shows a company signature, and you have written down whether it restricts portal access.
4. **Build the onboarding flow and make it a Standard Flow**

   Build a short flow: agreement first, then only the training a partner needs before their first referral. Publish it (status **Active**). Add it to your **Standard Flows**, the default set EULER assigns automatically when a partner joins the portal, so you never have to assign it by hand. **[VALIDATE MENU PATH]**

   **Check:** the flow is Active and listed as a Standard Flow.
5. **Give PAM something to answer from**

   Add at least your program terms and your referral rules as PAM knowledge sources, so the partner's first questions get answers from your content (see [PAM AI Knowledge Sources](https://support.eulerapp.com/en/c/ai-agents/pam-ai-knowledge-sources)).

   **Check:** each source shows as active. A source that never finished indexing is not used.
6. **Publish the form and send it to the pilot partner only**

   Toggle the form to **Active**, then send the pilot partner the form link or embed it with **Get Code** (see [Embed Euler Form](https://support.eulerapp.com/en/c/core-euler-features/customization-content/embed-euler-form)). Keep it to one partner until step 9 passes.

   **Check:** the partner's submission appears as a new partner application for you to accept.
7. **Approve the application, knowing what approval does**

   Approving runs onboarding: EULER finds or creates the partner and partner contact from the answers, syncs to your CRM, applies tags and creates an affiliate link. If EULER flags a **Potential Duplicate**, choose **Proceed with Creation** to create or reuse the CRM records. **Mark as Approved** creates nothing.

   One exception: on a Salesforce form that creates partners in the CRM only, approval creates only the Salesforce record. The partner appears in EULER when the sync brings it back.

   **Check:** the partner exists once in EULER and once in your CRM, and has an affiliate link. In CRM-only mode, the Salesforce record exists and the EULER record follows.
8. **Invite the partner's contacts to the portal**

   Invite the people who will submit referrals. If you would rather introduce EULER yourself, you can skip the invite email. **[VALIDATE OPTION LABEL]**

   **Check:** the contact's invitation shows as accepted. If it does not, ask POPS why the partner cannot access the portal (see [Troubleshooting Partner Access Issues with POPS AI](https://support.eulerapp.com/en/c/ai-agents/troubleshooting-partner-access-issues-with-pops-ai)): it reports bounced or never-activated invites and pending agreements.
9. **Run one real referral end to end**

   On a short call, have the partner submit one real referral, from the portal or by forwarding an email (see [DealFlow AI](03-dealflow.md)). Approve it from **Referrals to Approve** (see [Referral Approval](https://support.eulerapp.com/en/c/security-access/referral-management/referral-approval)).

   **Check:** the referral is approved in EULER, and the CRM record it should create exists with the partner attached.

## What wrong looks like

**WRONG - SETUP ORDER**

```
1. Invite 40 partners from a spreadsheet
2. Build the registration form
3. Connect Salesforce
4. Approve the applications that came in

Why it fails: in Forms 2.0, Forms cannot be used until a CRM
is connected, so step 2 stalls. When it does work, 40 partners
meet an untested form, and any duplicate or mapping error is
now 40 records to fix by hand. Connect, build, test, then
prove it on one partner.
```

## Check your work

- CRM connected under the intended user.
- Registration form passed its Test, and nothing mapped changed since.
- Agreement template has a company signature and a decided portal-lock setting.
- Onboarding flow is Active and a Standard Flow.
- Pilot partner exists once in EULER and once in the CRM, with an affiliate link.
- One referral approved, with its CRM record and the partner attached.

## Confirm with engineering

1. The role that can connect integrations and approve applications is [role]. Correct me.
2. Standard Flows are managed at [menu path]. Correct me.
3. The option to skip the partner invite email is labelled [label] and sits at [location]. Correct me.
4. Approving an application always creates the affiliate link at approval, outside CRM-only mode. Yes / no / correct me.
5. Pipedrive uses the same Integrations > Integrate path as Salesforce and HubSpot. Yes / no / correct me.

### Related documentation

- [Salesforce: connect](https://support.eulerapp.com/en/c/integrations/salesforce/salesforce) and [Integrating HubSpot](https://support.eulerapp.com/en/c/integrations/hubspot/integrating-hubspot)
- [Forms 2.0: building, testing and publishing forms](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0)
- [Embed Euler Form](https://support.eulerapp.com/en/c/core-euler-features/customization-content/embed-euler-form)
- [Create an Agreement Template](https://support.eulerapp.com/en/c/core-euler-features/agreements/create-an-agreement-template) and [Send an Agreement to a Partner](https://support.eulerapp.com/en/c/core-euler-features/agreements/send-an-agreement-to-a-partner)
- [Flows](https://support.eulerapp.com/en/c/core-euler-features/flows/flows) and [Using Flows with Your Partners](https://support.eulerapp.com/en/c/core-euler-features/flows/using-flows-with-your-partners)
- [Configuring and Monitoring PAM for Partners](https://support.eulerapp.com/en/c/ai-agents/customer-guide-configuring-and-monitoring-pam-for-partners)
- [Potential Duplicate](https://support.eulerapp.com/en/c/integrations/potential-duplicate)
- [Partner Portal Access](https://support.eulerapp.com/en/c/security-access/setup-administration/partner-portal-access)
- [Troubleshooting Partner Access Issues with POPS AI](https://support.eulerapp.com/en/c/ai-agents/troubleshooting-partner-access-issues-with-pops-ai)
- [Reviewing and Deciding on Partner Applications (MCP)](https://support.eulerapp.com/en/c/euler-mcp-customers/partner-applications)

### Sources for this page

- Forms 2.0 (Settings > Forms, form types, API Value, Test, Active toggle, Get Code, CRM requirement).
- Salesforce and Salesforce Integration: Data Flow (Integrations > Integrate, inherited permissions).
- Potential Duplicate (Proceed with Creation, Mark as Approved, Reject; Salesforce Lead rule).
- MCP connector reference: resolve\_partner\_application (what approval does, CRM-only exception), agreements\_manage (company signature), flows (Standard Flows).
- Change Log: portal lock until agreement signed (21 Feb 2025), skip partner invite email (19 Mar 2026). Referral Approval (Referrals to Approve).

### Next

- Gap 4: [Salesforce setup checks](05-salesforce.md). The decisions behind step 1 if you run Salesforce.
- Gap 8: [Referral statuses](09-statuses.md). What each status means after step 9.

---

*Independent writing sample by Bachtiar Widyantoro (bachwidy.site), November 2026. Not published or endorsed by EULER. Free to reuse and edit. Customer names in examples are fictional. Anything marked [VALIDATE ...] or [CONFIRM ...] is not settled by a public source and needs checking before publishing.*