Hello all,

I work for the Episcopal Diocese of Massachusetts and recently we have decided that we will be sharing our RE7 database with our Cathedral, the Cathedral Church of St. Paul.  While we are related organizations, technically this means that two seperate organizations will be sharing one RE database.  While it is clear that there are some donors that the Diocese will deal with and others only Cathedral will solicit, there is definitely going to be some donor overlap, thus creating a bit of a security nightmare!  Is anyone currently in a similar situation that can offer some guidance before the Cathedral completely converts their database to RE?

Thank you!

-Lindsay Morgia

Hi,

One suggestion would be to use constituency codes to build security groups around two different organizations.

For example, constituents who belong to just organization1 could be coded with ORG-1 constituency code; constituents who belong to just organization2 could be coded with ORG-2 constituency code. If there are donors who overlap, they could either have both constituent codes or have just one, such as ORG-1-2. Then when security groups are created in the database administration, those security groups would be given access to ORG-1 or ORG-2 or ORG-1-2 constituencies.

Create individual fund code and than restrict user of each organization by fund code. Similarly, you can also restrict organization by campaign code.  This way each organization will have access to the constituent but they will not be able to see how much they have donated to other organization. This might eliminate duplicate recording of constituent.

 AKD