Hiding Constituent Records

Hey all,

I'm trying to figure out a way to hide a batch of constituent records from view for everyone but our Development Team.  Does anyone know how one might do this?

Thought about doing this by assigning them all to a new Constituent Type and restricting that Type to the Development Security Control Group only, but it doesn't look like this is an option.  

Any ideas?  Has anyone done this before? 

  • You can't really hide records but you can control group data on them like address, email and alias type.

    If it really is a necessary business need, you could put generic data on the general tab, including name. The real name can then be stored as a control grouped alias which is searchable only by anyone in the Development user group.

    Be aware that this will potentially lead to duplicate records because other users outside Development won't be able to search for these constituents!  If that sounds too dire, perhaps keep the real name on the general tab and control group everything else.

  • You will not be able to hide the general tab information, but all other info should be able to be control groups so only they can view it.  We are in a consortium and that method has worked well for us.  You could place dummy info on the general tab and all the real information deeper if the general tab is a concern.  

    Sent from my iPhone

    On Mar 10, 2015, at 6:33 PM, "Naomi Satake" <bounce-naomisatake1832@tessituranetwork.com> wrote:

    Hey all,

    I'm trying to figure out a way to hide a batch of constituent records from view for everyone but our Development Team.  Does anyone know how one might do this?

    Thought about doing this by assigning them all to a new Constituent Type and restricting that Type to the Development Security Control Group only, but it doesn't look like this is an option.  

    Any ideas?  Has anyone done this before? 




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
  • Ah, that's too bad. 

    We're planning on importing a lot of potential duplicate records and wanted to hide these from view from other departments to prevent ticket sales, etc from being recorded in these temporary records.  Perhaps we'll attempt to import all of the addresses into a restricted address type and put "unknown"s on the general page.  Woof.