Ability to restrict gift entry by Gift Type based on Security Group
We have a policy that all CASH gifts need to be entered in Batches which tie to actual bank deposits and are used for reconciliation. Pledges are entered on a donors record (before the payment). On occaision an error was made where employee meant to enter a pledge, but did not change the gift type. Would like to either restrict users to only enter Cash or PAY CASH in Batch ONLY - OR restrict what types of gifts a user can enter based on the security group they belong too. The initial settings can be defaulted to the way they are now so that admins in all orgs wont need to go crazy changing security groups - however it would offer us a bit of control that the product does not currently have
-
Guest
- Jun 21 2012
Related ideas
We strongly request a way to lock down gift entry by gift type especially since that is one thing that cannot be corrected without creating an entirely new gift entry. We need to restrict some users to Gifts-in-kind only, and also pledge versus cash. This is especially important since cash gifts in RENXT are the default gift type and listed as "one-time gift" so it is not obvious to in-kind data entry specialists to double check that.
It would be helpful to create security rights based on gift type. This will support all nonprofits and their reconciliation processes with Finance. I would like only certain users to be able to enter pledges because at many nonprofits I've worked with, fundraisers will add pledges after the month "closes" because they have the ability to do so in RE however this creates a huge headache in clean reconciliations and reporting because new "late add" gifts have been added into months that should have been closed. Right now reconciliations is all theoretical in RE meaning even though the month is clean and accounted for, it could change by a simple mistake or late addition. There should be the ability to backdate pledges but this could exist at the Admin level versus changing information that at some point should become static. For end of year, historical and month by reconciliations and reporting, limiting security rights for adding gifts by type would be helpful.
This functionality would help our organization as well because we do not use the "Other" gift type and our gift entry folks sometimes get confused between gift type and payment method, so when there is an odd payment method (like, an insurance premium or expenses donated), they sometimes use the gift type "Other". If I had access to the table to make it inactive, I would. If I could create a business rule to pop up upon saving the gift that warned users against using the "Other" gift type, I would. But this would solve the problem, too.
We would prefer limiting access to staff that should be allowed to manage (add/edit) planned gifts, but not be able to manage (add/edit) regular gifts. Restricting by gift type would allow us further control over this functionality and reduce errors.