Little Green Light is a cloud-based donor management system for fundraisers.
Subscribe to get our latest product updates, best practices and tips to grow your nonprofit.
This April 2025 Release Notes edition shares the latest updates and fixes LGL developers have made over the past few months to improve and enhance functionality within Little Green Light.
Click any item in the table of contents below to link to further details.
It is now possible for organizations to make a document file publicly accessible via a public link, to allow the sending of “attachments” (in a manner of speaking) to emails that can be opened by the recipient. Access can also be granted and removed.
The form name has been added to the name of the file downloaded to enable tracking.
We have improved how the Little Green Light–QBO integration handles QBO classes by adding these features and bug fixes:
For accounts using the deposits-based QuickBooks Online integration feature, we have added a line in the Alerts area to list deposits that are waiting for review or ready to sync.
New data fields are created and existing data fields are sometimes renamed over time as Little Green Light is continually updated. We have updated our Flex Importer to reflect these changes automatically, so mapping fields and reporting fields should be consistent with one another moving forward.
It is now possible to add the [[sender_signature]] merge field from the list of merge fields that is available when crafting an email.
To decrease the opportunity of an account takeover, we have added an additional security layer for users changing their account email. When a user clicks the “Change your email” button in their user profile, the user is required to enter their password before being given the option to change the email address. If two-factor authentication is turned on, this will also be triggered.
As a security enhancement, we have implemented a 5-password-reset-per-day maximum. After 5 resets, a message is displayed to the user indicating the account has been locked and that the user needs to contact their account administrator or LGL Support. An additional lock feature to user accounts, controlled by the Administrator role, is also available.
Users reported that it was difficult to manage steward assignments for deactivated staff if they did not remember to reassign stewards before deactivating the staff member. Any team members that have been deactivated are now prevented from being displayed as stewards in Little Green Light.
We have added a Zip code field to PayPal Complete Payments as an additional security layer.
To prevent issues with historical payment information and problems processing recurring payments, we have disabled the ability to change a form’s type from “Donation/Payment” to “Non-payment” after payment submissions have been processed for the form.
Previously in LGL Forms, copied forms retained settings from the original form for the user (creator) and time zone. This has been updated so copied forms now display the user who copied the form as the creator as well as use the creator’s time zone.
Previously in LGL Forms, how you would set up your form to show a message when an inventory limit has been reached required that the inventory amount also be displayed. This was not apparent in the user interface, resulting in some confusion. The text in the UI has been clarified so the step to take to display the message is now clearer. The option text “Show a message (you can edit the message):” has been changed to “Show the field. If displaying remaining inventory above, a message will also be displayed (you can edit the message):”.
To prevent confusion and mapping issues, the maximum number of additional constituents that can be mapped in any given form has been limited to 10.
The default function in LGL Forms has been updated to allow a value to be set as a default even when there is only one option available to assign.
Some users experienced issues when attempting to scroll down in the left column of the Constituents tab. This has now been fixed.
When importing a file that had the “Deceased” field mapped, the field was not picking up negative values and sometimes incorrectly coded constituents as deceased.
Some users found the tooltip explanation of what is included in the “Total Raised by Type and Year” widget confusing. The tooltip has been updated with clarifying language.
Some users experienced the “Gifts by tier” fundraising view as sorting the gift tiers out of order. This has been fixed.
The Gift History report that you can download from the Giving Summary area in a constituent record had a display error, and in some places the pledge payments and the pledge total were both included in calculations. This has been fixed.
One of the constituent reporting fields (“Date added”) was not displaying any data upon report generation. This has been fixed.
Due to a display issue, the “Manage Templates” tab was previously not displaying for the “Contact Rpt. Reports” and “Volunteering Reports” areas. This has been fixed.
In the Annual Statements feature, a previous issue caused some constituents to be marked as “Moved to printed segment” when they were not actually in the printed segment. This has been fixed.
When attempting to scroll through a list of failed emails, some users were being presented with a blank page. This has been fixed.
Under specific circumstances in the QuickBooks Online integration area, the “Sync All” button on the Pending sales receipts page could be hidden even when there were sync-able gifts present. This has been fixed.
Two bugs have now been fixed in the QBO integration:
1. When a QBO Class was disabled in Settings by unchecking its checkbox, any Deposit where that class was selected on one of the Additional Line Items would fail to open when clicked.
2. When any QBO Item (Class, Payment Method, Product/Service, Tax Code) was disabled in Settings, any open Sales Receipt where that item was selected would continue to display the item instead of showing it as unset.
In both these instances, changes that cause information to be lost on a receipt will now require the user to fix the information before syncing.
In the QBO integration, when an account was using the “Generic QuickBooks Customer” and then switched to “Unique” customers, current unsynced gifts appeared to have no customer set. In reality, the generic customer was still assigned, which defined them in the system as sync-able when they weren’t. When the user then attempted to sync these gifts, QBO rejected them. This has been fixed to ensure that the generic customer ID is removed from all open sales receipts when the “Unique QuickBooks Customer” setting is enabled. It will also be added back when the “Generic QuickBooks Customer” setting is enabled.
In our QBO integration, under a very rare set of circumstances, a sales receipt could be removed from a new deposit when it should not have been. This has been fixed.
For gift data imported using the PayPal IPN (not using PayPal in LGL Forms), the gift date was being set to the current date (in UTC) when the record was created in the Integration Queue. This could end up being a much later date than when the PayPal donation was actually made, both due to the time zone difference and whether there was a significant delay in importing the record into the queue. The gift date is now set using the “payment_date” field coming in with the PayPal data.
Note: PayPal always provides the “payment_date” field in Pacific Standard Time (PST).
In rare cases, users editing the URL to move through search result pages would occasionally generate page numbers that did not function correctly. This has been fixed.
When mapping more than one field in a form to a single LGL field, the mapping of both fields would previously only save if the “Save & Finish” button was clicked twice. This has now been fixed.
When the name of a form was too long, an error occurred when the user checked out using PayPal as the payment method. The form’s name is now truncated in the order description so that the form name + invoice_id do not exceed the character limit for the form name.
Updates to the LGL Forms code removed the mobile (hamburger) menu from the user interface when viewing LGL Forms on a mobile device. The hamburger menu has now been added back to the UI.
In LGL Forms, an incomplete display rule previously would cause issues with the form, such as data not saving correctly. This has now been fixed.
Some users were experiencing an error when the default value in a form was the word “true”. This has now been fixed.
When passing two radio fields back to back to Note text in a form, previously only the first would be captured. This has now been fixed so both radio fields can now be mapped and the data captured.
When an apostrophe was present in the “Recurring” or “End Date” label text in the Amount field in a form, an error was triggered and the form could not be edited. This has been fixed.
When resetting the “Connect to LGL Appeal” dropdown field to a new appeal in a duplicated form, only the appeal references for Constituent #1 were reset; values for any additional constituents were not mapped. This has been fixed.
When an image was submitted via a form, the URL to the uploaded image would expire after 7 days and the image would no longer be available. This has been fixed.
Some users could not view submissions from Forms by clicking “View files” on the Submissions summary page. This was caused when the filename contained specific characters. We have fixed this issue.
The presence of quotation marks in field option text in a form previously caused an error. This has been fixed.
Some users found that when the domain for an email address contained mixed case (uppercase and lowercase) characters, the email would not appear as a valid sender. This has been fixed.
Some users were experiencing difficulty when attempting to add a section to a form containing links. This has been fixed.
The following release notes are relevant to software development only.
It is now possible to integrate with software services using JSON-based webhooks. In other words, the webhooks endpoint available in LGL can now handle JSON data. This feature is currently in beta. If you’re interested in using it, please send a request to LGL Support.
It’s now possible to add Notes to constituent profiles using the API. API developers can create and update Notes in the same way as they do Contact Reports (without the search entry point). Note types are also available.
In rare instances, users attempting to add a gift to an inactive (AKA deleted) constituent record using the API did not experience an error. The attempt appeared to be successful, but the gift was not added. This has been fixed so the API now rejects any attempt to create a gift for a constituent record that is inactive (because it has been merged or deleted).
Ready to try LGL? Get your first 30 days free. No credit card required.
