Answers.Body: <p>Brad is correct – this isn't possible to do without <a href="https://craftcms.com/docs/plugins/introduction" rel="nofollow">writing a plugin</a>. For your particular use case, this will be very simple, though.</p>
  
  <p>What you'll have to do, is to write a custom <a href="https://craftcms.com/docs/plugins/field-types" rel="nofollow">FieldType</a> that extends the stock <a href="https://craftcms.com/classreference/fieldtypes/EntriesFieldType" rel="nofollow">EntriesFieldType</a> class. The only thing your custom fieldtype needs to do, is to add an additional criteria to the query that pulls entries for input selection. Don't worry, this is going to be quite easy.</p>
  
  <p>The quickest way to get started is to use the excellent <a href="https://pluginfactory.io/" rel="nofollow">Plugin Factory</a> to scaffold your plugin. Call it whatever you like. Don't enable any of the plugin components.</p>
  
  <p>Download and unzip your plugin, and put the folder in your <code>craft/plugins</code> directory. Add a sub folder called <code>fieldtypes</code> to your plugin's directory (i.e. <code>{pluginhandle}/fieldtypes</code>).</p>
  
  <p>Create a new file in the <code>fieldtypes</code> directory called <code>MyPlugin_RestrictedEntriesFieldType.php</code> or the like (where <code>MyPlugin</code> should be replaced with the real name for your plugin).</p>
  
  <p>Inside that file, paste the following code (remember to change the class name to whatever you called the file):</p>
  
  <pre><code>&lt;?php
  namespace Craft;
  
  class MyPlugin_RestrictedEntriesFieldType extends EntriesFieldType
  {
  
      public function getName()
      {
          // This can be whatever you want, but avoid "Entries"
          return Craft::t('Restricted Entries');
      }
  
      protected function getInputSelectionCriteria()
      {
          $user = craft()-&gt;userSession-&gt;getUser();
          return array(
              'authorId' =&gt; $user-&gt;id,
          );
      }
  
  }
  </code></pre>
  
  <p>That's the whole thing; your custom fieldtype. Save the file and install your plugin. Convert whatever relevant Entries fields you may have to your new "Restricted Entries" fieldtype.</p>
  
  <p>The code above should be fairly self explanatory – it extends EntriesFieldType which means it'll work exactly like the stock Entries field (and any fields can also be converted to and from the Entries fieldtype without losing data). The only difference is that your custom fieldtype includes the <code>authorId</code> criteria when Craft pulls entries for input selection, where the <code>authorId</code> needs to match the currently logged in user's ID.</p>
  
  <p>If you need similar fields for other element types, you can just repeat the process – i.e. for a restricted Categories field, you'd create an additional file called <code>myplugin/fieldtypes/MyPlugin_RestrictedCategoriesFieldType.php</code> that extends <a href="https://craftcms.com/classreference/fieldtypes/CategoriesFieldType" rel="nofollow"><code>CategoriesFieldType</code></a>, and include the same <code>getInputSelectionCriteria()</code> method as above.</p>
  
  <p>For a bit of flexibility, you can also limit the restrictive behaviour to non-admins – i.e., if an <em>admin</em> is editing a post, that user should able to select entries authored by all users:</p>
  
  <pre><code>protected function getInputSelectionCriteria()
  {
      $user = craft()-&gt;userSession-&gt;getUser();
      if (!$user-&gt;admin) {
          return array(
              'authorId' =&gt; $user-&gt;id,
          );
      }
      return array();
  }    
  </code></pre>
  
  <p>Finally, a different option is to set the <code>authorId</code> criteria to the current entry's (or category's) author's ID, instead of the currently logged in user's ID. This is more flexible and perhaps more future proof, in that any user that has permission to edit the entry will only be able to select entries that have the same author as the entry's original author. </p>
  
  <p>Obviously, if the entry hasn't been saved yet it won't have an author, so this code should fall back to using the current user's ID for new entries, as above:</p>
  
  <pre><code>protected function getInputSelectionCriteria()
  {
      if ($this-&gt;element) {
          return array(
              'authorId' =&gt; $this-&gt;element-&gt;authorId,
          );
      }
      $user = craft()-&gt;userSession-&gt;getUser();
      return array(
          'authorId' =&gt; $user-&gt;id,
      );
  }
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-04T14:43:02.320Z
Answers.Text: Fantastic answer and exactly what I needed. I knew I'd be able to do a custom field but this saved me having to research the best approach and implement. Much appreciated.
Answers.UserDisplayName: Dexterity
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-04T15:25:18.997Z
Answers.Text: Awesome @Dexterity - happy it helped you out.
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-04T09:00:01.897Z
Answers.LastActivityDate: 2016-08-04T15:23:41.537Z
Answers.LastEditDate: 2016-08-04T15:23:41.537Z
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Answers.Body: <p>Craft's permission system doesn't go down to the field level, which is what you're looking for.</p>
  
  <p>You'd either have to replicate the functionality you're looking for on the front-end of the site, or develop a custom field type that took into account <a href="https://craftcms.com/docs/plugins/hooks-reference#registerUserPermissions" rel="nofollow">custom permissions</a> for your users.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-03T23:33:08.633Z
Answers.LastActivityDate: 2016-08-03T23:33:08.633Z
Answers.UserDisplayName: Brad Bell
Body: <p>First site using Craft and impressed thus far.</p>
  
  <p>I'm going to be allowing CP access for all users, and these users will have access to multiple channels. I want them to be able to relate their entries from different channels to each other, but only be able to select from their own entries within the relationship field.</p>
  
  <p>I can't seem to find anywhere that allows this. I did a test with 2 separate users, and when I went to relate, I could see the other user's entries available for relationship in the entries relationship field. This won't be acceptable as each user should be in their own silo and only have the ability to relate their own entries.</p>
  
  <p>Is there any way I can accomplish this that I'm missing? (edit: without custom field type)</p>
  
Tags: <relations><fieldtypes><entries-field><channels>
Title: Restricting relationship field by author
ThreadText: # Restricting relationship field by author
  
  (Asked by: username_0 on 2016-08-03)
  
  First site using Craft and impressed thus far.
  
  I'm going to be allowing CP access for all users, and these users will have access to multiple channels. I want them to be able to relate their entries from different channels to each other, but only be able to select from their own entries within the relationship field.
  
  I can't seem to find anywhere that allows this. I did a test with 2 separate users, and when I went to relate, I could see the other user's entries available for relationship in the entries relationship field. This won't be acceptable as each user should be in their own silo and only have the ability to relate their own entries.
  
  Is there any way I can accomplish this that I'm missing? (edit: without custom field type)
  
  **Tags:** relations, fieldtypes, entries-field, channels
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-08-04. Score: 2 | Accepted answer
  
  username_2 is correct – this isn't possible to do without [writing a plugin](https://craftcms.com/docs/plugins/introduction). For your particular use case, this will be very simple, though.
  
  What you'll have to do, is to write a custom [FieldType](https://craftcms.com/docs/plugins/field-types) that extends the stock [EntriesFieldType](https://craftcms.com/classreference/fieldtypes/EntriesFieldType) class. The only thing your custom fieldtype needs to do, is to add an additional criteria to the query that pulls entries for input selection. Don't worry, this is going to be quite easy.
  
  The quickest way to get started is to use the excellent [Plugin Factory](https://pluginfactory.io/) to scaffold your plugin. Call it whatever you like. Don't enable any of the plugin components.
  
  Download and unzip your plugin, and put the folder in your `craft/plugins` directory. Add a sub folder called `fieldtypes` to your plugin's directory (i.e. `{pluginhandle}/fieldtypes`).
  
  Create a new file in the `fieldtypes` directory called `MyPlugin_RestrictedEntriesFieldType.php` or the like (where `MyPlugin` should be replaced with the real name for your plugin).
  
  Inside that file, paste the following code (remember to change the class name to whatever you called the file):
  
  ```
  <?php
  namespace Craft;
  
  class MyPlugin_RestrictedEntriesFieldType extends EntriesFieldType
  {
  
      public function getName()
      {
          // This can be whatever you want, but avoid "Entries"
          return Craft::t('Restricted Entries');
      }
  
      protected function getInputSelectionCriteria()
      {
          $user = craft()->userSession->getUser();
          return array(
              'authorId' => $user->id,
          );
      }
  
  }
  
  ```
  
  That's the whole thing; your custom fieldtype. Save the file and install your plugin. Convert whatever relevant Entries fields you may have to your new "Restricted Entries" fieldtype.
  
  The code above should be fairly self explanatory – it extends EntriesFieldType which means it'll work exactly like the stock Entries field (and any fields can also be converted to and from the Entries fieldtype without losing data). The only difference is that your custom fieldtype includes the `authorId` criteria when Craft pulls entries for input selection, where the `authorId` needs to match the currently logged in user's ID.
  
  If you need similar fields for other element types, you can just repeat the process – i.e. for a restricted Categories field, you'd create an additional file called `myplugin/fieldtypes/MyPlugin_RestrictedCategoriesFieldType.php` that extends [`CategoriesFieldType`](https://craftcms.com/classreference/fieldtypes/CategoriesFieldType), and include the same `getInputSelectionCriteria()` method as above.
  
  For a bit of flexibility, you can also limit the restrictive behaviour to non-admins – i.e., if an *admin* is editing a post, that user should able to select entries authored by all users:
  
  ```
  protected function getInputSelectionCriteria()
  {
      $user = craft()->userSession->getUser();
      if (!$user->admin) {
          return array(
              'authorId' => $user->id,
          );
      }
      return array();
  }    
  
  ```
  
  Finally, a different option is to set the `authorId` criteria to the current entry's (or category's) author's ID, instead of the currently logged in user's ID. This is more flexible and perhaps more future proof, in that any user that has permission to edit the entry will only be able to select entries that have the same author as the entry's original author.
  
  Obviously, if the entry hasn't been saved yet it won't have an author, so this code should fall back to using the current user's ID for new entries, as above:
  
  ```
  protected function getInputSelectionCriteria()
  {
      if ($this->element) {
          return array(
              'authorId' => $this->element->authorId,
          );
      }
      $user = craft()->userSession->getUser();
      return array(
          'authorId' => $user->id,
      );
  }
  
  ```
  
  > **Comments:**
  > **username_0**: Fantastic answer and exactly what I needed. I knew I'd be able to do a custom field but this saved me having to research the best approach and implement. Much appreciated.  
  > **username_1**: Awesome @username_0 - happy it helped you out.  
  
  ---
  
  ### Answer by username_2 on 2016-08-03. Score: 2
  
  Craft's permission system doesn't go down to the field level, which is what you're looking for.
  
  You'd either have to replicate the functionality you're looking for on the front-end of the site, or develop a custom field type that took into account [custom permissions](https://craftcms.com/docs/plugins/hooks-reference#registerUserPermissions) for your users.
  
  
  ---
  
  