951 results found
-
Separate, non Follow-Up form to Collect Thank You Notes from Students
The current methods of collecting and delivering specific thank-you notes to donors from students are often difficult. We'd like to see a system where a dedicated thank you note form can be configured and assigned to the student per opportunity and as needed and attached to the request, eliminating the need to use follow up forms. The choice between having fewer common follow ups (general thank you) and a large number of opportunity-specific follow ups (to get a specific follow up) is not a great one. A dedicated way of exporting these or emailing a donor directly would also be…
2 votes -
Batch Re-Assign Follow Ups to a New User (Program Officer Leaving)
We have a Program Officer who is leaving the foundation. She has over 150 follow ups assigned to her. Reassigning to the new Program Officer is going to require that we reassign each one individually. It would be great to have the ability to batch reassign.
2 votes -
Rearrange Decisions and Follow Up Forms List
It would be really helpful for the organizer in me to be able to move around/re-arrange Follow Up Forms as well as Decisions. When creating new ones they go straight to the bottom, but if I could group them together in ways that would help my workflow that would be great!
8 votes -
merge fields
- Allow admins to create additional merge fields for their specific documents. Currently Foundant only has select merge fields without the ability to create new ones.
- Update Follow Ups so that admins can insert merge fields into follow up documents. This feature would be very helpful when we are creating grantee agreements as some fields are available in shared questions.
2 votes -
reassign request or followups to the primary organisation contact when you delete the assocatied contact
When a staff member leaves an organisation - rather than going through and reassigning the requests and follow ups - it would be ideal if the requests and follow-ups associated with their user were automatically reassigned to the primary contact for the organisation.
7 votes -
Batch Build and Edit Committees
Building review committees is time consuming and burdensome. Our list of 130+ volunteer committee participants changes annually. It takes MANY hours to select each existing committee in the universe, review and compare to an existing list for the changes and individually add new members, delete old ones, and build new profiles for net new participant. Building new profiles is also challenging since it can't be done on the committee building page so one needs to navigate to a separate window taking the steps to build a new profile and assign a password (yet another extra step).
It would save many…
5 votes -
Inactive Users Should Not Require an Email Address
Currently if a user is inactive they are required to have an email address. This is not useful when the new user in their role uses the previous employees email address. ie) ceo@testcompany.ca
If the new user uses the previous employees email then you are required to come up with a dummy address for the inactive employee. This is not ideal.
Inactive employees should NOT require an email.
2 votes -
Fund Advisor Portal Reports
After talking to Foundant Support, I think it would be nice for fund advisors to be able to generate reports. Specifically, if fund advisors can pull a report with donor names, addresses, gift amounts, etc., rather than having to click into each donor's profile, would be helpful for the nonprofits and donors we serve.
2 votes -
GLM Initial Set-up of New Account
We've had many grant award checks returned for "no receptacle" or "insufficient address" due to the application in GLM auto filling with whatever address was put in when the organization's account was initially set up. Most people will put their physical address in this spot. It would be helpful if when setting up new accounts in GLM both the mailing address and the physical address of an organization were required, then for the mailing address to be the default for the grant application. Any way around this issue?
1 vote -
Allow us to customize Apply Page ourselves
It would be great if we could customize the students' Apply Page ourselves instead of having to go through chat. The process could be similar to what we can do for our login page under the site settings.
I often want to make tweaks or change minor things and having to go through chat adds an extra layer and creates more work for chat.
2 votes -
No warning for required fields missing on UA questions
On any question type, if you miss a required field and click into the Applicant Opportunities tab to select opp specifics and try to save, there is no warning showing you have missed filling in a required space, the page goes nowhere, nothing occurs.
Please add a warning of some sort that a required field is missing.2 votes -
Customize Data in Metrics Dashboard
The vast majority of the default Metrics Dashboard data is related to decisions and payments/disbursements. Our organization does not facilitate payment through SLM/CSuite, so these charts/datasets are blank/not useful to us at all.
It would be great to be able to customize this dashboard to reflect the data in real-time that is most important to our organization (largely applicant data, so for example, race/ethnicity data, geographic location, number of applicants per program, etc).
2 votes -
Embedded AI checker
Embedded AI checker to note level of AI written language on submissions.
9 votes -
Show Decision Status
Show Decision Status: current setting applies to entire site (available under site settings). Moving this setting to the Process Manager and allowing it to be set individually on each process would open up more flexibility to accommodate different foundation's workflows.
Example: two grant programs are open at the same time. one is a rolling basis application process with fast turn around. the other is a quarterly LOI process involving board meetings. the ideal use of "show decision status" for these two programs would be vastly differently; yet the software is forcing one setting for all.
3 votes -
Limit Checkbox Selections
We would love the ability to limit the number of check marks applicants are able to select on certain checkbox questions. We ask folks to limit the number their choices, but often times they over select.
7 votes -
Randomly Assign Evaluators
In our process each applicant receives at least three reviews from three different evaluators. It would be nice if I could randomly assign evaluators to the applicants. I currently do this by creating an excel file with the applicants on the vertical axis and the evaluators on the horizontal. I assign each applicant a number and use a random number generator to assign the applications each reviewer is expected to review. To be able to do this quickly within the GLM system would be great. I know some of the competitors provide this option.
5 votes -
evaluation deadline reminder
Wouldn't it be wonderful if we could program LOI/Application Evaluation Dates into the process AND ALSO set up automater reminder emails that go to assigned evaluators before these deadlines?!
3 votes -
It would be nice to be able to edit the text in the Apply screen directly without having to request changes from the support team.
It would be nice to be able to edit the text in the Apply screen directly without having to request changes from the support team.
2 votes -
You should be able to close requests even if follow ups are still outstanding
We have a process where we give grants out - the applicant has to complete the grant contract and then submit a grant evaluation at school year end. However, some never submit their evaluations. We do not let them be eligible to apply for another grant unless all their evaluations have been submitted, so we do not want to close or abandon any of the outstanding follow up forms that say "MSHE Grant evaluation". However, at the end of the cycle, I want to be able to close out all my grant contracts that have been completed, however, since a…
10 votes -
Melanie.Frazier@state.mn.us
For GLM under website settings, "Warn Applicant of an Existing Request," if this could be for applications submitted by organization. For example, a user from an organization submitted an application but then another user tries to apply for the same grant opportunity. The user trying to submit the 2nd application would be notified that an application was already submitted. There may be instances when there are multiple programs within one organization are applying for a grant, if that's the case, allow multiple programs to be identified under one umbrella organization.
2 votes
- Don't see your idea?