Settings and activity
153 results found
-
14 votes
Conner Peckham
supported this idea
·
-
21 votes
An error occurred while saving the comment
Conner Peckham
supported this idea
·
-
9 votes
Conner Peckham
supported this idea
·
-
5 votes
Conner Peckham
supported this idea
·
-
5 votes
Conner Peckham
supported this idea
·
-
7 votes
Conner Peckham
supported this idea
·
-
7 votes
Conner Peckham
supported this idea
·
-
2 votes
An error occurred while saving the comment
Conner Peckham
commented
We've experienced this, as well. We had Foundant edit the label of the core fields in the Organization Summary section (which are also the registration fields) to be Mailing Address/City/State and then added a new field for Building Address (if different). This keeps the core address fields, which get merged into emails and reports that go to our payables team, the mailing address and has helped with mailing grant checks.
-
3 votes
Conner Peckham
supported this idea
·
-
5 votes
Conner Peckham
supported this idea
·
-
3 votes
Conner Peckham
supported this idea
·
-
3 votes
Conner Peckham
supported this idea
·
-
31 votes
Conner Peckham
supported this idea
·
-
4 votes
Conner Peckham
supported this idea
·
-
109 votes
Hey All,
Would you need multiple levels of folders or would one level be enough?
An error occurred while saving the comment
Conner Peckham
commented
One level would be helpful, but we would absolutely use multiple folder levels if available. A quick example that comes to mind of how we'd use multiple levels:
Level 1: Process Name
---Level 2: LOI/App
------Level 3: LOI/App Received
------Level 3: Reminders
---Level 2: Approved
------Level 3: Reminders
---Level 2: Declined
Conner Peckham
supported this idea
·
-
8 votes
An error occurred while saving the comment
Conner Peckham
commented
I'd like to bring this idea back to the top of the queue, especially as the Organization Summary redesign is underway. We would greatly appreciate an audit trail when organizations are merged so that we can easily tell which organizations were merged and when. Ideally, the merged data that was not selected as primary would still live in the system in an audit trail rather than be overwritten by the primary org's data so that if there were ever an error made, we could still access that information.
Conner Peckham
supported this idea
·
-
8 votes
Conner Peckham
supported this idea
·
-
8 votes
An error occurred while saving the comment
Conner Peckham
commented
We would absolutely use this if it were available. Currently we have an Excel template we created to assign scores to specific questions, but if the system could do it that would be great.
Conner Peckham
supported this idea
·
-
86 votes
Thank you for the idea.
Would you hope this is implemented across all processes?
An error occurred while saving the comment
Conner Peckham
commented
Agreed. When creating a new process, having the ability to toggle on a "Prevent the creation of a new LOI/Application if a pending/overdue follow-up exists for the following existing processes" option (with all existing processes available with checkboxes) would be amazing. We have some processes where orgs can apply no matter their participation in another grant, but some processes that are very specific around how often they can reapply.
Conner Peckham
supported this idea
·
-
91 votes
Conner Peckham
supported this idea
·
I agree. It would be amazing to be able to set up an automated email at any part of the workflow. For both internal and external audiences and not be limited to only certain workflow states and only one email per audience. Allow us to set up as many emails as we need so that it truly works the way we need it to.