Answers.Body: <p>I found another workaround which works quite well: I create a user group where users can only edit their entries.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-29T02:34:35.093Z
Answers.LastActivityDate: 2018-05-29T02:34:35.093Z
Answers.UserDisplayName: Paul
Answers.Body: <p>Entry permissions are sort of an all or nothing thing. If they can publish entries, they can publish all entries or just their own entries. The tricky part of this kind of permission is that Craft doesn't know if a category field will be on a particular entry type.</p>
  
  <p>A possible way to make this work is to create a custom plugin that fires the <a href="http://buildwithcraft.com/docs/plugins/events-reference#entries-onBeforeSaveEntry" rel="nofollow"><code>entries.onBeforeSaveEntry</code></a> event, and checks each user's category access with the entry's categories. Granted, you run into the issue of them being able to remove the category to remove any problems.</p>
  
  <p>A second option is to give them a special front-end portal area that will let them edit entries, and let you filter those entries to what they can edit. You will also then be able to omit fields that you don't want them to edit (including the categories that prohibit their access).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-23T03:07:00.700Z
Answers.Text: Thanks, I'll be looking into both options however for a newbie like me seems like there no easy options.
Answers.UserDisplayName: Paul
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-22T11:32:07.020Z
Answers.LastActivityDate: 2014-07-22T11:32:07.020Z
Answers.UserDisplayName: Bryan Redeagle
Body: <p>I'm building a site that regroups several properties, and I'd like each manager to edit content in his property only. All properties use the same templates and share content between each other.</p>
  
  <p>I first tried to create a new section for each property, but it occurs to me that it would be much simpler to have a "room" and "facilities" section (and templates), and then divide everything using categories.</p>
  
  <p>However at the moment user permissions only allow a user to add any category to their entries, which could lead to mistakes if users are not careful.</p>
  
  <p>Would it be possible to limit users to a single category, so that user1 can only edit entries in category1 and user2 in category2? Any tips on how to approach this?</p>
  
  <p>Thanks in advance</p>
  
Tags: <users><categories>
Title: Is it possible to limit users to adding/editing entries in specific categories?
ThreadText: # Is it possible to limit users to adding/editing entries in specific categories?
  
  (Asked by: username_0 on 2014-07-22)
  
  I'm building a site that regroups several properties, and I'd like each manager to edit content in his property only. All properties use the same templates and share content between each other.
  
  I first tried to create a new section for each property, but it occurs to me that it would be much simpler to have a "room" and "facilities" section (and templates), and then divide everything using categories.
  
  However at the moment user permissions only allow a user to add any category to their entries, which could lead to mistakes if users are not careful.
  
  Would it be possible to limit users to a single category, so that user1 can only edit entries in category1 and user2 in category2? Any tips on how to approach this?
  
  Thanks in advance
  
  **Tags:** users, categories
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2014-07-22. Score: 4 | Accepted answer
  
  Entry permissions are sort of an all or nothing thing. If they can publish entries, they can publish all entries or just their own entries. The tricky part of this kind of permission is that Craft doesn't know if a category field will be on a particular entry type.
  
  A possible way to make this work is to create a custom plugin that fires the [`entries.onBeforeSaveEntry`](http://buildwithcraft.com/docs/plugins/events-reference#entries-onBeforeSaveEntry) event, and checks each user's category access with the entry's categories. Granted, you run into the issue of them being able to remove the category to remove any problems.
  
  A second option is to give them a special front-end portal area that will let them edit entries, and let you filter those entries to what they can edit. You will also then be able to omit fields that you don't want them to edit (including the categories that prohibit their access).
  
  > **Comments:**
  > **username_0**: Thanks, I'll be looking into both options however for a newbie like me seems like there no easy options.  
  
  ---
  
  ### Answer by username_0 on 2018-05-29. Score: 1
  
  I found another workaround which works quite well: I create a user group where users can only edit their entries.
  
  
  ---
  
  