Skip to content

Set up auto-saving emails in a thread for a profile

3 min read

Introduction

Revenue Grid allows users to automatically capture entire email conversations in Salesforce using the Auto-save all emails in thread feature. When a user manually saves one email from a thread with this feature enabled, all related emails—both past and future—are automatically saved using the same Salesforce records and values selected during the initial save. This ensures that important conversations with prospects or partners are captured consistently, especially in long or complex sales cycles.

This article is intended for Salesforce administrators who want to enable or disable this feature at the profile level in Revenue Grid. When enabled, all users assigned to the profile will follow the same conversation capture strategy.

Note

Once enabled or disabled at the profile level, individual users cannot override this setting.

For more details on how the feature works, see Save all emails in a thread explained.

Prerequisites for enabling auto-saving of emails in a thread for a profile

Before enabling auto-saving of email threads, ensure the following:

  1. You have admin-level access to the Revenue Grid Admin Panel.

  2. The user’s mailbox connection in the profile is initialized.

  3. If your Salesforce organization saves emails as Tasks (not as EmailMessage objects), either:

Add a custom Thread ID field in Salesforce

Skip this step if:

  • Your Salesforce org saves emails as EmailMessage records, which include the built-in ThreadIdentifier field.
  • The Revenue Grid managed package is installed, which automatically creates the required field.

Revenue Grid uses a Thread ID value from the first saved email to identify related emails in the same thread. This value must be stored in a specific field in Salesforce when emails are saved as Tasks.

  1. In Salesforce, click the gear icon and select Setup.

  2. In the Object Manager, select Activity.

  3. Go to Fields & Relationships and click New.

  4. Select Text as the data type, then click Next.

  5. Enter the field details:

    • Field Label: e.g., ThreadID
    • Length: 255
    • Field Name: Auto-filled depending on the field label, e.g., ThreadID__c

  6. Clear the Required and Unique checkboxes.

  7. Select External ID to allow referencing the field from an external system and click Next.

  8. Grant visibility to the profiles that will use the Sidebar and click Next.

  9. Clear the option to add the field to page layouts—it will be used internally only.

  10. Click Save.

  11. Go to the Fields & Relationships and copy the Field Name (e.g., ThreadID__c) for use in the Admin Panel later.

Enable auto-saving of emails in a thread for the profile

  1. Log in to the Revenue Grid Admin Panel.
  2. Go to the Profiles tab.
  3. Select the profile you want to configure.
  4. Under the Details subtab, scroll to the Sync section.
  5. In the Thread ID field:
    • Enter the field name (e.g., ThreadID__c) if you created a custom field.
    • Skip this step if you use EmailMessage objects or have the managed package installed.
  6. Enable the Auto-saving of emails in threads option.
  7. Click Save.
  8. Ask users to refresh the Sidebar to apply the changes.

Disable auto-saving of emails in a thread

  1. Log in to the Revenue Grid Admin Panel.
  2. Go to the Profiles tab and open the desired profile.
  3. Under the Details subtab, go to the Sync section.
  4. Disable the Auto-saving of emails in threads option.
  5. Click Save.
  6. Ask users to refresh the Sidebar to apply the changes.

Email thread auto-save not working — troubleshooting steps

If emails from a thread are not being auto-saved:

  • Confirm that the mailbox is connected and syncing for the affected user.
  • Verify that the Thread ID field was created and added correctly in Salesforce.
  • Ensure the field name in the Admin Panel exactly matches the Salesforce API field name (e.g., ThreadID__c).
  • Make sure the field is accessible to the user profile in Salesforce.
  • If you’re using the managed package, confirm it’s installed and active.

If you’ve confirmed all of the above and the issue persists, contact our support team for assistance.

See also