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 September 2025 Release Notes edition shares the latest feature 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.
We have added new security options and enhanced existing security options as follows:
1. Additional options for 2-step verification (also known as 2 factor authentication, or 2fa). The original 2-step verification used email. It is now possible to use an authenticator app and set up recovery codes.
2. The user profile now contains a section for users to set 2-step verification settings for their master user; 2-step verification can be also required by the account administrator (see item b below)
3. We added a new “Security settings” section in Account Settings to set up security options.
a. This “Security settings” section now offer an inactivity auto-logout setting. By default, it is off. Auto logout options are 15 minutes, 30 minutes, 45 minutes, 1 hour, and none.
b. We moved the 2-step verification setting into this section as well.
4. The “Security settings” section is always present on this page, whether the settings are turned on or off.
Read more about the new and updated security settings:
Some users found the tooltip explanation of what is included in the “Total Raised by Type and Year” widget confusing. The tooltip language has been updated with clarifying language.
We have added a Zip code field to PayPal Complete Payments as an additional security layer.
As we update our system over time, new data fields are created and existing ones are sometimes renamed. We have updated the Flex Importer field names to reflect these changes automatically, so import and export field names are consistent.
When processing large numbers of deposits using our QBO integration, some users were experiencing long processing times. We have made updates to decrease the processing time.
We have increased the maximum allowed file size for images and documents uploaded into LGL from 10 MB to 20 MB.
And, as a reminder from our last Release Notes, you can set a document to be public and link to it in an email as a way to give recipients access to documents (in lieu of attachments). Check out this Pro Tip article for some cool ideas about how to use this feature.
We have added a “divide by one hundred” rule for amount fields in the mapping section of the Flex Importer. Using this rule helps when your data is in the form of cents (e.g., 2000) instead of dollars (e.g., 20.00).
A new merge field in LGL Forms confirmations, [[ payment_summary_with_deductible ]], includes a deductible column. This allows customers to continue to use the existing payment_summary that does not include the deductible information, and customers who want to include the deductible amount can use the new merge field.
We have added the form name to the name of the QR file you can download from your LGL Forms area. If you use QR codes for multiple forms, this helps you keep track of which is which.
When an LGL Forms account had only one payment processor enabled, the payment processor was previously not displayed in the form’s Edit page. We have updated the Edit page so the payment processor for that form is always displayed regardless of how many payment accounts are in use for the form.
In Forms, we have added an error message to indicate what is missing when a user attempts to sync a form submission that is lacking the volunteer data required to create a record.
It is now possible to upload a JPEG file as an image in LGL Forms. And as mentioned earlier, the allowable file size has increased here from 10 MB to 20 MB.
We have added text to clarify that in an LGL form the Venmo button can be displayed only if PayPal is enabled.
We have added API documentation clarifying that parameter values must be URL-encoded.
We have updated our API documentation around null values to clarify what users can expect to be returned in those cases.
It is now possible to add notes to constituent profiles using the API. Users can now create and update notes, as well as add note types in Types management.
Some users experienced issues when attempting to scroll in the left column of the page. This has been fixed.
Users attempting to add a gift to an inactive record via the API did not receive an error and the attempt appeared to be successful. We have made an update so the API rejects attempts to create a gift for a constituent record that has been deleted.
The Giving Summary report previously had a calculation error, so in some cases the pledge payments and the pledge total were both included in calculations. This has now been fixed.
Some users experienced the Gifts by Tier fundraising view sorting the gift tiers out of order. This has now been fixed.
In the submission queue, sometimes interest level was displayed as its numerical value instead of the description. This has now been updated.
In Reports, PDF templates are unavailable when returned results exceed 3,000 records. This was causing confusion, so we have updated the text on the Reports page to clarify this. There was also a bug preventing the PDF report from being available even if the search was updated to have fewer than 3,000 results. This has also been fixed.
Previously, a cloned gift would not include any custom gift fields that had been assigned to the original gift. That has now been fixed.
Cloning gifts that had tribute information associated with the original gift would sometimes result in tribute information being carried over when not desired. This has been fixed.
When a constituent record was cloned, some categories were previously not retained in the cloned record. This has now been fixed.
Cloned mailings with complex queries remained linked to the same query as the original, so changing the query for one resulted in changes to both the original and cloned result set. This has been fixed so the original and clone are now pointing to their own queries.
Due to changes in Zapier, matching preferences were not being accurately applied for imports. This has been corrected.
In searching goals, the “Goal Date” search criteria was misnamed “Gift Date”, leading to confusion. This has been fixed.
When adding a gift in LGL for someone who was tagged as “do not email”, the application previously displayed the “[this person] can receive acknowledgments via email” notification even though the constituent would have been excluded when the emails were sent given the communication tag. We have updated the interface so it’s clear when users cannot receive acknowledgments via email due to their communication tag status.
When attempting to export data, some users experienced the report fields not updating when a new report template was selected. This has been fixed.
In our QBO integration, the deposit sync previously allowed multiple clicks/submits, which resulted in duplicate sales receipts. This has been corrected.
When resetting the “Connect to LGL Appeal” dropdown field to a new appeal, the values were reset only for Constituent #1 and not for any additional constituents that were mapped. This has been fixed.
Some users found that when the domain for an email address contained mixed case letters, the email would not appear as a valid sender. This has been fixed.
Some links in the unpaid recurring donation section of LGL Forms were not valid. These have now been updated.
Some users could not view uploaded image files in LGL Forms by clicking “View Files” on the submission summary page. This was caused when the filename contained specific characters. We have fixed this issue.
The presence of quotation marks in the “Map Values” field name in LGL Forms previously caused an error. This has now been fixed.
Some users were experiencing difficulty when attempting to add a section to a form that contained links. This has now been fixed.
Some users were experiencing the error “Resubmitting payment failed – wrong number of arguments (given 3, expected 2)” instead of the decline error when resubmitting a failed payment. This has now been fixed.
“Complete payment” links for unpaid transactions were taking users to an admin URL first and then redirecting to the payment page. We have updated this so the links go directly to the payment page.
In Forms, recurring donations that were in the pending transfer state were previously sometimes appearing on the failed donation page. This has been fixed.
In some instances, PayPal Complete Payments was previously not storing the transaction ID. This has been fixed.
The link to send a test email confirmation was previously displayed even when no email confirmation had been set up. This has been fixed.
Though it is required for a rule always to have a form field selected, previously there was no error message displayed when this occurred. This has now been fixed.
Some default fields, such as “Country”, were previously not saving when set. This has been fixed.
Errors were previously encountered when viewing submissions or payment schedules when access to the associated Stripe account had been revoked or access to the account was outdated. This has been fixed.
When an image was submitted to an organization 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.
Ready to try LGL? Get your first 30 days free. No credit card required.
