Development Security Objects

I can’t point you to a document, Jesse, but I know that we chose to Control Group all Development Campaigns so that employees of another organization who provide box office services to us would not be able to see giving information (in addition to blocking access to the contributions tab and entry module).  That one step hid all gifts, associated transactions, and payments from those without access to that control group.  We had to make some additional careful decisions, like restricting access to certain reports, altering their constituent header, etc.

I'm facing some resistance from some of my colleagues in other departments on setting security for their groups. Since they are slow to do this and I am worried about an inadvertent or otherwise breach I would like to help them out by showing them which areas are off limits to them.

So can anyone point me to a document that goes over best-practice suggestions for which objects non-development people should stay the hell away from?

Thanks!

Jesse Cohen

Director of Development and Communications

The Metropolitan Opera Guild

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!

I can’t point you to a document, Jesse, but I know that we chose to Control Group all Development Campaigns so that employees of another organization who provide box office services to us would not be able to see giving information (in addition to blocking access to the contributions tab and entry module).  That one step hid all gifts, associated transactions, and payments from those without access to that control group.  We had to make some additional careful decisions, like restricting access to certain reports, altering their constituent header, etc.

I'm facing some resistance from some of my colleagues in other departments on setting security for their groups. Since they are slow to do this and I am worried about an inadvertent or otherwise breach I would like to help them out by showing them which areas are off limits to them.

So can anyone point me to a document that goes over best-practice suggestions for which objects non-development people should stay the hell away from?

Thanks!

Jesse Cohen

Director of Development and Communications

The Metropolitan Opera Guild

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!