What are the Admin Settings?

Use Admin Settings to configure how Momentum connects to your CRM, manages email sync, and assigns donor portfolios to your fundraisers. Settings are organized into sections for general configuration, email suppression, background sync, data processing, and fundraiser assignments. 

Note: these settings are only available for users with Admin permissions, as changes here affect how Momentum logs communications and reflects donor data across your organization.

Table of Contents

1. Access
2. General Settings
3. Email Suppression
4. Background Email Sync Configuration
5. Sync & Processing
6. Fundraiser Assignments
7. Week in Review
8. Organization Group Assignments

Access

To access the Admin Settings, select the three lines in the top right from any page. Then click Admin Settings from the menu.

Here, you’ll find the six setting areas specific to admin. 

General Settings

General Settings define basic configuration for your organization.

These settings ensure Momentum aligns with your organization’s environment and data sources and include:

• Email domain: The domain name of your organization, used to validate allowed email addresses.  Enter the domain only (e.g. givemomentum.com).
• Timezone: Your organization's timezone. This determines when notifications are sent and how dates are displayed.
• Donor intelligence source: Select the source for donor intelligence data. Leave blank to disable.
• Donor interaction mode: Choose whether to work with donors individually or group them by household. This is only relevant for integrations with Salesforce of Virtuous CRM+. RE NXT integrations are always based on the individual.
• Household email default: When emailing a household, choose whether to email only the head or all members.
• Custom DonorSearch API key: If your organization has its own DonorSearch account, enter the API key here. Leave blank to use the default Momentum key.

Email Suppression

Email Suppression controls which emails should not be automatically logged in Momentum and your CRM. Email suppression is useful when certain Contacts or domains should not have all communications tracked and helps maintain clean and appropriate communication records. This suppresses emails for all users at your organization.

You can suppress individual email addresses or entire email domains. Common use cases include:

• Overlapping donor roles where all emails should not be logged (students, parents, or alumni) 
• Non-fundraising relationships (example: donors who are also contractors or consultants) 
• Sensitive communications (example: a donor may also be board member who helps oversee HR)

Background Email Sync Configuration

Background Email Sync Configuration controls how Momentum connects to your email client (Gmail or Outlook) and logs both inbound and outbound emails with donors back to your CRM. 

The Background Email Sync settings include:

• Disable background email sync (Outlook/Gmail): When checked, no emails will be synced via background sync for this organization.
• Record email actions for all constituents outreach: Log email actions for all constituents mentioned in the email, not just those in the sender's portfolio.
• Do not log actions for CC and BCC constituents in emails: Only log actions for constituents in the TO and FROM fields. Constituents in CC and BCC will be ignored.
• Only log actions for user's assigned constituents: Only log an email action if the sender is the assigned fundraiser for the constituent.
• Do not log actions to Momentum users' records in CRM: Do not consider Momentum users in the CC or BCC fields when determining who to log the email action for.
• Log actions that include CRM fundraisers who are not Momentum users: By default, if a fundraiser has a record in your CRM, Momentum skips logging email actions. Turn it on, and Momentum only skips the fundraisers who also have a Momentum login. For example, a board member set up as a fundraiser without a Momentum account would start getting notes logged.
• Do not log actions from non-CRM senders: When this is on, Momentum won't log an email action if the sender isn't a constituent in your CRM. It checks the From address against your CRM contacts and Momentum users; if it finds no match, the email action is dropped, and nothing is logged for anyone copied on it either. For example, a donor's assistant emails a fundraiser from her own work address and CCs the donor. If checked off, Momentum logs a note on the donor's record. With it on, nothing is logged at all, as the assistant isn't a CRM constituent.
• Default email action type: Action type assigned to email actions logged to your CRM via background sync. Select from action types synced from your CRM, or leave blank to not assign a type automatically.

How Background Sync Works 

Momentum reviews the email addresses of recipients and senders on all of your user’s emails, and matches an email from your Gmail or Outlook to a constituent record in your CRM. Then, Momentum logs the email back to your database. 

Email sync determines:

• what gets recorded in Momentum
• what gets written back to your CRM
• how complete your donor communication history is

Careful configuration for how your emails are logging actions helps balance visibility and privacy, while saving your fundraisers time and work. 

Sync & Processing

Sync and Processing settings control how data is pulled from your CRM into Momentum. These settings ensure Momentum reflects the most accurate and up-to-date donor information.

These settings include:

• Remove unassigned constituents on sync: If a constituent assignment is removed in the CRM during a sync, also remove them from the assignee's portfolio in Momentum.
• Auto-retry failed CRM pushes: Automatically retry failed attempts to push actions to the CRM as part of a recurring task.
• Ignore deceased constituents: Do not create or maintain fundraiser assignments for constituents marked as deceased in the CRM.

Fundraiser Assignments

Depending on your CRM integration, how you configure the Fundraiser Assignment section varies. To get started, select Use fundraiser assignment portfolios. Read more below for each CRM. 

Blackbaud

Once enabled, configure the Primary Fundraiser Mapping Value(s), and optionally the Secondary Fundraiser Mapping.

(Fundraiser) Type is the hard-coded field that syncs fundraisers from Blackbaud. If you have multiple Fundraiser Types, include all Custom Types separated by a comma in the Primary Mapping Value. Or, if all Fundraiser Types are the Primary fundraiser, you may leave this field empty to sync them all.

If you have Fundraiser Types that indicate the Secondary Fundraiser, add those custom Types to the Secondary Mapping Value field. Separate with a comma. A Secondary Fundraiser field is optional. Momentum prioritized recommendations for the Primary Assignment fundraiser. Secondary Assignment fundraisers can see Actions and the Plan for the Constituents, but Automations are run only for the Primary Fundraiser. If using Secondary Fundraiser, you must add custom Types in the Primary Fundraiser sync, as well. 

Salesforce

Once enabled, configure the Primary Assignment Mapping, and optionally a Secondary Assignment field:

• Select Contact Owner or Account Owner from the dropdown if your organization tracks assignments using these default Salesforce fields.
• Or, if your organization tracks assignments in a custom field instead, for example, Primary Relationship Manager, enter that field's name in the Primary Mapping Value. 

Note: Populate only one option per assignment: either the Primary Fundraiser Mapping dropdown or the Primary Mapping Value custom field name, not both. If you enter a Custom Field in the Mapping Value field, ensure the first Primary Fundraiser Mapping dropdown is left empty.

Whether Momentum reads these fields from the Contact record or the Account record depends on your organization's Donor Interaction mode. For Household First organizations, Momentum reads Custom Fields from the Account record. For Individual (Contact) First organizations (the default,) Momentum reads Custom Fields from the Contact record.

A Secondary Assignment field is optional. Momentum prioritized recommendations for the Primary Assignment fundraiser. Secondary Assignment fundraisers can see Actions and the Plan for the Constituents, but Automations are run only for the Primary Assignment. If using Secondary Assignment, you must use Custom Fields in the Primary Assignment sync, as well. 

Virtuous CRM+

Week in Review

Enable or Disable the Week in Review for specific users. Week in Review helps users reflect on and refine their donor interactions. It acts as a checklist that appears in the Inbox, surfacing meetings and calls from the past seven days so users can review notes, add additional thoughts, or confirm everything looks good. Learn more about the Week in Review here.

Organization Group Assignments: Virtuous CRM+

If your organization uses Virtuous CRM+, portfolio assignments are managed through Organization Groups. Click here to learn more about using Organization Groups.

To use Fundraiser Assignments in Momentum, Organization Groups must first be created in CRM+ and have Contacts assigned to their appropriate group. The Organization Groups are, then, mapped to fundraisers in Momentum. You can assign more than one team member per Organization Group if any donor relationships are shared between multiple fundraisers. Momentum uses this mapping to assign Portfolios. Portfolios are automatically updated in Momentum as Contacts are added or removed from the Org Group in CRM+.