Automated onboarding with FundSub (Primary Investor + Collaborators) [Multi-funds]

1. Purpose

Enables customers to initiate 1-click investor invitations to FundSub directly from Salesforce. Using Salesforce data, subscriptions are automatically prefilled - ensuring investors and their collaborators can start with a partially completed form, reducing friction and manual entry.

---

2. Key Benefits & Features

• Eliminate manual onboarding with a single click inside Salesforce
• Ensure a seamless investor experience through automatic Salesforce → FundSub data transfer
• Extend invitations beyond investors to include associated collaborators

---

3. Potential Customer Personas

• Valuable for any FundSub customer using Salesforce as their CRM
• Especially helpful for firms aiming to prefill large portions of investor subscription forms via Salesforce
• Especially helpful if firms work with large investor teams and need to invite multiple participants

---

4. Prerequisites

4.1 Third party app requirements

• Connected app
  • Understand the concept: Defines how external applications (like Anduin) connect to Salesforce, using OAuth. Includes client ID/secret, scopes, callback URLs, etc.
  • Credentials: Customers must create a Connected App and provide the necessary credentials during setup.
  • Permissions: Ensure the Connected App has the right scopes to allow the integration to access and send data.
  • Session Limits: Salesforce allows only 5 active sessions per Connected App. If the limit is reached, the customer must create a new Connected App.
• Invoke flow
  • Screen Flow: A point-and-click automation that guides users through predefined actions. Customers must build a screen flow to programmatically interact with Anduin's FundSub invitation flow.
  • Custom Button: A button in Salesforce UI that triggers the screen flow. Buttons + flows = clean, guided experience.
• Object preparation
  • Subscription Object: Customers should prepare a consolidated object containing all the data intended for transmission to Anduin.
  • Contact Object: Customers also need to prepare an object listing all contacts who will be invited to Anduin. This contact object should include:
    • A unique identifier from the Subscription object (e.g., Opportunity ID) to link contacts to their respective subscriptions in Anduin.
    • A contact type field indicating whether the person is a Collaborator or Primary (only these values are accepted).

4.2 Anduin app requirements

• Fund access - the user must either:
  • Have admin access to the intended funds, or
  • Know a team member with admin access who can grant the necessary permissions during setup
• Data transfer
  • Data & Mapping: Identify what Salesforce data will be used and how it maps to FundSub fields
    • Clarify if it’s 1-to-1 mapping or requires transformation logic
  • Import Templates: depending on the exchanged data points and how it is mapped, the corresponding import templates will be recommended
    • Anduin Standard Alias (ASA)
    • Custom Templates

🚧

Note

⚠️

Template Setup

1. Single-Fund Integration
   ✅ No constraints — integration can proceed without special requirements.

2. Multi-Fund Integration
   Depends on the chosen template method:

   • ASA Route
     ✅ No constraints — just ensure the ASA is mapped to all intended funds.

   • Custom Template
     🔹 All template names must be consistent across funds. This enables the correct picklist option in configuration.
     🔹 Each template must include the required data points for its respective fund.
     🔹 Templates do not have to be identical — content can vary, but the template name must match.

---

⚙️

How the Integration Works

• When triggered, the integration looks up the configured template name per fund.
• Data is pulled from Salesforce source records:
  • If template content is identical across funds → Salesforce schema and template are the same.
  • If template content differs → Salesforce should be a union of all templates, ensuring compatibility across funds.
• The template defines which data points are prefilled. The integration maps Salesforce data based on each fund’s selected template.
• The subscription is then created with prefilled data and invitation gets sent

---

5. Pre-Setup Checklist

---

6. Internal Step-By-Step Rollout Guide

6.1 Grant access to the Integration Hub

• Customers need to contact their Implementation manager to ensure they have access to the Integration Hub and this integration

6.2 Locate the solution

• In the Browse tab of the Integration Hub, the customer can locate the Salesforce (Order creation) - Multiple Contacts solution

  

6.3 Install the solution

• Step 1: Click Install to begin setup

  

• Step 2: Name the Integration

  • Recommend a clear and descriptive name (e.g., “Salesforce integration - Fund Alpha” or “By John Smith”)
  • Click Next: Link to Anduin objects

• Step 3: Grant integration permission to customer’s intended objects (funds)

  • Step 3.1: A list of accessible Anduin objects (e.g., Funds) will appear
  • Step 3.2: Click Open next to the relevant fund
  
  • Step 3.3: In the permission module, find the integration name and click Add
  
  • Step 3.4: Return to the Integration Hub - the fund should now show a “Linked” tag
  

🚧

If the target fund is not listed, there are 2 options

1. Customer needs to be added with admin role for that fund, then return to the step 3.2. Customer should be able to see the target fund there
2. Customer requests their team member who has admin role in that fund to perform step 3.3 using Settings > Integrations in the FundSub app and they can continue with step 3.4

6.4 Configure the solution

• The customer may rename the integration or proceed as-is

  

• Enter Connected App credentials

  

• Select the Anduin fund this integration should work with. Can select multiple funds.

  

• The customer can specify the data template which will define the prefilled data points. There are 2 types of template

  • Anduin standard fields - contain only limited data points
  • Custom template - contain as many data points as they desire with complex computation as needed.

• They also need to tell us the Salesforce object which is used to push data to Anduin for order creation and data prefill

  

• Additionally, they need to specify the Salesforce object which compiles all of contacts that are meant to be onboarded in Anduin

  

• This step configures which Salesforce fields map to which FundSub template fields

  • Left column (Salesforce field) - data points listed in the Salesforce object they specified before
  • Right column (Anduin template field) - data points listed in the Anduin template they specified before

  🚧

  Note

  1. Single-Fund Integration
     ✅ Mapping is straightforward with one-to-one mapping.

  2. Multi-Fund Integration

     • If the template content is identical across funds, the mapping is also straightforward since all prefilled data is the same.
     • If the template content is not identical across funds, the data to be prefilled will vary per fund.
       → In this case, this centralized mapping interface should support a mapping matrix that accounts for each fund's unique structure.

  

• To successfully send out the invitation, customers need to specify more in the Contact object

  • Which fields represent First name, Last name, Email so we can send invitations accordingly
  • Which field represent the association with the Subscription object so we can identify and add members accurately
  • Which field represent the contact type so we add them to the correct role
  

• Additional invitation logics can be configured

  • Add additional contacts to an existing subscription in Anduin
  • Remove contacts from a subscription in Anduin upon detecting the outdate in Salesforce
  

6.5 Validate the solution

Once configuration is complete:

1. The customer should trigger the Salesforce screen flow via the custom button they previously created
2. This will initiate the integration, resulting in:
   • A new subscription order being created in the target Anduin fund
   • The order being prefilled with mapped Salesforce data
   • An investor invitation email being sent, using the email field provided
   • Corresponding collaborators will be added to that same subscription with invitations sent

If the automation works end-to-end, the setup is successfully validated.