Configure Philanthropy Cloud · Philanthropy Cloud

Manage the settings for a workplace or organization in Settings. This includes the locale settings, currency settings, payment methods, volunteer settings, login settings, welcome email settings, and privacy settings. The Stripe account can also be connected.

Note: Based on organization preferences or your user role, some Philanthropy Cloud features may not be available.

Important: Processors cannot process donations until the Stripe account is connected (see Stripe Connect) and the Tax Receipts and Pledge Confirmation Emails are configured.

Important for WAMs:

WAMs must make sure that they're in the right workplace context before performing any tasks. Functionality may differ based on workplace context and the associated privileges for that site.
WAMs can switch between the workplaces they administer and the context of their own organization, which itself may be a workplace. To switch between workplace contexts, enter the name of the workplace or organization in the Search field located in the toolbar.

Connect a Stripe Account to Philanthropy Cloud

Note: For Processors only.

In order for a workplace to enable employee donations, their processing partner ("Processor") must have an active Stripe account connected. Each organization that processes transactions for a customer must connect a Stripe account to the Philanthropy Cloud environment. You may use an existing Stripe account or you can create a new one.

If you need to create a Stripe account, visit https://dashboard.stripe.com/register to begin the account creation process. You must enter your bank account information and activate your account before proceeding.

Important for Processors: Processors cannot process donations until they connect a Stripe account to Philanthropy Cloud and Configure Tax Receipts and Pledge Confirmation Emails.

To connect a Stripe account to Philanthropy Cloud:

Select Settings.
In the Stripe Connect section, select Not Connected. You're redirected to Stripe's website, where you'll sign into your existing Stripe account.

Important: Do not create a new account through this page.
After you log into your Stripe account and authorize the connection request, you return to Philanthropy Cloud. The Settings page indicates a successful connection.

You are now ready to process donations.

Every credit card donation in Philanthropy Cloud is reflected as a Payment in Stripe. Each payment's metadata contains unique information from Philanthropy Cloud, including the Donation ID. This ID is available through the Donation API for Processors to match against.

Locale Settings

The default locale settings apply to all new users until they customize their profile. This setting can also be changed on a per user basis using a CSV file.

To set the locale settings for a workplace or organization:

Select Settings.
In the Locale Settings section, select the Default Locale and the Default Time Zone.
Select Save.

Currency Settings

The default currency applies to your entire organization or workplace. Reports use this currency setting.

Users also default to this currency setting until they customize their profile. This setting can also be changed on a per user basis using a CSV file.

To set the currency for a workplace or organization:

Select Settings.
In the Currency Settings section, select your Currency.
Select Save.

Payment Methods

Select the available payment methods for your organization or workplace. When creating campaigns, you can choose which of these payment methods to include.

When Payment Methods and Payroll Giving Configuration settings are changed, Organization Administrators, Processor Organization Administrators, and WAMs are notified via email to ensure that the new settings are correct and are processed correctly.

Important: Processors cannot process donations until the Stripe account is connected (see Stripe Connect) and the Tax Receipts and Pledge Confirmation Emails are configured.

To select the payment methods for a workplace or organization:

Select Settings.
In the Payment Methods section, select Cash, Check, Payroll, and/or Stock. Selected payment methods are available for all donations. Campaigns can additionally restrict payment methods.

Note: Credit card donations are always enabled. Cards supported include most major brands, such as Visa, Mastercard, and American Express. The full list of supported cards is determined by the credit card processor.

Note: You must configure the Payroll Giving Configuration section when payroll is selected.
Select Save.

Payroll Giving Configuration

Configure payroll and bonus payroll giving for your workplace when payroll is one of your selected payment methods.

Recurring payroll settings must be configured to enable one-time and bonus payroll giving. One-time payroll giving must be configured to enable bonus payroll giving. Additionally, payroll-related fields must also be enabled for users to complete the payroll and bonus payroll configuration process. To disable one-time payroll giving, bonus payroll must be disabled.

Impact totals for recurring payroll donations are calculated per the number of pay periods for that organization and increment per pay period. The payroll deduction occurs every pay period on or around the same date. For example, an organization could have 24 pay periods per year, and the end of the month could change per the month.

To configure one-time and bonus payroll payroll giving:

Select Settings.
In the Payroll Giving Configuration section, select Recurring.
For annual payroll donations:
1. Select Annual. Annual payroll donations continue for a year from the Payroll Deduction Start Date and must be renewed each year. Annual payroll donations can be made during a fixed enrollment period.
2. In the Fixed Enrollment Period section, enter an Enrollment Start Date and Enrollment End Date. Users can begin new recurring payroll donations within this specified time window each year.
3. Enter a Payroll Deduction Start Date. The Payroll Deduction End Date is one year from the Payroll Deduction Start Date.
For perennial payroll donations:
1. Select Perennial. Perennial or continuous payroll donations only end when an employee cancels their gift or leaves the company. Perennial payroll giving can be configured with either a fixed enrollment period or a continuous enrollment period.
2. For a continuous enrollment period where an employee can initiate new recurring payroll deductions at any time, select Continuous. Payroll deductions start immediately.
3. To establish a limited time window each year when employees can initiate payroll deductions, select Fixed. Then enter an Enrollment Start Date, an Enrollment End Date, and a Payroll Deduction Start Date.
To enable one-time payroll donations:
1. In the Payroll Giving Configuration section, select One-Time.
2. Select Enabled.
3. Select a one-time payroll option:
  - Always - one-time payroll deductions are enabled at any time of year.
  - Date Range - one-time payroll deductions are enabled during a specified enrollment period only. Enter Start and End dates. The Date Range cannot be longer than 90 days.
4. Set the user record values for Annual Pay Periods. Payroll Deduction is enabled by default. You can manage users individually or using a CSV file in User Management. For more information, please refer to the Data Dictionary.
To enable bonus payroll donations:
1. In the Payroll Giving Configuration section, select Bonus Payroll.
2. In the Bonus Payroll Schedule section, select Enabled.
3. To schedule a bonus payroll for donations, enter a Payroll Date and a Cutoff Date.
  
  Donors can give from a bonus payroll up to the cutoff date. Bonus payrolls in the current and next calendar year are displayed to the end user.
  
  Note: The Payroll Date and the Cutoff Date must be in the future (after today’s date), and the Cutoff Date must be before the Payroll Date.
4. Select Add. Up to ten bonus payroll dates can be scheduled.
5. You can edit scheduled bonus payrolls in the Scheduled table that don't have associated pledges. You can also archive them by changing the cutoff date.
6. Enable the user record values for Bonus Payroll. You can manage users individually or using a CSV file in User Management. For more information, please refer to the Data Dictionary.

Volunteer Settings

Organization administrators and champions can create and manage volunteer opportunities and campaigns. Then users can sign up for volunteer opportunities, log time, view their volunteering history, and select their volunteer skills.

Volunteering is enabled by default. To disable or re-enable volunteering for your organization:

Select Settings.
In the Volunteer Settings section, select or deselect the Volunteering Enabled/Disabled toggle.

Before volunteering is disabled, organizations with active volunteer opportunities must either submit a support ticket or manually cancel all scheduled and published volunteer opportunities. To submit a support ticket, select submit a ticket.

When volunteering is re-enabled, users must refresh the application to access its features.

Social Visibility Settings

When social visibility is enabled and users view a volunteer opportunity, they see the names and profile pictures of others in their organization or community who signed up.

Important: Your organization is responsible for obtaining consents and complying with all applicable laws.

To enable social visibility:

Select Settings.
In the Social Visibility section, select Social Visibility Enabled.

Login Settings

Organizations can configure flexible policies for user logins. Select a default login method for your organization’s users. These settings only apply to newly created users and are not retroactive.

Organizations with SSO enabled can specify a default login policy for all users. When administrators leave these values blank for users individually or using a CSV file in User Management, user values are inherited from the organization defaults.

Username/Password & Single Sign-on (SSO) - Allows users to use Single Sign-on and use a Philanthropy Cloud-issued username/password in addition to SSO.
Single Sign-on (SSO) only - This value restricts users to use Single Sign-on only for logging into the application. If enabled for an organization, it applies to all users.

Administrators can override organization defaults and specify Login Settings on a per user basis. You can manage users individually or using a CSV file in User Management. For more information, please refer to the Data Dictionary.

Login Settings	User CSV File	User can log in using...
Username/Password & SSO	Username_Password	SSO or Username/Password
Username/Password & SSO	SSO Only	SSO Only
Username/Password & SSO	Blank	SSO or Username/Password
SSO Only	Username_Password	SSO Only
SSO Only	SSO Only	SSO Only
SSO Only	Blank	SSO Only

Note: To enable SSO for your organization, please contact Philanthropy Cloud Support.

Welcome Email Settings

Select the default value for how users receive welcome emails.

Default settings apply only to newly created users. Changes made to these settings do not affect users who have already logged into Philanthropy Cloud.

Welcome email settings can also be set on a per user basis. You can manage users individually or using a CSV file in User Management. For more information, please refer to the Data Dictionary.

Username/Password

For users who log in with a username and password, choose from these welcome email settings.

Send immediately: When creating a new user, Philanthropy Cloud immediately sends a welcome email that includes a link for the user to log in and set their password. The link provided is only for the initial sign on.
Defer until first login: When creating a new user, Philanthropy Cloud does not send a welcome email. You can create a personalized welcome email and manually send it from your organization. The only requirement is that you include a link to Philanthropy Cloud (https://philanthropycloud.com) in the email so the user can access the application. When the user visits https://www.philanthropycloud.com for the first time, they receive an email to validate that this unauthenticated web visitor actually holds an email address matching a user on record. If the user has a Philanthropy Cloud username and password enabled, the email contains a link to set their password.

Single Sign-on (SSO)

For users who log in with SSO, choose from these welcome email settings.

Send immediately: When creating a new user, Philanthropy Cloud immediately sends a welcome email with a link to the Philanthropy Cloud Home page, where the user is prompted to log in with their SSO credentials.
Never send: Philanthropy Cloud never sends welcome emails. This option is only available for SSO users, since a welcome email is required to set a username and password.

Privacy Settings

Provide links to your Privacy Policy and Data Subject Access Request (DSAR) form to comply with CCPA/GDPR requirements. Users can access your forms using these links.

Note: When both a workplace and its WAMP provide links, users see links to both forms.

Privacy Policy

Provide a link to your privacy policy that displays in your site footer.

Note: When both a workplace and its WAMP provide links, users see links to both forms.

To display a link to your privacy policy:

Select Settings.
In the Privacy Settings section, enter your Privacy Policy URL. It must start with http:// or https://.
Select Save.

Data Subject Access Request

Provide a link to your Data Subject Access Request (DSAR) form that users access from their profile.

When users access your DSAR form, their Salesforce Philanthropy Cloud IDs are appended to the DSAR request URL. For example, “https://.../dsar_request_page?SPCID1234567”.

Note: When both a workplace and its WAMP provide links, users see both links.

To display a link to your Data Subject Access Request form:

Select Settings.
In the Privacy Settings section, enter your Data Subject Access Request URL.
Select Save.

Workplace Account Management Partners

Note: For WAMPs and WAMs only.

Workplace Account Management Partner (WAMP) and Workplace Account Manager (WAM) information appears on the Settings page in a workplace context.

WAMPs are organizations that manage workplaces. WAMPs can assign WAM roles to their employees. Workplaces cannot assign or remove WAMs directly. For information on assigning roles, see Assign User Roles in User Management.

WAMs have full site access to administer workplaces they are managing. WAMs can also customize their own Philanthropy Cloud user profiles. There are some actions that can only be performed for the workplaces that WAMs administer and not within the context of their own organization, and vice versa.

Important for WAMs:

WAMs must make sure that they're in the right workplace context before performing any tasks. Functionality may differ based on workplace context and the associated privileges for that site.
Content that WAMs create in the context of a workplace is only available to that workplace. To add stories that can be accessed by any workplace, create them in the context of a WAMP.
WAMs can switch between the workplaces they administer and the context of their own organization, which itself may be a workplace. To switch between workplace contexts, enter the name of the workplace or organization in the Search field located in the toolbar.

Email Configurations

You may need to configure network and email settings to ensure emails from Philanthropy Cloud are delivered in a timely and secure manner. The following systems send transactional emails related to Philanthropy Cloud. Philanthropy Cloud does not currently send any marketing emails that would require explicit user opt-in.

Login Messages

Philanthropy Cloud uses standard Salesforce email infrastructure to generate emails relating to the login process, such as welcome emails and password reset emails.

Salesforce email is DKIM signed using the key at: `prod._domainkey.philanthropycloud.com` but originates from `salesforce.com`.

For more information and a complete portfolio of Salesforce.com IP addresses and domains, see Salesforce IP Addresses and Domains to Allow.

Notification Messages

Philanthropy Cloud uses its own email infrastructure to send notification messages that are not related to the login process, such as tax receipts and confirmations.

All emails go out on a dedicated static IP address with Mailgun (159.135.227.76).
Production email is sent from the domain `mail.philanthropycloud.com`.
Partner and demo emails are sent from `partner.mail.philanthropycloud.com`.

For maximum deliverability of both login-related and notification email messages, be sure you allow `mail.philanthropycloud.com` and `salesforce.com` when DKIM verification passes.

Password Link Expiration

If your organization has email security software that causes a password reset link to expire, request a new password or contact the email security software support team to have them allow emails coming from Salesforce. For more information, see Salesforce 'Reset Password' link is expired.

Configure Tax Receipts and Pledge Confirmation Emails

Note: For Processors only.

Tax receipts are issued differently based on the payment method used for the donation. Tax receipts also vary per country.

For all credit card donations, Philanthropy Cloud automatically sends donation confirmation emails with tax receipts as PDF attachments.

For cash, check, and stock pledges, Philanthropy Cloud sends pledge confirmation emails. Processors follow up with payment information and issue tax receipts when the pledged donations are fulfilled.

For payroll pledges, donors can use the appropriate pay stubs as their tax receipts, since charitable deductions are indicated on their pay stubs.

You can create and preview the email messages. You can also send sample emails as required.

Note: Based on organization preferences or your user role, some Philanthropy Cloud features may not be available.

Important for Processors: Processors cannot process donations until they Connect a Stripe Account to Philanthropy Cloud and configure Tax Receipts and Pledge Confirmation Emails.

To configure a tax receipt or a pledge confirmation email:

Select Receipts and Confirmation Emails.
Select the appropriate tax receipt or pledge confirmation email to configure: Tax Receipt, Payroll Deduction, Stock Pledge, Cash Pledge, or Check Pledge.

Important: Configuring payroll deduction, stock pledge, cash pledge, and check pledge confirmation emails is optional. However, if these emails are not configured, their corresponding donation options are not available to customers, even if the payment methods are enabled.
Enable the payment method as required.
In the Logo section, drop an image file in the appropriate area or select Browse.

The optimal size for an image is 70px high by 150px wide. Supported file formats supported are .jpg, .gif, .svg, and .png. The maximum file size is 5MB. Philanthropy Cloud automatically scales and pads your image.
To use the same logo for a pledge confirmation email as the one used on the Tax Receipt, select Use Tax Receipt Logo.
In the Body Content section, enter plain text only. Use this section to say thank you, provide information about how you will follow up to collect the pledge, or share other marketing content.
In the Contact Information section, enter plain text only. Use this section to provide contact information in case a donor has a question about their gift, or other concerns.
Preview a summarized view of the content in the Preview section.
To send a sample tax receipt, select Send sample receipt email.
To send a sample pledge confirmation email, select Send sample confirmation email. Enter an Email Address and select Send. A confirmation email is sent to the addressee.