Restrict Security Rights

Le Wynnie
Le Wynnie
Sixth Anniversary Kudos 1 Facilitator 1
in Blackbaud Raiser's Edge NXT®: General Discussions
Hi,


We are in the phase of moving all of our department data to RENXT. However, the biggest concern for everyone is the security. Each of the department is willing to grant other department access to view their data BUT they don't want them to see specific information such as Research note or Actions. They also don't want the other department to be able to run/export any list that contains their data either. But it doesn't look like it's feasible in RE in general at the moment. As long as they can VIEW the data, they can access the list in RENXT. Is anyone here in the similar situation and have a better work around system?


Thank you,

Wynnie

Comments

  • Le Wynnie
    Le Wynnie
    Sixth Anniversary Kudos 1 Facilitator 1
    Hi Bill,


    Thank you for responding back to me. The Note is just an example. Restricting someone from viewing a specific field as a user is not an issue. However, the issue restricting them from viewing certain information according to the Constituency Code. 


    Currently, I've categorized each fundraising department by Constituency Code and then use Security by Constituency Code to restrict viewing rights. I'll give you an example of our current situation:


    The Corporate Sponsor department is only allowing the Individual Fundraising department to view their data only. They don't want the Individual Fundraising department to edit (which is no problem to configure) or run lists and reports which will contain data from the Corporate Sponsor department. However, the current setup in RE is that if they can VIEW the data, they can run lists.


    I would love to attend your webinar. Can you send me the link to signup?


    Thank you!

    Wynnie
  • Bill Connors
    Bill Connors
    Tenth Anniversary Kudos 5 First Reply Name Dropper
    Hi, Wynnie.  You are correct, it is not possible to let someone view data in the constituent record but then not see it or use it elsewhere.  When I've encountered this in the past, it's seemed there was too much politics and too little lack of trust.  If people working in the same organization are professionals that can be trusted, it shouldn't be an issue.  If they're not, well, should they be working there?  There's always going to be types of data that people can do things with but they shouldn't, and it can't all be controlled with minute levels of security.  Of course I can't speak to the situation at your organization and how big of a deal this should or should not be, but it's unlikely Blackbaud will ever prioritize this to make it a function.  The request and legitimate need for it is too rare.  And most users don't use the security options they have, let alone are begging for more granularity.  But, of course, not my decision to make.  :)


    The session next week is part of bbcon and you can register here (free, and it's online):  https://www.bbconference.com/  Hope to "see" you there!  
  • Marilyn Shriver
    Marilyn Shriver
    Seventh Anniversary Participant Facilitator 1 Blackbaud Certified
    I'm running into the issue of trust in my organization. A new campus partner wants to record his relationships and conversations. He is in a position to raise a lot of money for his unit.  I'm getting a lot of push-back from Advancement Services, saying we need a written policy and all kinds of restrictions. Do you have any examples of written policies and procedures?
  • Le Wynnie
    Le Wynnie
    Sixth Anniversary Kudos 1 Facilitator 1
    I don't know if this will help but for our migration, I wrote an agreement document for all departments to sign.  


    1. The pros, cons, and risks of data sharing and vice versa

    2. The responsibilities of data protection

    3. The number of users, names of users, and their title


    Wynnie
  • Marilyn Shriver
    Marilyn Shriver
    Seventh Anniversary Participant Facilitator 1 Blackbaud Certified
    Wynnie, are you willing to share that document?
  • Julie Lytle
    Julie Lytle
    Eighth Anniversary Facilitator 1
    This is a great idea Wynnie!  I currently restrict who even gets access to the system.  Once they are approved very clear guidelines are established.  If they break them they run the risk of having their access taken away.  I, inherited a database that was not clean and one where way to many people had access and rights.  It was impossible to maintain!  So we had to get a little tough and set clear policies and procedures with clear cut "penalties".  Not fun, but we have seen a dramatic turnaround in the quality and accuracy of our data, not to mention that I have fewer gray hairs! 
  • Le Wynnie
    Le Wynnie
    Sixth Anniversary Kudos 1 Facilitator 1

    Marilyn Shriver:

    Wynnie, are you willing to share that document?

    Hi Marilyn, 

    What's your email? I can send you our current template. Hopefully it be able to help you a little bit.


    Wynnie

  • Le Wynnie
    Le Wynnie
    Sixth Anniversary Kudos 1 Facilitator 1

    Julie Lytle:

    This is a great idea Wynnie!  I currently restrict who even gets access to the system.  Once they are approved very clear guidelines are established.  If they break them they run the risk of having their access taken away.  I, inherited a database that was not clean and one where way to many people had access and rights.  It was impossible to maintain!  So we had to get a little tough and set clear policies and procedures with clear cut "penalties".  Not fun, but we have seen a dramatic turnaround in the quality and accuracy of our data, not to mention that I have fewer gray hairs! 

    I feel your pain. When I inherited the database, believe or not EVERYONE had supervisor rights. It was quite scary. 


    But I do think that a guided document is definitely needed. I had to create one because we are migrating other department data to RENXT and everyone is sensitive about their data. 


    Wynnie

  • Marilyn Shriver
    Marilyn Shriver
    Seventh Anniversary Participant Facilitator 1 Blackbaud Certified

    Hi, Wynnie –
    Thanks for sending your document about rights restrictions. Very
    much appreciated!

     

    Marilyn Shriver, CFRE

    Director of Development

    Advancement Division

    Keene State College

    Office: (603) 358-2371

    Mobile: 603-209-9255

    Fax: (603) 358-2400

    marilyn.shriver@keene.edu

     

     

  • Jenny Marquardt
    Jenny Marquardt
    Ninth Anniversary Kudos 3 Name Dropper Participant

    Hi Wynnie,

     

    May I please get a copy?

     

    Thanks so much!

    Jenny

     


    Jenny
    Stephens, bCRE-Pro

    Director, Donor Analytics and Information Management

    Development Office


    T 626
    396-2483 or C 818-396-2691
    Jenny.Stephens@artcenter.edu


    ArtCenter
    College of Design

    1700 Lida St.

    Pasadena, CA 91103
    www.artcenter.edu


     

  • Le Wynnie
    Le Wynnie
    Sixth Anniversary Kudos 1 Facilitator 1
    Hi Jenny,


    Here's the template I created. 



    It's not a fancy document. The purpose of this form is to get
    the agreement in writing and capture all the requested users.



    I hope this helps a little.



    Thanks,

    Wynnie

  • Le Wynnie
    Le Wynnie
    Sixth Anniversary Kudos 1 Facilitator 1


    Hi Marilyn,



    Here's the template I created. 



    It's not a fancy document. The purpose of this form is to get
    the agreement in writing and capture all the requested users.



    I hope this helps a little.



    Thanks,

    Wynnie


  • Marilyn Shriver
    Marilyn Shriver
    Seventh Anniversary Participant Facilitator 1 Blackbaud Certified
    Wynnie, was there supposed to be an attachment? I don't see anything.
  • Darlene Wolf
    Darlene Wolf
    Eighth Anniversary Name Dropper Participant Facilitator 1
    Wynnie, could I also get that template. We have no policies and procedures and I can use all the help I can get as I try to create some.

    wolf@landinstitute.org

     

Categories