- or
No existing idea results
- ~ No ideas found ~
1422 results found
-
Short Description separation from Long Description
The short description and long description of a grant request on the catalog is not differentiated in any way. This looks a bit messy to the donor who may only want to glance at the short descriptions as opposed to reading the entire long description for each grant request. It would be very beneficial if there was a separation between the short description and the long description such as a line, a larger space, or even just bolding the short description and not bolding the long one.
9 votes -
Show Organization Name in Charity Check Log
Add organization name as a column in the charity check log to more easily confirm that the right Tax ID is in the profile. Right now, if you need to confirm that a grantee has the right Tax ID on file, you have to run a new charity check.
10 votes -
Task Reports Not Connected to Opportunity
It would be extremely helpful to be able to use the custom Tasks report for tasks not connected to an opportunity. It seems strange to me that we have the ability in CSuite to link tasks to Donors, to Funds, to Gifts, etc., and then are not able to report out on the details of those Tasks. I know we are not alone in using Tasks outside of tracking Opportunity Tasks. Using tasks has become a way for us to manage our workflows internally across departments, so would like to see more robust reporting that matches the existing functionality.
9 votes -
Allow a Ticket Cap
Allow a ticket cap to be implemented so that there is a maximum amount of tickets that can be claimed in one transaction.
15 votes -
Changing and Customizing the Buttons in Portal
Allow us to customize and change the Changing and Customizing the Buttons in Portal "Previous Grantee or Fund, Search Grantee, and or Manual Grantee"
5 votes -
Enhanced User Login & Engagement Tracking in Community Suite
We push people to the Portal a lot, but right now we really don’t have a good way to see how often people are actually logging in.
We can’t easily tell who’s active, who hasn’t logged in for a while, or whether people are using the Portal the way we hope they are. Without that info, it’s hard to know what’s working, where users might be getting stuck, or how engaged our fund advisors and other users really are.
It would be incredibly helpful if C-Suite could make basic login details—like last login date, how many times someone has logged in, and overall login trends—objects in Reporting.
Having even simple data would help us understand user engagement, spot people who might need support, and see whether changes we make to the Portal are actually improving things.
We push people to the Portal a lot, but right now we really don’t have a good way to see how often people are actually logging in.
We can’t easily tell who’s active, who hasn’t logged in for a while, or whether people are using the Portal the way we hope they are. Without that info, it’s hard to know what’s working, where users might be getting stuck, or how engaged our fund advisors and other users really are.
It would be incredibly helpful if C-Suite could make basic login details—like last login date, how many times someone has logged…
8 votes -
Expand Character Limit for "Fund Beneficiary Grantees/Funds" Description Field
The description field for a fund beneficiary grantee has a limit around 250 characters. This is where we enter the grant purpose for these organizations so they understand how to use the grant. We have several funds with purpose language that is much longer than 250 characters. It would be helpful to expand this field to have an unlimited character limit.
9 votes -
Archive closed bank accounts
It would be nice if we could archive a closed bank account. Thanks!
11 votes -
Allow Internal Grant Letters to Pull Receiving Fund Fund Advisor Info (Name/Address)
When generating an internal grant letter (e.g., a DAF granting into an Agency Fund or Field of Interest Fund), foundations may want to notify the receiving fund advisor that a grant has been made into their fund.
Currently, there are no available merge fields that allow users to pull:
-The primary fund advisor of the receiving fund
-The receiving fund advisor’s mailing address
-Other advisor contact details from the receiving fundThis limitation makes it difficult to automate internal notification letters for:
-Interfund grants
-DAF → Agency Fund grants
-DAF → Field of Interest grantsCurrent Limitation:
Internal grant letters only have access to fields tied directly to the grant record and its originating fund. There is no way to dynamically reference the receiving fund’s advisor information.Requested Enhancement:
Add merge fields to internal grant letters that allow users to pull:
-Receiving Fund Primary Advisor Name
-Receiving Fund Primary Advisor Address (Street, City, State, Zip)
-Receiving Fund Advisor Email/PhoneImpact:
This enhancement would:
-Reduce manual data entry
-Eliminate reliance on custom fields as workarounds
-Improve automation for internal grant communications
-Support foundations that frequently process interfund grantsWhen generating an internal grant letter (e.g., a DAF granting into an Agency Fund or Field of Interest Fund), foundations may want to notify the receiving fund advisor that a grant has been made into their fund.
Currently, there are no available merge fields that allow users to pull:
-The primary fund advisor of the receiving fund
-The receiving fund advisor’s mailing address
-Other advisor contact details from the receiving fundThis limitation makes it difficult to automate internal notification letters for:
-Interfund grants
-DAF → Agency Fund grants
-DAF → Field of Interest grantsCurrent Limitation:
Internal grant letters…9 votes -
Checks Content - Remove Detail Attachment
We were in hopes of streamlining our communication with our payees when an ACH payment was processed. We enabled the check content but were disappointed when we tested the process that an automatic pdf is created that lists what Fund the payment is coming from. We would like the pdf to be an option that can be turned off OR have an option to not have the Fund shown on the pdf.
16 votes -
spending policy
When calculating the annual distributions for a fund, the system allows you to edit the amounts Csuite is calculating before review and posting. We often adjust the amounts for scholarship funds, new funds, etc. It would be helpful if the system would allow you to see an adjusted total before selecting review or an edit selection after review is selected. Lack of this ability causes much rework as errors happen and the entire process has to be redone.
8 votes -
dashboard
The dashboards for grants and donations are excellent It would be amazing to have something similar for reporting on our organization's finances and investment performance. Graphic presentation of info is important to our finance committee, and it seems a shame to have to create everything manually from exported reports now that CSuite has dashboard capabilities.
Create a dashboard for financial performance. (budget YTD and full year, year over year, trends, etc.) Allow user to select and save filters (accounts, fund groups, etc.)
10 votes -
Fund Portal Donate Button - Add tributes
Fund advisors must now donate to their fund via the new Donate button instead of the Giving Hub. Please add an option for them to donate in memory of/in honor of to create a tribute on their donations in this new area.
4 votes -
Flexible Multi-Factor Authentication (MFA) Controls
Problem Statement:
Currently, the system requires MFA at every login, regardless of the device or session context. While secure, this "one-size-fits-all" approach is causing significant MFA fatigue among users and disrupting workflows on trusted, managed devices.Proposed Enhancement:
I am requesting the implementation of more granular MFA controls that allow for a better balance between security and user experience. Specifically, I propose adding the following features:
"Remember This Device" Option:
Allow users to opt-in to a trusted device status (e.g., for 14 or 30 days). This would suppress MFA prompts for subsequent logins on that specific browser/device until the duration expires or the session cookie is cleared.
Adaptive/Risk-Based MFA:
Implement logic that triggers MFA only when "out-of-pattern" behaviour is detected, such as:
Logins from a new IP address or geographic location.
Accessing the system from an unrecognized device or browser.
Attempts to perform high-privilege actions (e.g., password changes or data exports).
Configurable Re-authentication Intervals:
Provide administrators the ability to set different MFA frequencies based on user roles (e.g., standard users every 7 days vs. admins at every login).Benefit:
These updates will reduce "notification spam," lowering the risk of users reflexively approving malicious MFA requests while maintaining high security for sensitive actions and unknown access points.Goal:
Move from a static "every login" requirement to a dynamic, risk-aware authentication model.Problem Statement:
Currently, the system requires MFA at every login, regardless of the device or session context. While secure, this "one-size-fits-all" approach is causing significant MFA fatigue among users and disrupting workflows on trusted, managed devices.Proposed Enhancement:
I am requesting the implementation of more granular MFA controls that allow for a better balance between security and user experience. Specifically, I propose adding the following features:
"Remember This Device" Option:
Allow users to opt-in to a trusted device status (e.g., for 14 or 30 days). This would suppress MFA prompts for subsequent logins on that specific browser/device until the duration…6 votes -
Expand Special Character Support in CSuite Password Policy
Problem Statement:
There is currently a technical conflict between our organization’s security tools and the CSuite platform. We enforce the use of Keeper for all staff to generate and store high-entropy passwords. However, CSuite rejects many of the standard special characters generated by these tools (e.g., ^, *, [, {, |).
When Keeper generates a secure password, CSuite frequently returns an error, forcing staff to manually change or delete characters that are not allowed or resort to simpler, less secure passwords. This creates a significant friction point and undermines our security posture.Proposed Enhancement:
Update the CSuite password validation logic to support the full range of special characters found on a standard ASCII keyboard.Technical Requirements:
Broaden Character Set: Allow all standard symbols, including:! @ # $ % ^ & * ( ) _ + - = [ ] { } ; : ' " \ | , . < > / ? ~`
Validation Alignment: Ensure the backend database and application filters are updated to handle these characters securely (e.g., via proper salting/hashing) to prevent injection risks while allowing user flexibility.Benefit:
Security Compliance: Allows staff to use 100% of the security features in Keeper without manual intervention.
Improved UX: Eliminates the "trial and error" loop staff currently face when setting or changing passwords.Goal:
To align CSuite’s password policy with industry-standard password managers, ensuring that "strong" passwords generated by our internal tools are accepted without error.Problem Statement:
There is currently a technical conflict between our organization’s security tools and the CSuite platform. We enforce the use of Keeper for all staff to generate and store high-entropy passwords. However, CSuite rejects many of the standard special characters generated by these tools (e.g., ^, *, [, {, |).
When Keeper generates a secure password, CSuite frequently returns an error, forcing staff to manually change or delete characters that are not allowed or resort to simpler, less secure passwords. This creates a significant friction point and undermines our security posture.Proposed Enhancement:
Update the CSuite password validation logic…6 votes -
Turn off or modify email for non-gift
We would like to be able to either (1) turn off donation emails related to non-gift donation types, or (2) be able to modify the donation emails to have more appropriate wording related to these donation types. It appears there is only one Donation Notify Email Body within Communication Content that can be assigned in this area and it would be helpful to customize the body of the email based on the donation type.
4 votes -
Portal - customize email subject line and body
There should be a way to customize the email subject line and body in the portal. We have a new portal user who has reached out to us about editing some of the wording as it is confusing to the user and I agree. The specific instance is the email that the user receives after submitting a grant request and the subject line is "Request Confirmation". To the user, it sounds like they need to take action, when it should say something like "We’ve Received Your Grant Request" or "Thanks for Submitting Your Grant Request". Same with the body of the email, it could be improved upon.
If this is available on the donation side, it should be on the grant side as well.
Thanks for your consideration!
There should be a way to customize the email subject line and body in the portal. We have a new portal user who has reached out to us about editing some of the wording as it is confusing to the user and I agree. The specific instance is the email that the user receives after submitting a grant request and the subject line is "Request Confirmation". To the user, it sounds like they need to take action, when it should say something like "We’ve Received Your Grant Request" or "Thanks for Submitting Your Grant Request". Same with the body of…
12 votes -
Opportunity Task Notes Should Display in Fund Notes Tab When Fund is Selected
Currently, when creating an Opportunity Task Note, users can associate both a Profile and a Fund with the note.
The note does display in the Notes tab on the associated Profile
However, the note does not display in the Notes tab on the associated FundThis creates an inconsistency in how notes are surfaced across related records.
Suggested Enhancement:
-When a Fund is selected on an Opportunity Task Note, the note should also appear in the Notes tab of that Fund
-This would mirror the existing behavior for Profiles and create consistency across the systemWhy This Matters:
-Improves visibility of stewardship and relationship activity at the Fund level
-Ensures important context isn’t siloed only to Profiles
-Creates a more complete view of interactions tied to a FundCurrently, when creating an Opportunity Task Note, users can associate both a Profile and a Fund with the note.
The note does display in the Notes tab on the associated Profile
However, the note does not display in the Notes tab on the associated FundThis creates an inconsistency in how notes are surfaced across related records.
Suggested Enhancement:
-When a Fund is selected on an Opportunity Task Note, the note should also appear in the Notes tab of that Fund
-This would mirror the existing behavior for Profiles and create consistency across the systemWhy This Matters:
-Improves visibility…5 votes -
Improve CC Field Selection When Sending Grant Letters via Email from Document Bucket
When processing grant letters through the Document Bucket and sending them via email, the system automatically populates the “Email” field using the primary email address on the profile.
However, the “CC” field currently requires manual entry, even when additional email addresses already exist on the profile.
It would be very helpful to enhance this workflow by allowing users to select from existing email addresses tied to the profile, rather than manually typing them in.
Suggested Enhancement:
Add a dropdown or selector within the CC field that:
-Displays all email addresses associated with the profile
-Allows users to quickly select one or multiple recipientsOptionally, allow a hybrid approach:
-Select from existing emails and/or manually enter a new address if neededWhy This Matters:
-Reduces manual entry and risk of typos
-Improves efficiency when sending high volumes of grant letters
-Creates consistency with how the primary email field is automatically populated
-Better leverages existing profile data within CommunitySuiteAdditional Considerations (Nice-to-Have):
-Ability to save default CC recipients for specific grantees
-Multi-select with checkboxes for quick inclusion of multiple contactsWhen processing grant letters through the Document Bucket and sending them via email, the system automatically populates the “Email” field using the primary email address on the profile.
However, the “CC” field currently requires manual entry, even when additional email addresses already exist on the profile.
It would be very helpful to enhance this workflow by allowing users to select from existing email addresses tied to the profile, rather than manually typing them in.
Suggested Enhancement:
Add a dropdown or selector within the CC field that:
-Displays all email addresses associated with the profile
-Allows users to quickly select one…6 votes -
Hide historical events when buying a ticket from a profile payment
I need old events to NOT show up on the “Sell Ticket to Campaign - Choose Ticket” page. See attached picture. Right now, we only have a couple years’ worth of events, but I’m worried about how long it will get once we start having more events. I’ve tried making the old events “historical” events, but they’re still showing up as available tickets to purchase.
Additional info: I get to the “Sell Ticket to Campaign - Choose Ticket” page when clicking “Buy Ticket” from a profile payment. There are both current and past events visible that have clickable ticket links. For example, in the attached screenshot, I need to have only the 2026 Community Gathering event show and not the 2025 Community Meeting events. The only option I have right now is to go into each old event's ticket and manually make it Sold Out. While that prevents clicking buying a ticket to an old event, it does not solve the massive number of events that will be listed on the page in a few years.
I need old events to NOT show up on the “Sell Ticket to Campaign - Choose Ticket” page. See attached picture. Right now, we only have a couple years’ worth of events, but I’m worried about how long it will get once we start having more events. I’ve tried making the old events “historical” events, but they’re still showing up as available tickets to purchase.
Additional info: I get to the “Sell Ticket to Campaign - Choose Ticket” page when clicking “Buy Ticket” from a profile payment. There are both current and past events visible that have clickable ticket links.…
8 votes
- Don't see your idea?