title: Managing users in the TFS work items "Assigned To" field
body: <p>So I know there have been a couple of posts around about this topic, but I don't think they've quite got to the bottom of it!</p>
  
  <p>So my problem is that when I create a new work item in TFS, the users which I can assign it to include <em>NT Authority\Local Service</em> (which is also the TFS service account). I'm not asking why, as I know that this field, by default is populated by the Valid Users group, and upon inspecting the groups, I can see that the group permissions hierarchy looks like this:</p>
  
  <pre><code> -&gt; Valid Users
     -&gt; Project Collection Admistrators
        -&gt; Project Collection Service Accounts
           -&gt; NT Authority\Local Service
  </code></pre>
  
  <p>And you can't change anything in the project collection service accounts, so surely by default, everyone has this user in the assign to field? So does this mean everyone accepts it, or do they modify their process templates to filter it out (see the blog <a href="http://blog.edwardsmit.com/2006/08/limiting-the-assignedto-dropdown-population-for-team-foundation-server-workitems/" rel="nofollow noreferrer">here</a>)?</p>
  
  <p>Just seems a bit odd to me that by default is isn't filtered out already! Clearly I don't want to be removing this from any permissions either (even if I could) as I'm worried it'll cause problems later.</p>
  
  <p>So is filtering in the process template the only way (which looks like a bit of effort to maintain), or is there a simpler way?</p>