FundSvcs Community

 View Only
  • 1.  Centralized

    Posted 03-12-2025 03:28 PM

    Hello everyone,

    We are exploring the possibility of allowing campus partners access to our fundraising CRM to manage non-fundraising relationships. The idea is that having insight into vendor and university contacts could benefit our prospect researchers and gift officers.

    However, we have some concerns. Our CRM is purpose-built for fundraising, as well as alumni and parent engagement, so adapting it to meet the needs of non-fundraising groups would require significant effort in system configuration and reporting. Additionally, we are mindful of potential risks, such as campus partners inadvertently using donation information inappropriately (e.g., selecting vendors based on their giving history). We have other hesitations but those are the main two.

    Has anyone centralized non-fundraising relationship management within your fundraising CRM? If so, how has it worked for your institution, and what challenges have you encountered?

    Looking forward to your insights!



    ------------------------------
    Rachel Ellis
    Point Loma Nazarene University
    rellis2@POINTLOMA.EDU
    ------------------------------


  • 2.  RE: Centralized

    Posted 03-14-2025 08:50 AM

    We have granted access to a few colleagues in other departments. The main things we have had to look out for:

    • License count limitations. We use Salesforce so we have a set number of licenses available and had to strategically provide access to folks
    • Data storage limits - we regularly review our data storage to make sure we keep a good buffer between our storage max
    • Security/Privacy. Making sure there is some way to limit non-pertinent fields to other partners through permission lockdown (view, edit, create, delete)

    It does have its pros of having our partners enter in their own contact reports which saves us time and paints a more comprehensive picture for us of a constituent's engagement with us vs us not having access to that information or it living in another system. 



    ------------------------------
    Miranda Luna
    Linfield University Advancement
    mluna@linfield.edu
    ------------------------------



  • 3.  RE: Centralized

    Posted 03-14-2025 09:30 AM

    I would echo the need for security. For example, do these external users have a business need to see the giving history on your donors, if they are using your system to manage vendors and vendor contracts?

     

    One big example I recall on our end was a customization our developers built to allow our athletics department to manage ticket sales. The ticket reps had very little access to our system – they could enter interactions/contact reports, but they could not see any giving history. Eventually, they just decided not to use our system anymore. I think the idea was that we would benefit from having these people in our system and see their engagement. One major problem was the quality of the data, because it was coming from a system where people could buy tickets and sometimes enter completely different name and contact information each time they ordered, so there were tons of duplicates. I'm not sure we got a great ROI on that project, and all the work our developers did was for naught when they stopped using the system. We also ended up deleting about 100K records that we had loaded, because the data was bad and there was no engagement from many of the constituents we had loaded for the project.

     

     

    Kelli Crispin

    The University of North Carolina at Chapel Hill 

    Office of University Development

    E  kelli.crispin@unc.edu