CommunitySuite Release Notes 2026

Monthly Release Features are listed with a Monthly Release: [Date] heading and have links to relevant resources. Other enhancements/fixes are listed with a Product Enhancements: [Date] heading.

June 2026

Monthly Release: June 3

Pledge/Promise Online Creation

CommunitySuite clients needed a way for donors to initiate a pledge or promise online without staff intervention. Rather than building a standalone pledge form, the existing donation flow on the Giving Hub and Portal was extended to support pledge or promise submissions, keeping the donor experience consistent and giving foundations control over which options are available to their donors.

Key Benefits

• Donors can commit to giving directly through the Giving Hub or Donor Portal without contacting foundation staff.
• Foundations can manage pledge and promise pipelines online rather than entirely through staff data entry.
• Automatic staff notifications and donor acknowledgment emails reduce manual follow-up.
• Pledges and promises submitted online are automatically posted, reducing extra steps for staff and removing barriers for donors (enabling donors to make their first payment without staff intervention).
• Configurable button labels and acknowledgment content let foundations match the form to their brand and donor communications.

Online Pledge and Promise Submission via Giving Hub and Donor Portal

Site-wide setting to enable form: In Portal Options → Giving Hub Settings → Donate → Enable Pledge/Promise Form to enable the form on the Giving Hub. In Portal Options → Portal Settings → Donor → Enable Pledge/Promise Form to enable the form on the Portal. The form allows the foundation to accept pledges or promises. Promises are enabled by default. To change this, navigate to Money In → Pledges/Promises → Settings → Pledge/Promise Form Type and select between Pledge and Promise in the drop-down menu. This is a site-wide setting and affects both forms. If an admin changes the site-wide setting, existing records are unaffected

Donors can submit pledges or promises within the existing donation flow on the Giving Hub (and/or Portal). There is automatic creation of the pledge or promise record in CommunitySuite, with profile matching following the same logic as new donations. Pledges can now be converted to Promises (and vice versa) if the status is new (unposted/uncommitted). Navigate to the relevant pledge, and select Convert to Promise in the left-side menu. Navigate to the relevant promise, and select Convert to Pledge in the left-side menu.

Automatic staff email notification on submission can be configured in Portal Options → Portal Notifications. Configurable donor acknowledgment email can be managed in Pledges/Promises → Content → Pledge Form Acknowledge Email Subject and Pledge Form Acknowledge Email Body. Pledges and promises submitted from the Giving Hub and Donor Portal are automatically posted. This enables donors to immediately make a pledge payment without waiting for staff to post their pledge/promise.

Customizable button labels for the pledge/promise option are available, as some donors may not be familiar with pledges or promises. Manage this option in Portal Options → Giving Hub Settings → Donate → Pledge/Promise Form Button Label. Customizable content above the pledge form is available to include special instructions and/or details about the purpose of the form. Manage this option in Portal Settings → Giving Hub Content → Pledge → Public Pledge Form Content. Customizable thank-you content shown after form submission on the Giving Hub can be configured in Portal Settings → Giving Hub Content → Pledge → Public Pledge Form Submitted.

 

Resources:

• Enable and Submit Online Pledges and Promises
• Pledges/Promises Settings
• Customize Pledge/Promise Content

---

May 2026

Product Enhancements: May 29

Fund Import: Updated the Fund Import to accept account number for the cash account field instead of the internal account ID, which is not visible in the UI. This aligns with other imports such as Journal Entry, Voucher, and Invoice.

2 Factor Authentication / Password Reset: Resolved an issue where users who had set up 2FA via an authenticator app could get stuck in a login loop when attempting to reset their password.

Historic AP / AR: Resolved an issue where the payment year columns on the Historic AP and Historic AR reports applied the fiscal year offset in the wrong direction, causing payments to display under the incorrect fiscal year for foundations with a fiscal year offset from the calendar year.

Due Diligence Charity Check: Made an update so that boolean fields in results are displayed as 1 or 0 instead of Yes/No. Resolved an issue where the Charity Check Log link was no longer visible on the Grantee record for sites not using Due Diligence. Updated Due Diligence results for Canadian organizations to exclude US-only fields and data sources for clarity, and renamed the 509a column header to Additional Classification. For Canadian grantees, the Additional Classification column pulls in CRA Category data.

---

Product Enhancements: May 27

Donation Import: Updated Donation Import instructions to align with column headers in the import file template.

Financials: Resolved an issue where running a financial report for a zero-dollar fund with "Include Zero Balances" enabled would return a critical error. The report now generates successfully for zero-dollar funds with this option selected.

---

Product Enhancements: May 19

Donor Portal: Updated the donor portal so that donation advisors can view details of donations where they are listed as an advisor (excluding tax receipts, which remain visible only to the donor). Previously, clicking into an advised donation displayed a "This is not your donation" error message.

---

Product Enhancements: May 15

Print Page: Resolved an issue where using Print Page on a report after scrolling down the page caused duplicate headers to appear mid-printout and report results to appear out of order or skip ahead.

Due Diligence: Resolved an issue where grantees created from grant requests submitted through the Portal were not including the EIN. Additionally, the portal grantee profile search now requests up to 500 results (previously defaulted to 100), and results are paged consistently with internal database search results. Note: Additional information, such as street address, does not carry over to the Grantee profile at this time.

Workato: Resolved an issue where Workato connector events could fail intermittently when triggered during profile creation.

Custom Reporting: The following fields are now available in Custom Reporting for check records: Check Address, Address 2, City, State, Zip Code, Country, and City/State/Zip. These fields reflect the address from the check record, allowing staff to accurately report where payments were sent.

Profiles: Added a "Login As" search from the main Profiles list page under Login Log. Users with the existing "Login As" permission can now search for and log in as a profile directly from this page, reducing the number of clicks compared to the previous workflow.

Budgets: Resolved an issue where selecting "Copy Last Year's Budget" when creating a budget would flash and fail, or display a "no previous year" message, even when a budget for the previous year existed. This occurred when the site's fiscal year start date didn't align with the date the previous year's budget was created. For example, if the fiscal year setting had changed since the budget was made, or if a budget had previously been created and deleted. The system now finds the most recent budget from the prior fiscal year rather than requiring an exact start date match.

---

Product Enhancements: May 14

Grants: Resolved an issue where a donation notification email was sent for a donation that was never created. This occurred when posting an internal grant from a fund with no grant approvers: the system initiated the post process before checking for approvers, sending the notification before rolling back the failed post. The approver check now runs before the post is initiated, preventing notifications from being sent for grants that cannot be posted.

ABA Files: Resolved an issue where generating an ABA file for direct debit donations returned a generic platform error when the Financial Institution Abbreviation (FIA) field was empty on the associated bank account. The system now validates the FIA field before attempting to generate the ABA file and displays a clear "Financial Institution Abbreviation (account)" error message, making the issue easier to diagnose and resolve.

---

Monthly Release: May 13

Org Profile Compliance

A new Foundant-native Due Diligence check is now available in addition to the existing Candid/GuideStar Charity Check. Due Diligence pulls compliance data directly from Foundant's data lake (IRS BMF, Pub78, 990 filings, OFAC) and surfaces it natively in CommunitySuite. Users can choose, via a checkbox in Grants Settings, whether to use the Foundant Due Diligence check or continue with Candid. Both check types and their acknowledgments appear in a single unified diligence log.

This release gives users the option to replace the Candid charity check with native compliance data refreshed daily (monthly for Canadian data). This is particularly for users who want to see more up-to-date data, and/or want to align their Compliance data with Grant Lifecycle Manager (GLM). 

Key Benefits

• Native compliance data in CommunitySuite, sourced from IRS and OFAC, refreshed via daily ingestion.
• Site-wide choice between Candid and Foundant Due Diligence.
• Unified diligence log so reviewers see both Candid and Due Diligence history in one place.
• Audit log entry captured when a Due Diligence check is acknowledged from a grant.

Foundant Due Diligence Check on Grantees and Across the Grant Approval Workflow

There is a site-wide option in Grant Settings to choose which compliance check runs. If multiple are selected, the hierarchy that takes priority is Due Diligence > Candid or Grant Connect. For Due Diligence Checks, Charity Verified ="bmf_status": true, "pub78_verified": true, "currently_revoked": false, "ofac_found": false. If any of these fields fail, the organization will fail the due diligence check.

Bmf_status indicates the organization is in the IRS Business Master File (the master list of all tax-exempt organizations). Pub78_verified indicates the organization is eligible to receive tax-deductible charitable contributions (listed in Publication 78). An organization can have tax-exempt status (bmf_status: true) but not be eligible for deductible donations (pub78_verified: false). For example, social welfare organizations 501(c)(4) are tax-exempt, but contributions to them are not tax-deductible. "Currently_revoked: true" means the organization has lost its tax-exempt status, typically for failure to file required Form 990 returns for three consecutive years (automatic revocation). This data comes from the IRS Auto-Revocation List. "ofac_found: true" means the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) has identified a person, organization, or entity as a national security, foreign policy, or economic threat - and U.S. persons (including foundations and grantmakers) are legally prohibited from doing business with them.

 

Both the single-grant and bulk flows function the same way, and the charity check interval still functions the same. The only change is the data source/displayed and the actual check run.

Single-grant flow: Run a Due Diligence Check directly from a grant record, with grant pages displaying the relevant compliance fields and a "Last Due Diligence Check" timestamp that shows all relevant compliance fields.

Bulk flow: "Due Diligence Check All" - action extended to support running Due Diligence checks in bulk.

Portal: Search results in the Portal are powered by the Org Profile service instead of Candid when the settings is enabled. Search results are sorted by “last modified date” (effectively the most recently updated organizations).

Sources & publish dates: Displayed alongside check results.

Acknowledge by / timestamp: Captured in the diligence log.

Terminology updates: Column headers, button labels, and permission references updated to reflect "Due Diligence" alongside existing "Charity Check" language.

 

Resources:

• Enable and Run Due Diligence
• Grantees Permissions
• Grants Settings

---

Grant Import Improvements

We are expanding the grant imports functionality. Users can now bring grants into CommunitySuite with a full payment schedule already attached instead of opening each grant after import to set the payment date. A separate import is also now available for internal (fund-to-fund) grants, allowing organizations that process high volumes of interfund transfers to import them in bulk instead of creating them one at a time.

Payment Schedule and Internal Grant Import

Added First Payment Date, Payment Frequency, and Number of Payments to the grant import template. If only the First Payment Date is provided, a single payment is created on that date; if all three fields are populated, a full payment schedule is generated. Existing imports with these columns left blank behave as they do today.

Grants → Import: New columns for First Payment Date, Payment Frequency, and Number of Payments.

Validation: First Payment Date required if a schedule is being created; Number of Payments ≥ 1; Payment Frequency required when Number of Payments > 1.

Resource:

• Import Grants

---

Portal Grantee Donations Export

Grantees logging into the portal can now bulk-export all donations attached to their grants. This is particularly useful for grantees that need to download donor and donation information for grants received through the Grant Catalog or donations from the Nonprofit Directory. Previously, grantees had no way to perform a bulk export of donation details and had to navigate into each grant to export its details one at a time, which was an operational burden for high-volume organizations. This export combines the data from the exports currently available on the Grantee Portal and the Grant tab, where a specific grant is selected.

This exports donations attached to the grantee's grants, not donations the grantee themselves has made.

Export Donations

The Export Donations action is available on the portal grantee summary page that exports all of the grantee's grants and their associated donation details into a single CSV file. The export uses one row per donation and includes all data currently available in the grant and donation exports that the grantee has access to. Grantees can apply a date range filter before running the export to scope the results.

Export details are listed below:

• Bulk export of donations attached to grants in a single CSV, replacing the per-grant manual export workflow.
• Date range filtering so grantees can pull only the records they need (e.g., for fiscal year reconciliation).
• Particularly valuable for Grant Catalog and Nonprofit Directory recipients who receive multiple public donations.
• Only grants with attached donations will export in this.

Resource:

• Portal Setup and Configuration

---

Captcha Hardening 

As part of ongoing security enhancements, we have tightened how CAPTCHA validates the hostname of incoming traffic. Stricter hostname checking helps block bad actors from spoofing your site.

Key Benefits

• Stronger protection against CAPTCHA bypass attempts that rely on hostname spoofing.
• Continued support for customers who legitimately proxy CommunitySuite traffic (e.g., for translation or alternate domains).

---

Product Enhancements: May 8

Portal 2FA Setup: Resolved an issue where the Two Factor Authentication setup screen for portal users listed inactive email addresses and phone numbers alongside active ones. Only active email addresses and phone numbers are now shown when a portal user sets up Two Factor Authentication.

Donations: Resolved an issue where a portal user could donate to a private fund through the giving hub and enter any name as the donor, creating donation records on funds that should not have been accessible to the public. Private fund access and donation routing in the giving hub are now consistent for all users regardless of login state. Fund advisors can still donate to private funds through the portal when staff enables the Enable Advisor Donate Button on the relevant fund.

Fund Advisor - Grant Catalog: Resolved an issue where the grantee name on a Grant Catalog grant request could be lost when a fund advisor edited the request from the cart, causing the request to fail to save. The originally selected grantee is now preserved through editing and submission.

Donor Report: Resolved an issue on the Donor Report where the [ALL] and [Fiscal] year presets on the Donation Date filter behaved inconsistently when a financial offset was configured. The [ALL] preset now reflects the calendar year, and the [Fiscal] preset reflects the fiscal year with financial offset (if set in system settings).

Profiles - Do Not Mail: Resolved an issue where marking a profile as Do Not Email cleared the profile's primary email address from the profile record, causing email data to be missing or blank across reports, exports, statements, template fields, and donor management screens. It also suppressed system-generated emails such as tax receipts, pledge acknowledgements, fund request acknowledgements, grant card receipts, advisor reminders, opportunity letters, and Resend Guest Link bulk actions.

Do Not Email now keeps the profile off campaign list exports without altering the email address itself, so system-generated emails are sent normally, and email data displays consistently. Profiles where the primary email was previously cleared by this issue will have their email address automatically restored. Profiles synced to external email-list providers also stay accurate: Do Not Email profiles are no longer added to event email lists, and existing list memberships are still removed when participation changes.

Permissions: Resolved an issue where changing a user's group did not immediately update the access shown on the home screen and dropdown menus. A user who moved to a new group could retain their previous group's links and access until any permission screen was opened and saved as a workaround. Group changes now refresh the user's access without requiring a manual permission save.

GLM/SLM Integration: Resolved an issue where international phone numbers entered in GLM/SLM mapped to the domestic phone number field in CommunitySuite, causing format errors when editing the profile. Profiles from GLM/SLM now use the country code to determine phone type. When the country is neither the US nor Canada, the phone number is stored in the international phone field, and domestic format validation is skipped.

Checks: Resolved an issue where document generation jobs for check batches posted in an overlapping window could attempt to pull documents across batches, resulting in incorrect document counts and incomplete batches. Document generation jobs are now scoped to the batch that triggered them, and the posting completeness check only flags checks that pay a grant or scholarship expecting a letter, so mixed batches with regular vendor checks no longer get held up.

Check Batch: Resolved an issue where check batches containing internal grants would fail to post when no internal grant letter template was configured. Document generation now skips grants whose letter template type is not configured, allowing the batch to post.

Fund Request: Resolved an issue where the Fund Request staff notification email displayed default placeholder text instead of the fund request details. Also resolved an issue where custom content configured for the Fund Request Acknowledgement email displayed as raw HTML in the message body. If the Fund Request Acknowledge Email Subject and Fund Request Acknowledge Email Body content are not defined, an email will not be sent.

Admin Fee Custom Report: Resolved an issue where the Admin Fee Report included retained earnings transactions posted to the default admin fee expense account. Retained earnings are now excluded from the report. Admin fees posted to the default admin fee account will appear in this report; admin fees posted to a secondary account will not appear in this report.

---

Product Enhancements: May 7

Portal Password Policy: Resolved an issue where the password policy for non-user portal logins could not be edited. The portal user password policy is now configurable in Communication -> Portal Options -> Portal Settings. The backend user/employee password policy remains separately configurable in User Settings.

Internal Grant: Resolved an issue where the grant letter template selection on internal grant create and edit displayed only external grant letter templates. Grant Create and Edit now load internal grant letter templates for internal grants and external grant letter templates for external grants

Nonprofit Profiles: Resolved an issue where a public phone number entered on a nonprofit profile could not be deleted/saved as empty. The nonprofit designation phone is no longer tied to the profile's primary phone, and the field can now be saved as empty.

Funds: Added the ability for a fund to be its own beneficiary. The fund now appears in the beneficiary search when adding beneficiaries.

Grants: Added an Edit Payment Date bulk action that updates the payment date on all grant payment lines that do not have a voucher assigned. If a payment schedule has multiple lines and none have vouchers, all lines update. Updated several grant screens to display "Sponsored Org/Payee" in place of "Sponsored Org."

Quick Transfer: The Amount field now formats with commas as you type.

Permissions: Pinned the column headers to the top of the Permissions page so they remain visible while scrolling.
Added a separate Import permission for profiles, split out from the Create permission. Groups that currently have the profile Create permission automatically receive the new Import permission.

Fund Advisor Permissions: Added All/None toggles for quickly setting tab access across rows and columns. Tab labels now display vertically to reduce horizontal scrolling.

Bank Reconciliation: The check number is now displayed in the reverse bank reconcile. Void check rows now highlight the entire row in red rather than only the check number.

Account Transfer Email: Resolved an issue where the reference link on an account transfer request email logged in a profile's email history led to an unrelated transaction or a "Transfer not found" error. The link now points to the originating account on the transfer request.

Profiles Custom Report: Resolved an issue where filtering a custom Profiles report on Link Start Date or Link End Date returned a critical error instead of results.

---

April 2026

Product Enhancements: April 30

Grants: Added a new Edit Payment Date bulk action to the Grants → New and Grants → Approval bucket views. Users can now select multiple grants and update the next payment date in a single action, rather than opening and editing each grant individually.

---

Product Enhancements: April 28

Grant Letter Template: Added grantee_fedid and supported_vendor_fedid as available fields on grant letter templates.

Online Ticket Registration: Resolved an issue where required fields (name, email, phone) were missing from free ticket event registration pages, preventing registration.

---

Product Enhancements: April 15

Data Visualization: Resolved an issue where fund balance data in Data Visualization could drift out of sync with CommunitySuite over time. The data sync process was not picking up certain data changes, causing fund balances shown in Data Visualization dashboards not to match the values in Custom Reports. Data syncing has been corrected, and a full resync of client data will be performed to ensure accuracy.

---

Product Enhancements: April 13

Historic Donations: Removed the TransID field from the Historic Donation entry form. This field was originally intended to allow users to tie historical donations to a GL transaction, but it did not support editing after entry and could cause errors if users entered non-numeric values, or unintended accounting issues if a valid transaction ID was entered incorrectly. The field has been hidden to prevent these problems.

Profiles: Resolved an issue where address verification duplicated suite or apartment numbers across both address lines. When USPS validation moved a unit designator (such as Suite or Apt) from Address Line 2 to Address Line 1, the original value was not being cleared from Address Line 2, resulting in duplicate information on the profile. The unit designator is now properly removed from Address Line 2 after verification.

Styles: Resolved an issue where the "Apply Donor Portal Style to Funds" setting on a Supported Organization was not correctly applying the organization's portal style to its associated funds. The setting now properly controls whether the Supported Organization's style shows on the relevant funds in the Donor Portal, and funds with their own assigned style will correctly display their fund-level style.

Charity Check: Resolved an issue where the bulk charity check (Charity Check All) function failed with an error when processing a large number of grants as a background job. Users can now successfully run bulk charity checks without encountering an error.

---

Product Enhancements: April 9

Fund Request: Resolved an issue where funds created through a fund request could not be deleted, displaying the error "Unable to delete the fund because there are still references to it." The fund request reference is now properly cleared, so the fund can be deleted as expected.

---

Monthly Release: April 8

Investment Strategies - Fund Base Balance

We are excited to release the ability to set a Base Investment Balance Account and a Base Investment Balance amount on investment strategies. Previously, investment strategies only supported percentage-based allocation across accounts. 

Key Benefits

• More flexibility in investment strategies, allowing foundations to reserve a flat dollar amount in a designated account before percentage-based allocations run.
• Balance Swap calculations now automatically prioritize filling the Fund Base Investment Balance account up to the configured threshold before distributing remaining assets across the strategy's percentage accounts.

Base Investment Balance

Added the ability to set a Base Investment Balance Account and Base Investment Balance amount on investment strategies. Users will now see these fields at the top of each investment strategy when editing. The designated account must be different from the percentage-based accounts already in the strategy (i.e., the Base Investment Balance Account cannot also be one of the strategy's allocation accounts).

The system treats the Base Investment Balance as a threshold: it will fill the designated account up to the configured dollar amount using whatever assets the fund has available. If a fund has less in available assets than the configured amount, the system only swaps the available amount and does not recommend swaps that exceed the fund's actual assets. Once the designated account reaches the configured amount, no further swaps are recommended, and remaining funds flow through the normal investment strategy percentage allocations.

Another way to think about it is adding a step in the hierarchy of how available fund balance is allocated. Min checking balance → payables (SP, AP, etc.) → Base Investment Balance → investment strategy percentage allocations.

Resource: 

• Cash Balancing Setup 

---

Online Fund Request

Community foundations have relied on manual, offline processes to establish new funds, including phone calls, emailed forms, and paper applications. This creates delays, errors, and a fragmented donor experience at a time when commercial DAF providers offer seamless online fund opening. This feature introduces an online fund request form that can be published/promoted in different ways: one public so that donors/prospects can access through a standalone publishable URL, and one that can be added to the Portal.

The form captures fund details, including any fund custom fields the admin has enabled, and then hands off to the existing checkout flow for contact information. Upon submission, the system automatically creates a Fund Request record in the Fund Request list (visible under Funds → List Requests in the left-side menu), creates a new profile from the submitted contact information (or matches to an existing profile), and designates the submitting profile as the Fund Advisor on that request. Designated staff receive an email notification, and the donor receives a configurable acknowledgment email.

Staff can then manage incoming requests from the Fund Request list view, which displays key columns including ID, Created Date/Timestamp, Fund Name, Profile Name, and Opportunity ID. From a fund request, staff can create an Opportunity to track the prospective fund through customizable pipeline stages. The fund request and opportunity are linked with two-way navigation. 

This is a new permission, so it allows users who do not have "create" fund permissions to make a fund request, which someone with appropriate permissions can then convert into a full fund.

Key Benefits

• Enables foundations to offer a self-service experience for users to submit their interest in opening a fund.
• Reduces manual data entry from phone, email, or paper applications, reducing transcription errors and speeding up fund establishment.
• Provides a standardized intake process with automated staff notifications and donor confirmation, preventing missed follow-ups during a critical donor decision window.
• Gives foundations earlier visibility into their fund pipeline, since submitted requests appear immediately in a Fund Request list rather than waiting for manual staff entry.
• Integrates with the existing Opportunities feature so staff can track each fund request through customizable pipeline stages.

Fund Request Form

This feature enables Portal users and/or Giving Hub users to submit fund creation requests to a foundation. Foundations create a single form that can be accessed in two ways: via a toggle on the Giving Hub that activates a publishable URL, or via a toggle on the Fund Advisor Portal profile.

Form Fields & Flow:

The fund request form includes configurable fields: Fund Name (required) and Fund Details.

Fund Custom Fields: Admins control which fund custom fields appear on the form by enabling the "Fund Request Form" checkbox on each custom field in the Fund Custom Fields configuration (Funds → Custom Fields). Enabled fields display on the form in the configured order, positioned below Fund Name/Details and above Contact Information. Each field inherits its name, description, and required/optional settings from the Fund Custom Field configuration. If no custom fields are enabled, the form displays without an additional fields section.

Contact Information: (with a selector for individual, household, or organization).

The individual type selected collects first name, middle name, last name, suffix, email, and phone.

Household or Organization collects name, email, and phone.

Submitting a request automatically searches the system for an existing profile or creates a new profile with the provided contact details.

What Happens on Submission:

A fund request record is created and appears in the Fund Request list (Funds → List Requests in the left-side menu). New/existing profile is designated as Fund Advisor and assigned to the fund request, and to the fund, if it is eventually created. Staff receive email notifications (configured in Portal Notifications → Fund Requests). The donor receives a configurable acknowledgment email (configured in Funds → Content).

Fund Request List & Management:

The Fund Request list view includes default columns: Name, Phone, Email, and Opportunity ID. From here, staff can: Review incoming fund requests, create an Opportunity directly from a fund request, similar to grant promise flow, to track the prospect through customizable pipeline stages, navigate between the fund request and its linked opportunity (two-way navigation), convert a request into a full fund by selecting "Create Fund" from the request, and delete a fund request.

Settings:

Portal Options → Giving Hub Settings → Enable Fund Request Form.

Portal Options → Portal Settings → Profile → Enable Fund Request Form.

Portal Options → Giving Hub Content → Public Fund Request → Public Fund Request Content (customizable content displayed above the public-facing fund request form via Giving Hub).

Portal Options → Portal Content → Profile → Portal Fund Request Content (customizable content displayed above the fund request form within the Fund Advisor Portal).

Portal Options → Portal Notifications → Fund Requests (configure which staff members receive email notifications when a new fund request is submitted).

Funds → Content → Fund Request Acknowledge Email Subject / Fund Request Acknowledge Email Body (configurable acknowledgment email template sent to the donor upon submission).

Funds → Content → Fund Statement (existing content form reorganized into its own tab).

Funds → Custom Fields → "Fund Request Form" checkbox (controls whether each fund custom field appears on the fund request form).

Fund Request → Opportunity integration (create and link from fund requests).

Resource:

• Accept and Manage Online Fund Requests

---

Product Enhancements: April 3

Custom Reports: Resolved an issue where the "IS NOT" date filter in custom reports was not working correctly with relative date options. When filtering on a date field and selecting "IS NOT" with a relative date range (e.g., "This Year," "Last Month," "Q1"), the filter was incorrectly returning records that matched the selected range instead of excluding them. The filter now correctly excludes records matching the selected relative date range.

Custom Reporting: The Object Profile Note report now displays all notes associated with a profile, including notes entered on specific designations (Donor, Grantee, Customer, Vendor) as well as notes on related objects such as Opportunities, Funds, and Tasks.

Stripe: Fixed an issue where donor addresses from countries outside the US, Canada, and Australia could be saved with corrupted characters when received from Stripe. The system will not save addresses from unsupported countries. Addresses from the US, Canada, and Australia continue to be saved as expected. Full international address support will require broader system changes and will need to be planned separately.

---

Product Enhancements: April 2

Profile Merge: Fixed an issue where grantees and vendors could be merged with themselves, which caused a system error. The merge process now prevents selecting the same record as both the source and target.

Data Visualization: Additional grant data has now been flattened into the Grant Payment dataset, so users can build dashboards that include more payment-level and grant-level fields. Grant-related columns in the Grant Payment dataset are prefixed with "Grant Payment Grant" to distinguish them from Grant Payment columns. If additional grant fields are needed in a Grant Payment report, users can see and pull additional grant-related fields from the Grant Payment Grant dataset.

Grant Reports: Fixed an issue where child grants (and vouchers) in a multifund group could be excluded from custom report results when filtering by a custom field value. Previously, a custom field value set on the parent record would display correctly for both the parent and child records in a report, but filtering on that same value would drop the child records from the results. Custom field filters now correctly return all multifund records that display the filtered value.

Profile Log: Improved the audit log to preserve information about the user who performed an action when an employee account is deleted. Previously, if an employee who had created log entries was later deleted from the system, all of their log entries would display "System" as the user, making it unclear who originally performed those actions. The system now stores the employee's name directly on each log entry at the time the action is recorded, so the correct user name is retained in the audit trail even if the employee account is subsequently removed.

Grants: Fixed an issue where multifund grants could appear stuck in the Award Letter bucket even after award letters had been marked as sent. Previously, when a grant with "Award Letter Needed" was linked to another grant via Multifund Add, the child grant's award letter status was not properly cleared when the parent grant's letter was marked as sent. This caused grants to remain in the Award Letter bucket with no way for users to remove them. The system now correctly updates the award letter status across all linked grants in a multifund group.

---

March 2026

Product Enhancements: March 30

Print Page: Updated the Print Page function to use the browser's native print dialog directly, while still hiding CommunitySuite navigation bars from the printed output. This change simplifies the backend and removes a step for users, who no longer need to press Ctrl+P (or Cmd+P) from a separate print preview page. Additionally, resolved an issue where the Support "Help" icon was appearing on the printed page and blocking content.

---

Product Enhancements: March 25

Grantee Search: Resolved an issue where some organizations from the GuideStar search appeared without a name on grant requests. In some cases, this caused the grantee name to display as blank in request buckets and on the grant request itself. The organization name now displays correctly for affected records.

---

Product Enhancements: March 20

User Preferences: Resolved an issue where the legacy "Lock Params" setting was incorrectly preventing some users from changing their user preferences (themes). This setting was previously replaced by the "Profile - Manage Login Info/Login As" permission. The lock has been removed for all affected users, and user preferences are now editable by these users as expected.

---

Product Enhancements: March 18

UI Updates: Resolved a few items where several confirmation messages and notifications displayed inaccurate or misspelled text.

Tributes: When clearing a tribute from an individual donation, the confirmation dialog read "Confirm Donation Delete," which implied the entire donation was being deleted. The message has been updated to "Confirm Tribute Delete" to accurately reflect that only the tribute connection is being removed.

Bulk Charity Check: Corrected a typo on the on the confirmation message after running a bulk Charity Check.

Grant Request Void/Cancel Notification: When a fund advisor cancels or voids a grant request from the portal, the staff notification email has been updated so the email now reads "voided a grant request."

Users: We've added three new security settings under Users, in the left-side menu of Settings, to give organizations more control over how employees authenticate and access CommunitySuite.

• Disable Employee Password Reset Via Email - When enabled, this setting prevents backend users from using the forgot-password flow to reset their own password. Instead, a site administrator will need to reset the password on their behalf. This is useful for organizations that want to reduce the risk of unauthorized access through a compromised email account. Before enabling this toggle, teams will likely want to discuss and/or set up an internal process to handle password reset requests, verify user identities, and confirm which users have access to do so. This may also include considering when administrators with password reset permissions are out-of-office.
• Force SSO Login - This toggle only applies to organizations with SSO set up. When enabled, users linked to SSO must authenticate exclusively through their SSO provider. They will not be able to bypass SSO by logging in with a username and password.
• No Email/Phone 2FA for Users - When enabled, this setting restricts two-factor authentication (2FA) to an authenticator app only, removing the option to receive verification codes via email or SMS. App-based 2FA is generally considered more secure, and is more resilient against account compromise.

---

Product Enhancements: March 13

Pledges: Resolved an issue where pledges could be linked to internal donations. Promises can still be linked to internal donations as expected.

Dark Mode: Improved clarity and contrast for several UI elements, including the custom field creation dropdown, calendar date pickers, rich text editors, and support and other resource links.

Affiliate Orgs: Resolved an issue with the grantee/donor name on internal grants and donations. Internal grants and donations from Affiliate/Supported Org funds that were not marked as a Separate Entity were incorrectly displaying the Affiliate's name as the donor. These transactions now correctly show the main Foundation name as the grantee/donor.

---

Product Enhancements: March 12

Permissions: Resolved an issue where clicking the back arrow on the Task Permissions page directed users to a "Not Found" page. The back arrow now navigates to the default Tasks page (Current Tasks assigned to the logged-in user).

---

Product Enhancements: March 11

User Preferences/UI: Added theme support with three new options: Dark, Contrast, and Green. These are now available alongside the default Light theme. Users can switch themes by selecting their name in the top-right corner, navigating to User Preferences from the left-hand menu, and choosing their preferred theme. Dark mode was a popular request from Idea Lab, and the Idea Lab Live webinar in February 2026, and the Contrast theme was added in response to user UI feedback.

IDEA LAB LIVE - Internal Grants: Added the ability to tie a promise to an internal grant. After initial grant creation, the option to add a promise will appear at the bottom of a newly created internal grant. On the internal grant, users can then select "Add" to view any open promises to the destination fund. Users can then select "Link" to connect the internal grant and the promise. The promise can also be unlinked from the internal grant by selecting "Clear" next to the Promise ID.

If the dollar amount of the grant is more than the promise, the Promise Adjustments table will reflect the increase. If the promise is more than the grant, the promise will show the balance remaining.

This is a request from the February 2026 CommunitySuite Idea Lab Live webinar. 

Public Securities: Updated functionality to handle larger imports of public securities. We've improved how large public security lookups are handled. Any lookup with more than 20 ticker symbols now processes in the background, ensuring all valid symbols populate correctly. Once the lookup completes, simply refresh the page to view your securities.

Stripe Terminal: Resolved an issue causing an error when running Canadian debit cards through a Stripe terminal. Updated functionality to allow Interac payments. 

---

Product Enhancements: March 10

Outlook Plugin: Fixed an error that caused the Outlook plugin to break when searching for profiles. Users were seeing a red error message instead of search results, which made the plugin unusable. Profile search within the Outlook plugin now works as expected.

Grants: Resolved an issue where grantee profiles were showing as invalid when creating grants. The specific root cause was the profile search logic that was using grantee IDs as profile IDs, which could result in grants being attached to the wrong grantee. The fix and some additional follow up work will standardize search box behavior across the system to consistently use profile IDs, affecting search fields in Grants, Profiles, Events, Donations, Vouchers, Scholarships, Funds, and other areas. 

Grantee Portal: Resolved an issue with anonymous grants where the fund name was visible when viewing grant details, and the grant description was incorrectly replaced with "Anonymous" in the grant list view. The fund name is now properly hidden, and the description displays correctly.

---

Product Enhancements: March 3

Multifund Grants: Resolved an issue where users were able to un-post multi-fund grants when one of the related grants was cancelled. Previously, it was possible to un-post and un-approve a multi-fund grant even if one of the related grants had been cancelled. The system now correctly prevents un-posting a multi-fund grant when any of its related grants have been cancelled.

---

February 2026 

Product Enhancements: February 27

Grant Types: Resolved an issue where archived grant types were appearing when bulk setting grant types on grantees. Previously, when using the Bulk Action to "Set Default Grant Type" on Grantees, both active and archived grant types were included. Archived grant types are now correctly filtered out, so only active grant types appear when being set in bulk.

Fund Advisor Portal: Resolved an issue where submitting a grant request would error if the grant was recurring and the "Number of Recurring" field contained only a space.

IDEA LAB LIVE - 1099 Reports: Added "Pay Address" field to 1099 reports.

IDEA LAB LIVE - Checks: Added "Foundation Name" and the "Check Number" to Check Detail Attachments.

Note Custom Fields: Resolved an issue preventing users from creating new note custom fields.

Tribute Honor Template: Updated Template Fields List page to clarify the ID needed to see field examples. Users need to enter mn_id to see all relevant fields

Fund Advisor Portal: Fixed an issue where refreshing the page after submitting a grant request through the fund advisor portal could result in duplicate submissions.

Permissions: Removed "Login As" permission on the Fund Advisor permission page. This functionality shifted to a different area, and as a result, this particular permission became obsolete. This ability to log in as other users can still be set on the Profile permission page with the "Login as another User" toggle. The ability to log in as other users is not affected.

Fund Statements: Resolved an issue where the YTD Interval setting on individual funds was not being applied when generating fund statements.

---

Product Enhancements: February 23

Historic Donation: Resolved an issue preventing users from editing certain fields on historic donations.

Admin Fees: Admin Fee Types will no longer run if they have been archived.

---

Product Enhancements: February 17

Data Visualization: Added and updated new datasets CSuite Scholarship Payment, CSuite Scholarship Payment Grant, and CSuite Scholarship Payment Scholarship to enable users to create dashboards with payment-level scholarship data. The Grant Date field has been made available in the CSuite Scholarship Grant dataset.

Data Visualization: Created and updated datasets CSuite Grant Payment and CSuite Grant Payment Grant to enable users to create dashboards with payment level grant data.

---

Product Enhancements: February 13

Funds: Resolved an issue where the Enable Advisor Donate Button was not saving correctly if selected during fund creation.

Giving Hub: Resolved an issue where a dollar sign was not showing next to amounts on the donation checkout page.

Grant Ledger & Scholarship Ledger Custom Reports: Updated a few items on the new Grant Ledger & Scholarship Ledger Custom reports. These are activity/ledger style reports that show activity that impacts the general ledger (post, cancel, partial cancel) from a grant or scholarship within a specific time period. This will allow users to more easily compare grant and scholarship activity with the general ledger. Grant Ledger - Shows activity in the approval, voucher, paid, and complete status. Updated report logic so that partial cancellations appear on this report. Added a field to show which scholarship lines are post by payment ("Scholarship Post By Payment"). Scholarship Ledger - Scholarship ledger will not show post by payment scholarships.

1099: Resolved an issue where vendor addresses were not appearing on the 1099 report if Do Not Mail was selected on the vendor profile.

---

Product Enhancements: February 11

FT Admin: Resolved an issue causing a temporary error message on sandbox syncs and some other batch jobs. Any jobs that were caught were re-initiated upon resolution.

FT Admin: Removed toggle allowing users to disable the "shiny new look" UI changes and the old top navigation. All users have been moved to the new user interface and new top navigation.

Data Visualization: Resolved an issue causing some fund balances from updating correctly. Affected fund balances are now up to date.

Cart Checkout: Added the ability to disable address collection in the cart checkout for free event tickets. If selected, users going through the checkout process for an event ticket will only be asked to enter a phone number and email address, not a physical address. To enable this option, navigate to Communication -> Portal Options, Giving Hub Settings from the left menu, and then select the Checkout tab. There, users can edit and select the relevant checkbox to enable "No Address On Free Ticket Checkout".

---

Product Enhancements: February 3

Single Sign On (SSO): Resolved an issue causing users to see an error when changing providers.

---

January 2026

Product Enhancements: January 30

Data Visualization: Added "Donation Profile Type Name", "Donation Profile Type ID", "Donation Household Profile Type Name", and "Donation Household Profile Type ID" to the CommunitySuite Donation Profile dataset. This will allow users to run donation reports with, and filter based on, the donor profile type.

Single Sign On (SSO): Resolved an issue causing users to encounter an error when setting up SSO in multiple environments. For the time being, the ability to set up SSO in the sandbox environment has been disabled. The ability to set up SSO in production/live environments is still enabled. Improved the onboarding process by enabling users to exit and restart the process

FedID Field: Updated references to "FedID (SSN/EIN)" to show the updated field name "FedID (EIN)", in an effort to clarify the purpose of this field. In a previous release, the SSN and EIN fields were separated; this change is cleaning up wording in a few areas to align with that change.

---

Product Enhancements: January 28

HTML Editor: Resolved an issue with pasting text into rich text html editor fields.

1099 Reports: Resolved an issue causing some vendors that did not need a 1099 to appear on the 1099 report.

API: Resolved an issue with the Power BI Connector.

---

Product Enhancements: January 23

Custom Reports: Added two new custom reports, Grant Ledger and Scholarship Ledger, to help users verify grant and scholarship activity against the General Ledger. These reports capture all activity within the selected date range, including canceled awards, regardless of when the original award was made.

2-Factor Authentication: Added the ability to use 2-Factor Authentication for Australian phone numbers in Australian sites. Phone numbers need to be 10 digits, and do not need the country code entered on the profile.

---

Product Enhancements: January 15

Profile Search: Resolved an issue causing international addresses to populate incompletely when searching for profiles upon creation of pledges, promises, loans, and opportunities. Profile addresses will now fully populate.

Campaigns: Resolved an issue that prevented users from disabling the "Ticket Additional Donation" setting in situations where the "Ticket Include Note" setting was also enabled.

Fund Advisor Portal: Resolved an issue causing the fund name to show instead of the public fund name when viewing donation details.

---

Product Enhancements: January 13

Affiliate Giving Hub: Resolved an issue causing the affiliate organization name not show in the subject line of donation receipts from the Giving Hub.

Print Envelope: Updated the envelope label so that if the mailing label is blank, the label field will default to showing the following fields in the following order: Prefix, First Name, Middle Name, Last Name, Suffix. The mailing label field still allows users to define a particular label other than the default.

Custom Reports: Added an Opportunity Task Notes report so that users can run reports with tasks and their associated notes. This will allow users to run more detailed task reports, including related fields from opportunities and notes associated with a task.

Stripe: Resolved an issue causing an error when manually rerunning Stripe transactions.

Till: Added a Total Non-Till Balance line to the Unreconciled Non-Till Transactions table.

Account Financial Views: Added all/none buttons when editing the accounts associated with a financial view.

Grants: Updated internal grant workflows for affiliates and sponsored organizations. Now the affiliate/sponsored organization name is displayed as the grantee only when that profile has been marked as a separate entity; otherwise, the foundation name will be shown.

---

Product Enhancements: January 8

Grant Catalog: Added the ability to donate on the direct grant page to grants when no funding goal is currently set.

Grants: Added an option in the Grants Settings called "Show Grant Payable Swaps". This setting will display Grants Payable in the Balance Swap. To turn on this setting, navigate to Grants, and then Settings from the left-side menu. Click edit settings to check the "Show Grant Payable Swaps" option.

---

Monthly Release: January 7

Single Sign-On Integration (SSO)

We are excited to announce the launch of Single Sign-On (SSO) capability, enabling users to access the platform using their existing corporate credentials. This enhancement streamlines the authentication process and improves security across your organization.

Key Benefits

For End Users:

• One-click access with existing corporate credentials
• No additional passwords to remember
• Faster login experience
• Automatic session management

For Administrators:

• Centralized user management
• Enhanced security controls
• Automated user provisioning and de-provisioning
• Comprehensive audit logging
• Reduced password reset requests

Users: Added the ability to enable SSO for the entire organization or individual users.  Users will see the Enable SSO Login in the Me tab.  This will allow the individual user the ability to enable SSO. To enable SSO for all users within the organization, Admin will enable SSO using the SSO Settings in Users.  Once SSO setup has been completed by the admin, the admin will need to enable the Automatically Link SSO Users setting in User Settings. This will enable SSO for the entire organization.  

Email Matching Requirement: For SSO authentication to work properly, the login credentials in user profiles within CommunitySuite must match the SSO credentials configured in your identity provider. Before enabling SSO, administrators should verify that all user profile email addresses in CommunitySuite match the email addresses (or usernames) used in your identity provider. If your foundation is using email addresses for SSO login, the same email address must be used for CommunitySuite user profiles. A mismatch between CommunitySuite user emails and SSO credentials will prevent successful authentication.

Things to Note: This is for users within CommunitySuite, not the Portal login for Fund Advisors, Grantees, Donors, etc.

Resource:

• CommunitySuite Single Sign On (SSO)

---

Product Enhancements: January 6

Fund Reports: The Detail Trial Balance report now shows in the list of available reports from the fund record.

---

Product Enhancements: January 5

Campaign Online Event Registration: Resolved an issue causing an error when a guest of one profile purchased their own ticket separately.

Shiny New Look: Responded to user feedback on the new UI updates, particularly around visibility and shading:
- Increased contrast when grouping a custom report.
- Increased contrast between enabled and disabled action buttons according to user permissions.
- Updated buttons for generating award letters on scholarships.

Fund Advisor Portal: Resolved an issue causing the internal fund name to show when drilling into grant history.

Fund Advisor Portal: Resolved an issue that caused an error when drilling into the Fund Summary report when the lookback date was not set.

Grant Requests: Resolved an issue that allowed Fund Advisors to donate to fully funded requests where overfunding was not allowed.

 

• (05-29-2026) 2 Factor Authentication / Password Reset: Resolved an issue where users who had set up 2FA via an authenticator app could get stuck in a login loop when attempting to reset their password.
• (05-15-2026) Print Page: Resolved an issue where using Print Page on a report after scrolling down the page caused duplicate headers to appear mid-printout and report results to appear out of order or skip ahead.
• (05-15-2026) Workato: Resolved an issue where Workato connector events could fail intermittently when triggered during profile creation.

• (05-13-2026) Captcha Hardening: As part of ongoing security enhancements, we have tightened how CAPTCHA validates the hostname of incoming traffic. Stricter hostname checking helps block bad actors from spoofing your site.

  Key Benefits

  - Stronger protection against CAPTCHA bypass attempts that rely on hostname spoofing.
  - Continued support for customers who legitimately proxy CommunitySuite traffic (e.g., for translation or alternate domains).

• (03-30-2026) Print Page: Updated the Print Page function to use the browser's native print dialog directly, while still hiding CommunitySuite navigation bars from the printed output. This change simplifies the backend and removes a step for users, who no longer need to press Ctrl+P (or Cmd+P) from a separate print preview page. Additionally, resolved an issue where the Support "Help" icon was appearing on the printed page and blocking content.
• (03-18-2026) UI Updates: Resolved a few items where several confirmation messages and notifications displayed inaccurate or misspelled text.
• (03-16-2026) User Preferences/UI - Dark Mode: Improved clarity and contrast for several UI elements, including the custom field creation dropdown, calendar date pickers, rich text editors, and support and other resource links.
• (03-11-2026) User Preferences/UI: Added theme support with three new options: Dark, Contrast, and Green. These are now available alongside the default Light theme. Users can switch themes by selecting their name in the top-right corner, navigating to User Preferences from the left-hand menu, and choosing their preferred theme. Dark mode was a popular request from Idea Lab, and the Idea Lab Live webinar in February 2026, and the Contrast theme was added in response to user UI feedback.
• (03-10-2026) Outlook Plugin: Fixed an error that caused the Outlook plugin to break when searching for profiles. Users were seeing a red error message instead of search results, which made the plugin unusable. Profile search within the Outlook plugin now works as expected.
• (02-11-2026) FT Admin: Resolved an issue causing a temporary error message on sandbox syncs and some other batch jobs. Any jobs that were caught were re-initiated upon resolution.
• (02-11-2026) FT Admin: Removed toggle allowing users to disable the "shiny new look" UI changes and the old top navigation. All users have been moved to the new user interface and new top navigation.
• (01-28-2026) HTML Editor: Resolved an issue with pasting text into rich text html editor fields.
• (01-23-2026) 2-Factor Authentication: Added the ability to use 2-Factor Authentication for Australian phone numbers in Australian sites. Phone numbers need to be 10 digits, and do not need the country code entered on the profile.
• (01-13-2026) Print Envelope: Updated the envelope label so that if the mailing label is blank, the label field will default to showing the following fields in the following order: Prefix, First Name, Middle Name, Last Name, Suffix. The mailing label field still allows users to define a particular label other than the default.
• (01-07-2026) Single Sign-On Integration (SSO): We are excited to announce the launch of Single Sign-On (SSO) capability, enabling users to access the platform using their existing corporate credentials. This enhancement streamlines the authentication process and improves security across your organization.

Key Benefits

For End Users:

-One-click access with existing corporate credentials

-No additional passwords to remember

-Faster login experience

-Automatic session management

For Administrators:

-Centralized user management

-Enhanced security controls

-Automated user provisioning and de-provisioning

-Comprehensive audit logging

Reduced password reset requests

Users: Added the ability to enable SSO for the entire organization or individual users.  Users will see the Enable SSO Login in the Me tab.  This will allow the individual user the ability to enable SSO. To enable SSO for all users within the organization, Admin will enable SSO using the SSO Settings in Users.  Once SSO setup has been completed by the admin, the admin will need to enable the Automatically Link SSO Users setting in User Settings. This will enable SSO for the entire organization.  

Email Matching Requirement: For SSO authentication to work properly, the login credentials in user profiles within CommunitySuite must match the SSO credentials configured in your identity provider. Before enabling SSO, administrators should verify that all user profile email addresses in CommunitySuite match the email addresses (or usernames) used in your identity provider. If your foundation is using email addresses for SSO login, the same email address must be used for CommunitySuite user profiles. A mismatch between CommunitySuite user emails and SSO credentials will prevent successful authentication.

Things to Note: This is for users within CommunitySuite, not the Portal login for Fund Advisors, Grantees, Donors, etc.

Resource:

CommunitySuite Single Sign On (SSO)

• (01-05-2026) Responded to user feedback on the new UI updates, particularly around visibility and shading:
  - Increased contrast when grouping a custom report.
  - Increased contrast between enabled and disabled action buttons according to user permissions.
  - Updated buttons for generating award letters on scholarships.

Accounts

Account Transfers

Allocation Tables

Bank Reconcile

Budget

Cash Management

Funds

General Ledger

Journal Entry

Revenue Share

Accounts Receivable

Admin Fee

Deposits

Donations

Invoices

Payments

Pledges/Promises

Public Securities

Till

Accounts Payable

Checks

Distributions

Grants

Grant Cards

Grant Catalogs

Loans

Scholarships

Split Interest

Term Investments

Vouchers

990 Report

1099 Report

CRA Reporting

Financials

Fund Statements

Reports

Campaigns

Opportunities

Portal Options

Styles

Templates

Tributes

Files

Logs

Notes

Tasks

Profiles

Donors

Grantees

Vendors

Customers

Students

Nonprofit

Fund Advisors 

Affiliate/Orgs

Alumni

System Data 

Users

Groups

Stewards

Grant Types

Service Areas

Payment Processors

Custom Fields

Integrations