Best Practices for Emails and Contact Points/Permissions for Consortiums

Does anyone have any guidance on what are the best practices for emails and contact points / permissions for consortiums?  Our member organizations were implemented at different times and are using the Tessitura functionality differently and I'm trying to determine which practices we should standardize on. (Some of the organizations are using contact purposes and/or permissions now and I'm working on setting the others up.)  Is it necessary for each organization have it's own control-grouped email type for any of their customers?  Should the contact permissions (which are control grouped) be tied to a control-grouped email vs. the non-control grouped one?  How should output sets be managed to facilitate the process of each organization pulling emails for their e-news and ticket information (not all of our organizations use WordFly and there are concerns about one organization pulling another's emails).  If this has been discussed before or presented at TLCC, I'd love to see that info.  If not, is there any interest in discussing this at TLCC? 

Parents
  • To be sure, Contact Permissions are not connected to emails (or other Contact Types), but are connected to the constituent instead.

    I can't be much help here: we keep our customer accounts separate, so we can leave decisions like this completely up to the consortium members for their org.  We are, finally, all using Contact Permissions, though.

Reply
  • To be sure, Contact Permissions are not connected to emails (or other Contact Types), but are connected to the constituent instead.

    I can't be much help here: we keep our customer accounts separate, so we can leave decisions like this completely up to the consortium members for their org.  We are, finally, all using Contact Permissions, though.

Children
No Data