Answers.Body: <p>Yes, that checkbox must be checked. (The one reflecting the specific "direction" you wish.</p>
  
  <p>I don't think you can configure this to occur automatically, however since you have custom code, it should be possible to add the permission automatically using an API call (the parameter name I believe is <code>is_permission_a_b</code> or <code>is_permission_b_a</code>).</p>
  
  <p>Here's an API call:</p>
  
  <pre><code>$result = civicrm_api3('Relationship', 'create', array(
    'sequential' =&gt; 1,
    'contact_id_a' =&gt; "",
    'contact_id_b' =&gt; "",
    'relationship_type_id' =&gt; "",
    'is_permission_a_b' =&gt; "",
    'is_permission_b_a' =&gt; "",
  ));
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-02T18:05:46.830Z
Answers.Text: Thank you for your answer k3ix.  
  I am surprised that there is not a feature on a relationship to say that (in this example) the individual will automatically be able to view and edit the information on the basis that they are a station administrator.  
  I may be putting in a new support ticket!
Answers.UserDisplayName: Darren Whittenham-Gray
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-02T18:27:30.100Z
Answers.Text: Darren, I suspect that such capability may have been intentionally omitted.  It would be too easy for a system to be configured to always set the permission and then forget about it.... with ultimately some contacts getting permissioned where they shouldn't be.
Answers.UserDisplayName: DaveD
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-03T02:35:18.147Z
Answers.Text: It would be bad to always grant the permission on employee relationships: if you collect employer name on a public form, someone could just change employer repeatedly to get access to a bunch of contacts.
Answers.UserDisplayName: Andie Hunt
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-02T17:04:12.553Z
Answers.LastActivityDate: 2015-04-02T17:13:36.283Z
Answers.LastEditDate: 2015-04-02T17:13:36.283Z
Answers.UserDisplayName: DaveD
Answers.Body: <p><a href="https://civicrm.org/extensions/relationship-permissions-acls" rel="nofollow">Relationship Permissions as ACLs</a> doesn't fully work in CiviCRM 4.6.x (please refer to issue here <a href="https://issues.civicrm.org/jira/browse/CRM-17349" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-17349</a>) </p>
  
  <p>There is a good news for "permissioned relationships" fans: sounds like CiviCRM (at least 4.6.10) not only allows "one to one" permissions via relationship; it has also build-in support for inherited permissions via relationships via "Allow second-degree relationship permissions" radio button at Administer->System settings->Misc . </p>
  
  <p>It's truly brilliant for use cases, where (quote):  <strong>contacts with the permission to edit a related contact will inherit  that contact's permission to edit other related contacts.</strong></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-05T21:08:43.847Z
Answers.LastActivityDate: 2015-11-05T21:08:43.847Z
Answers.UserDisplayName: yurg
Answers.Body: <p>There is an extension that does exactly what you're looking for:</p>
  
  <p><a href="https://civicrm.org/extensions/relationship-permissions-acls">Relationship Permissions as ACLs</a></p>
  
  <p>The release on the extensions page only does 1 thing (setting permissioned relationships to <em>actually</em> give acl permissions to those contacts, which CiviCRM does not do by default) but if you download the extension directly from github, it has the feature you are looking for (automatically adding certain permissions for certain relationship types). I believe the reason you have to download that version manually is because of a dependency on another extension (also available from github) and the automatic extension downloader does not resolve dependencies.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-02T21:35:58.220Z
Answers.Text: Evening Coleman,  
  I have just read through the requirements of Entity Settings and the 1.2 branch of Relationship Permissions.  
  
  I think this is going to need me to go much deeper into the code of the site than I am competent at doing. To me it looks like I have to go in via the file system to install 1.2?
  
  It looks like I will be batting this off to our developers to do! 
  
  Thank you for your help though...
Answers.UserDisplayName: Darren Whittenham-Gray
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-03T01:00:40.860Z
Answers.Text: Good luck getting it working :)
Answers.UserDisplayName: Coleman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-02T19:38:43.050Z
Answers.LastActivityDate: 2015-04-02T19:38:43.050Z
Answers.UserDisplayName: Coleman
Body: <p>I am currently using D7.35 and Civi4.4.14</p>
  
  <p>We have custom relationships on our Civi installation. What I would like them to do is give the individual permission to view and edit the organisation which for some reason worked in development and not in the real world.... I think because the first tick box is unticked.... right?:</p>
  
  <p><img src="https://i.sstatic.net/t8N3B.png" alt="Relationship Box"></p>
  
  <p>So there are probably two questions:</p>
  
  <ol>
  <li>Am I Right?</li>
  <li>How can I get Civi to allocate this automatically?</li>
  </ol>
  
  <p>There is a bit of further information. </p>
  
  <p>Our developer custom coded the module designed for our member management system. So a Station Administrator (as per the picture) and promote or demote within his station without our intervention using a custom page where a number of relationships are managed.</p>
  
Tags: <permissions><relationships>
Title: How do I set up custom permissive relationships?
ThreadText: # How do I set up custom permissive relationships?
  
  (Asked by: username_0 on 2015-04-02)
  
  I am currently using D7.35 and Civi4.4.14
  
  We have custom relationships on our Civi installation. What I would like them to do is give the individual permission to view and edit the organisation which for some reason worked in development and not in the real world.... I think because the first tick box is unticked.... right?:
  
  ![Relationship Box](https://i.sstatic.net/t8N3B.png)
  
  So there are probably two questions:
  
  1. Am I Right?
  2. How can I get Civi to allocate this automatically?
  
  There is a bit of further information.
  
  Our developer custom coded the module designed for our member management system. So a Station Administrator (as per the picture) and promote or demote within his station without our intervention using a custom page where a number of relationships are managed.
  
  **Tags:** permissions, relationships
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_4 on 2015-04-02. Score: 5 | Accepted answer
  
  There is an extension that does exactly what you're looking for:
  
  [Relationship Permissions as ACLs](https://civicrm.org/extensions/relationship-permissions-acls)
  
  The release on the extensions page only does 1 thing (setting permissioned relationships to *actually* give acl permissions to those contacts, which CiviCRM does not do by default) but if you download the extension directly from github, it has the feature you are looking for (automatically adding certain permissions for certain relationship types). I believe the reason you have to download that version manually is because of a dependency on another extension (also available from github) and the automatic extension downloader does not resolve dependencies.
  
  > **Comments:**
  > **username_0**: Evening username_4,   I have just read through the requirements of Entity Settings and the 1.2 branch of Relationship Permissions.    I think this is going to need me to go much deeper into the code of the site than I am competent at doing. To me it looks like I have to go in via the file system to install 1.2?  It looks like I will be batting this off to our developers to do!   Thank you for your help though...  
  > **username_4**: Good luck getting it working :)  
  
  ---
  
  ### Answer by username_1 on 2015-04-02. Score: 5
  
  Yes, that checkbox must be checked. (The one reflecting the specific "direction" you wish.
  
  I don't think you can configure this to occur automatically, however since you have custom code, it should be possible to add the permission automatically using an API call (the parameter name I believe is `is_permission_a_b` or `is_permission_b_a`).
  
  Here's an API call:
  
  ```
  $result = civicrm_api3('Relationship', 'create', array(
    'sequential' => 1,
    'contact_id_a' => "",
    'contact_id_b' => "",
    'relationship_type_id' => "",
    'is_permission_a_b' => "",
    'is_permission_b_a' => "",
  ));
  
  ```
  
  > **Comments:**
  > **username_0**: Thank you for your answer k3ix.   I am surprised that there is not a feature on a relationship to say that (in this example) the individual will automatically be able to view and edit the information on the basis that they are a station administrator.   I may be putting in a new support ticket!  
  > **username_1**: username_0, I suspect that such capability may have been intentionally omitted.  It would be too easy for a system to be configured to always set the permission and then forget about it.... with ultimately some contacts getting permissioned where they shouldn't be.  
  > **username_2**: It would be bad to always grant the permission on employee relationships: if you collect employer name on a public form, someone could just change employer repeatedly to get access to a bunch of contacts.  
  
  ---
  
  ### Answer by username_3 on 2015-11-05. Score: 1
  
  [Relationship Permissions as ACLs](https://civicrm.org/extensions/relationship-permissions-acls) doesn't fully work in CiviCRM 4.6.x (please refer to issue here <https://issues.civicrm.org/jira/browse/CRM-17349>)
  
  There is a good news for "permissioned relationships" fans: sounds like CiviCRM (at least 4.6.10) not only allows "one to one" permissions via relationship; it has also build-in support for inherited permissions via relationships via "Allow second-degree relationship permissions" radio button at Administer->System settings->Misc .
  
  It's truly brilliant for use cases, where (quote): **contacts with the permission to edit a related contact will inherit that contact's permission to edit other related contacts.**
  
  
  ---
  
  