The Harvest allows users within your org to convert incoming emails into Salesforce records. To provide access to Harvest for the users in your org, navigate to Setup and open Email Services.

1. Create an Email Service in Salesforce 

1. Navigate to Setup and in the Quick Find box, type Email Services and select it.
2. Click on New Email Service. Fill in the necessary information, including the name of the service and a brief description and in the Apex class choose EmailParserHandler.
3. Select All in Accept Attachments dropdown
4. Check the Active checkbox and click on Save
   

   

2. After that, open the email service you've created, and under Email addresses tab, click on New email address and create a context user:

    Email address name – record name, i.e. Email parsing.
    Email address – will be populated with Email service name.
    Active – must remain checked to enable user's activity .
    Context user – user for whom the functionality will be enabled.
    Accept emails from –  specific emails users will receive the inquiries from. By default, populated with the email address of the Context user. If provided, emails from only those mailboxes will auto create Record requests. To avoid potential issues, is suggested to be left blank.
 

3. Click on the Save button and repeat for each user who requires given functionality. 

4. On the Harvest Admin Console context users will appear under the Context Users tab (formerly named "Email Addresses"). This tab will allow for convenient copying of the corresponding addresses for each user. When you want to configure the forwarding rules for the users, or allow them to forward the emails for parsing ad hoc, copy the corresponding email addresses and provide users with them.

Click Manage context users on this tab to jump directly to the Email Service page in Setup (Step 2 above) if you need to add or edit a context user.

Each row shows a Status badge — Active or Inactive — for that email address, plus warning icons (hover for details) when the underlying Email Service needs attention:

• Error icon — the Email Service itself is inactive; emails sent to this address are not processed until it is reactivated in Setup.
• Warning icon — the Email Service's Accept Attachments setting is not set to All; attached files will not be parsed until it is.
• Info icon — the address (or its Email Service) restricts Authorized Senders; only emails from the listed senders are accepted.

5. Assign the appropriate permission set to each user who will use Harvest.

1. Go to Setup > Permission Sets.
2. Select Ascendix Harvest User (for end users) or Ascendix Harvest Admin (for administrators).
3. Click Manage Assignments > Add Assignments.
4. Select the users and click Assign.

Both permission sets give access to My Harvest Settings, where each user can choose their own AI model, edit their parsing instruction and object descriptions, and copy their Harvest email address. Admins who also forward emails for parsing can use it to keep their personal settings separate from the org settings in the Admin Console. See My Harvest Settings.

Note: An admin without the Ascendix Harvest Admin permission set sees the Org Settings tab of the Harvest Admin Console in read-only mode, with a message that explains how to assign the permission set.

6. (Optional) Let another user approve a broker's Record Request Sets.

By default, only the owner of a Record Request Set can approve its suggested records. To give a backup user (for example, an assistant, or a colleague who covers during vacation) the same approval rights without changing ownership, give that user Read/Write access to the Record Request Sets with standard Salesforce sharing:

• a sharing rule on the Record Request Set object (for example, share all sets owned by a broker with a public group that contains the assistant),
• a manual share on a single Record Request Set, or
• a public group used in either of the above.

The user then sees the shared Record Request Sets, with the owner shown, and can use Create All, Quick Create, Edit & Create, Review & Compare and Discard in the same way as the owner. See Salesforce documentation for how to create sharing rules.

Note: The backup user needs the Ascendix Harvest User permission set and access to the records Harvest creates (Accounts, Contacts, Properties and others). In most orgs this access comes from the xRE Broker permission set.