title: Valid use case for django admin?
body: <p>I want to build a django site where a certain group of trusted users can edit their profile information. Does it make sense to have each trusted user go through the django admin interface? I'd only want them to be able to see and edit their own information (obviously). It doesn't seem like this fits the way the django people define "trust", especially the bolded bit...</p>
  
  <p>From <a href="http://74.125.95.132/search?q=cache:fw9E1c2Oa7AJ:www.djangobook.com/en/beta/chapter18/+django+admin+use+cases&amp;hl=en&amp;ct=clnk&amp;cd=2&amp;gl=ca&amp;client=firefox-a" rel="noreferrer">The Django Book, Chapter 18</a>:</p>
  
  <blockquote>
    <p>The admin is designed to be used by
    people who you, the developer, trust.
    This doesn’t just mean “people who
    have been authenticated;” it means
    that Django assumes that your content
    editors can be trusted to do the right
    thing.</p>
    
    <p>This means that there’s no “approval”
    process for editing content — if you
    trust your users, nobody needs to
    approve of their edits. It also means
    that the permission system, while
    powerful, has no support for limiting
    access on a per-object basis. <strong>If you
    trust someone to edit their own
    stories, you trust them not to edit
    anyone else’s without permission.</strong></p>
  </blockquote>
  
  <p>Is this one of those use cases that fits with django's admin module, or is it just a specialized view for a non-trusted user?</p>