Answers.Body: <p>One way of approaching it is with a handful of smart groups:</p>
  
  <p>Lets assume you create compliance officers as individuals and link them with a 'Compliance officer is/of' relationship</p>
  
  <p>1) Create a smart group of 'Compliance officers of member orgs' by using Advanced Search to search for organisations that have a current membership and setting 'Display Results as' to 'Related contacts' and the relationship as 'Compliance officer of' - this is the first group to add to your mailing.</p>
  
  <p>2) Create a smart group of 'Member Orgs'</p>
  
  <p>3) Create a smart group of 'Member orgs with compliance officers' by searching for members with a 'compliance officer is' relationship</p>
  
  <p>4) Create a smart group for 'Member orgs without compliance officers' using  Search > Custom Search > Include/Exclude search and the last two groups you just created</p>
  
  <p>5) Create a smart group of 'Main contacts of member orgs without compliance officers' similar to 1) using 'Member orgs without compliance officers' and Related contacts/Main contact of - This is the second group to add to your mailing.</p>
  
  <p>Use too many layers of smart groups and your server will be gasping for air, but it might work if your numbers are not too large. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-30T21:12:48.510Z
Answers.Text: Smart, this proves the possibility to accomplish this by using merely configuration. So no developer skills are needed. A developer mindset however helps.
Answers.UserDisplayName: Kainuk - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-29T19:36:20.630Z
Answers.LastActivityDate: 2017-08-29T19:36:20.630Z
Answers.UserDisplayName: Aidan
Answers.Body: <p>A different approach would be to have a 'compliance' email address on the organisation and use rules triggered on relationship changes to update that address to be compliance or main contact as appropriate.</p>
  
  <p>A variant of that is to use a Contact Reference custom field on your org updated by rules on relationships - or just updated manually depending on the workflow.</p>
  
  <p>Several options with different implications ... depends what works for you.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-30T21:14:43.377Z
Answers.Text: At the moment I suppose the need is to mail a list with compliance officers (or their main substitutes),  so I think I cannot use the email address
Answers.UserDisplayName: Kainuk - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-29T19:42:05.857Z
Answers.LastActivityDate: 2017-08-29T19:42:05.857Z
Answers.UserDisplayName: Aidan
Answers.Body: <p>Not sure I fully get the issue. Using different relationships types would seem the obvious answer, but am thinking that isn't what you are asking for.</p>
  
  <p>Key thing is that whoever does the renewal must have a Permissioned Relationship, so if you need to separate the 'default' from the others then you may be able to do it by creating custom groups that differ based on whether the relationship is Permissioned or not</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-28T20:41:45.593Z
Answers.LastActivityDate: 2017-08-28T20:41:45.593Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I am working for a customer that has organizations as members.  The employees are also registered, and a member organization must have a main contact. All official communication is sent to the main contact. </p>
  
  <p>But sometimes a member has a compliance officer, depends on the size.
  Special mailings about compliance must be sent to the compliance officers if an organization has one. Otherwise, it must be addressed to the main contact.
  We have not decided yet register the compliance officer. It can be a separate relationship or a group on the contact.</p>
  
  <p>Any tips how to achieve this?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-29T18:52:50.360Z
Comments.Text: Are you meaning: for each member organisation, if there is a compliance officer, email the compliance officer, otherwise email the main contact ?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-29T18:57:39.393Z
Comments.Text: Well summarized.
Comments.UserDisplayName: Kainuk - CiviCooP
Tags: <groups><relationships><configuration>
Title: How to mail to the default contact person of a member organization with more employees?
ThreadText: # How to mail to the default contact person of a member organization with more employees?
  
  (Asked by: username_0 on 2017-08-28)
  
  I am working for a customer that has organizations as members. The employees are also registered, and a member organization must have a main contact. All official communication is sent to the main contact.
  
  But sometimes a member has a compliance officer, depends on the size.
  Special mailings about compliance must be sent to the compliance officers if an organization has one. Otherwise, it must be addressed to the main contact.
  We have not decided yet register the compliance officer. It can be a separate relationship or a group on the contact.
  
  Any tips how to achieve this?
  
  **Tags:** groups, relationships, configuration
  
  > **Comments:**
  > **username_1**: Are you meaning: for each member organisation, if there is a compliance officer, email the compliance officer, otherwise email the main contact ?  
  > **username_0**: Well summarized.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2017-08-29. Score: 2
  
  One way of approaching it is with a handful of smart groups:
  
  Lets assume you create compliance officers as individuals and link them with a 'Compliance officer is/of' relationship
  
  1) Create a smart group of 'Compliance officers of member orgs' by using Advanced Search to search for organisations that have a current membership and setting 'Display Results as' to 'Related contacts' and the relationship as 'Compliance officer of' - this is the first group to add to your mailing.
  
  2) Create a smart group of 'Member Orgs'
  
  3) Create a smart group of 'Member orgs with compliance officers' by searching for members with a 'compliance officer is' relationship
  
  4) Create a smart group for 'Member orgs without compliance officers' using Search > Custom Search > Include/Exclude search and the last two groups you just created
  
  5) Create a smart group of 'Main contacts of member orgs without compliance officers' similar to 1) using 'Member orgs without compliance officers' and Related contacts/Main contact of - This is the second group to add to your mailing.
  
  Use too many layers of smart groups and your server will be gasping for air, but it might work if your numbers are not too large.
  
  > **Comments:**
  > **username_0**: Smart, this proves the possibility to accomplish this by using merely configuration. So no developer skills are needed. A developer mindset however helps.  
  
  ---
  
  ### Answer by username_1 on 2017-08-29. Score: 2
  
  A different approach would be to have a 'compliance' email address on the organisation and use rules triggered on relationship changes to update that address to be compliance or main contact as appropriate.
  
  A variant of that is to use a Contact Reference custom field on your org updated by rules on relationships - or just updated manually depending on the workflow.
  
  Several options with different implications ... depends what works for you.
  
  > **Comments:**
  > **username_0**: At the moment I suppose the need is to mail a list with compliance officers (or their main substitutes),  so I think I cannot use the email address  
  
  ---
  
  ### Answer by username_2 on 2017-08-28. Score: 1
  
  Not sure I fully get the issue. Using different relationships types would seem the obvious answer, but am thinking that isn't what you are asking for.
  
  Key thing is that whoever does the renewal must have a Permissioned Relationship, so if you need to separate the 'default' from the others then you may be able to do it by creating custom groups that differ based on whether the relationship is Permissioned or not
  
  
  ---
  
  